EditorObjectsBlackList

[Jupp]

~S~ Everyone,

 

There are files in the IL-2 data GUI folder, one is the source of the ME bottom right window display's information. Here is the line item list of that file :

 

 

Mission Objects Max Count.cfg

 

BUILDING=10
AIRFIELD=8
FLAG=8
VEHICLE=40
PLANE=20
BALOON=20
SHIP=10
EFFECT=12
ENTITY=80
INFLUENCEAREA=12
COMPLEXTRIGGER=10

 

 

As you can see, the Max Building Count is "10".

 

Ten "buildings" is the MAX amount of Buildings Recommended to run the simulation properly. Ten buildings to simulate WW2 Combat over Stalingrad... and .etc???

 

This is why I routinely overrun the limits in my own creations. Damn the torpedoes style! But anyway... No, you cannot edit that file and "make everything better" either. Nope.

 

 

The other file is called : "EditorObjectsBlackList".cfg and here is it's content listing :

 

graphics\planes\i16t24\i16t24-c.txt
graphics\planes\mig3\mig3-c.txt
graphics\planes\p40e1\p40e1-c.txt
graphics\planes\il2m41\il2m41-c.txt
graphics\planes\pe2s35\pe2s35-c.txt
graphics\planes\pe2s35\pe2s35-c1.txt
graphics\planes\pe2s35\pe2s35-c1-low.txt
graphics\planes\pe2s35\pe2s35-c2.txt
graphics\planes\pe2s35\pe2s35-c2-low.txt
graphics\planes\bf109e7\bf109e7-c.txt
graphics\planes\bf109f2\bf109f2-c.txt
graphics\planes\mc202s8\mc202s8-c.txt
graphics\planes\bf110e2\bf110e2-c.txt
graphics\planes\bf110e2\bf110e2-c1.txt
graphics\planes\bf110e2\bf110e2-c1-low.txt
graphics\planes\ju88a4\ju88a4-c.txt
graphics\planes\ju88a4\ju88a4-c1.txt
graphics\planes\ju88a4\ju88a4-c1-low.txt
graphics\planes\ju88a4\ju88a4-c2.txt
graphics\planes\ju88a4\ju88a4-c2-low.txt
graphics\planes\ju88a4\ju88a4-c3.txt
graphics\planes\ju88a4\ju88a4-c3-low.txt

graphics\planes\lagg3s29\lagg3s29-c.txt
graphics\planes\bf109f4\bf109f4-c.txt
graphics\planes\bf109g2\bf109g2-c.txt
graphics\planes\il2m42\il2m42-c.txt
graphics\planes\il2m42\il2m42-c1.txt
graphics\planes\il2m42\il2m42-c1-low.txt
graphics\planes\pe2s87\pe2s87-c.txt
graphics\planes\pe2s87\pe2s87-c1.txt
graphics\planes\pe2s87\pe2s87-c1-low.txt
graphics\planes\pe2s87\pe2s87-c1-wm.txt
graphics\planes\pe2s87\pe2s87-c1-wm-low.txt
graphics\planes\pe2s87\pe2s87-c2.txt
graphics\planes\pe2s87\pe2s87-c2-low.txt
graphics\planes\ju87d3\ju87d3-c.txt
graphics\planes\ju87d3\ju87d3-c1.txt
graphics\planes\ju87d3\ju87d3-c1-low.txt
graphics\planes\he111h6\he111h6-c.txt
graphics\planes\he111h6\he111h6-c1.txt
graphics\planes\he111h6\he111h6-c1-low.txt
graphics\planes\he111h6\he111h6-c1-wm.txt
graphics\planes\he111h6\he111h6-c1-wm-low.txt
graphics\planes\he111h6\he111h6-c2.txt
graphics\planes\he111h6\he111h6-c2-low.txt
graphics\planes\he111h6\he111h6-c3.txt
graphics\planes\he111h6\he111h6-c3-low.txt
graphics\planes\he111h6\he111h6-c3-wm.txt
graphics\planes\he111h6\he111h6-c3-wm-low.txt
graphics\planes\he111h6\he111h6-c4.txt
graphics\planes\he111h6\he111h6-c4-low.txt
graphics\planes\la5s8\la5s8-c.txt
graphics\planes\fw190a3\fw190a3-c.txt
graphics\planes\yak1s69\yak1s69-c.txt
graphics\planes\ju523mg4e\ju523mg4e-c1-low.txt
graphics\planes\MiG3s24\Mig3s24-C.txt
graphics\vehicles\_t34-76stz\_t34-76stz_turret.txt
graphics\vehicles\_pziii-l\_pziii-l_turret.txt
graphics\vehicles\_pziii-l\_pziii-l_c.txt
graphics\vehicles\_pziii-l\_pziii-l_c1.txt
graphics\vehicles\_t34-76stz\_t34-76stz-c.txt
graphics\vehicles\_t34-76stz\_t34-76stz-c1.txt
graphics\Artillery\SearchlightGER\SearchlightGER-attach.txt
graphics\Artillery\SearchlightGER\LandlightGER-attach.txt
graphics\Artillery\SearchlightSU\SearchlightSU-attach.txt
graphics\Artillery\SearchlightSU\LandlightSU-attach.txt
graphics\Artillery\61k\61k-attach.txt
graphics\Artillery\Flak38\Flak38-attach.txt
graphics\Trains\Wagons\AAPlatform.txt
graphics\Trains\Wagons\AAPlatform-mg.txt
graphics\Ships\1124\1124-T1.txt
graphics\Ships\1124\1124-T2.txt
graphics\Ships\1124\1124-T3.txt
graphics\Ships\1124\1124-T4.txt
graphics\Ships\RiverGunShipA\RiverGunShipA-T5.txt
LuaScripts\WorldObjects\MapEmitters\AmmoExplosion.txt
LuaScripts\WorldObjects\MapEmitters\AmmoExplosion_Big.txt
LuaScripts\WorldObjects\MapEmitters\DummyGroundExpl.txt
LuaScripts\WorldObjects\MapEmitters\Ring_Bell.txt
LuaScripts\WorldObjects\MapEmitters\Static_Fire.txt

 

This is important for editors to understand, to not use those entries when working with say,  a Complex Trigger MCU.

 

 (*as an example of why this is very important information, any number of these things could result in errors occuring)

 

Oddly enough I find my future self further answering questions that my former self had in the past... Circle K anyone?

 

http://forum.il2sturmovik.com/topic/16110-information-please/

 

Light it Up,

 

!S -Jupp-

Edited February 11, 2016 by Jupp

[Juri_JS]

Aren't these max count numbers just a remnant from the early days of RoF?

[Jupp]

~S~ Juri,

 

Well yes and no. Yes it's related, but no, we are dealing with BOS now, not ROF, and soon BOM as well.

 

You can go over those limits, that is discussed in other threads, and indeed I even mention that in this one too.

 

 

To that end, I write sometimes things that "we" know already, to the benefit of those that don't know these things.

 

And then also, I expand that for us "ubermenchen", such as bringing the EditorObjectsBlackList entries up as a Topic for review.

 

I'm not from the "pay no attention to the man behind the curtain school of intellectual propriety misgivings" that some people seem to be from.

 

Paint a target on my back for it, but that's what it looks like from my own fishbowl over many years of being involved in this hobby in general...

 

I enjoy spelling it out for the next guy to want to learn about combat flight simulator mission creations. Because someday we could say :

 

Isn't that just the X from IL-2 Sturmovik Battle of Stalingrad... I already know everything about that...

 

and if no one ever posted from behind the magic curtain, this knowledge would die.

 

 

And that's the way it is,

 

!S -Jupp-

Edited February 11, 2016 by Jupp

[No601_Swallow]

OK. From a position of total ignorance, can I ask: what's the difference between the "graphics\planes\mig3\mig3-c.txt" and the normal "graphics\planes\mig3\mig3.txt"? Does that question even make any sense? And what are these .txt files anyway? 

[Jupp]

~S~ Swallow,

 

I'm glad you asked Swallow! (heh)  That is a perfectly sensible question, and here is why!

 

 

From my slightly less ignorant position, I believe that those extraneous entries are having to do with Modeling items. C maybe meaning Canopy or Cockpit.

 

I didn't make the things, and have only built one Airplane in GMax before, but because of that, and other knowledgebasi, that is the gist of it I can say with confidence.

 

Canopy would be a good guess, since that entails making transparency, which is handled differently thus the following... are you asleep yet, it goes on and on... lol

 

 

Others like the sound effects are in the same way referenced to scripting (*text) that is encoded to the game-engine and even if these "stubs" as they are called

 

are available to be seen by us, due to programming whatchamahaveit convention forcing them to be used / seen like this, these particular entries are in fact more

 

or less akin to "Hidden Folders and Files", which, if it weren't for necessity, these entries would be "invisible". We don't have that option due to the program's conventions.

 

 

 

I used the example given because if you'll notice, this is a good place to understand it from. Go down the listing and you can see the relation. Someone else might define exactly what "c" is.

 

In plain Engish, only use the Main Model Entry when using the Complex Trigger in this manner, which, I have done, plus what I've related, is how I come by this knowledge to share with you.

 

In concerns for the Newby Complex Trigger User in the Mission Editor, knowing this information could be the difference between Hours of Work going south or not, in some cases of it.

 

Or worse yet, abandoning Mission Creating out of frustration altogether, as many reports from around the world have already reported that to have happened. Self-Taught trial/error is not fun.

 

For everyone at least.

 

 

Cheers Chap,

 

!S -Jupp-  

Edited February 11, 2016 by Jupp

[No601_Swallow]

Interestsing! [strokes imaginary beard thoughtfully]. I'd better go back and check my complex triggers!

 

Thanks once again, Jupp!

[JimTM]

Good info Jupp. Thanks. I already have it covered in the upcoming manual:

 

Object Scripts List

      ...

      Important! Do not specify scripts with "-c" after the first part of the object name. For example, specify he111h6 but not he111h6-c1-low.

Edited February 11, 2016 by JimTM

[Jade_Monkey]

Im pretty sure i used the "c" versions (just in case) and nothing broke. So what effect does it have?

[Jupp]

~S~ Fellas,

 

 

The good of this thread is us all pow-wowing about something other than the cup holders on the limited production year whatever...

 

 

I wouldn't worry too much Swallow, as Monkey relates, and I'll confess, I have used those entries (just in case) before too...

 

to no ill effect (that I know of or observed anyway), however, the name of the .cfg is "EditorObjectBlackList", so I'd just assume remove doubt.

 

 

And the rest of the mambajamba I wrote is certainly true regardless.

 

Adding background and general knowledge is an important part of education, making specific details much easier to understand, I hope.

 

 

Does this constitute reverse trolling, am I the Anti-Troll?

 

So anyway, Jim's got it covered, I can put it to sleep now.

 

 

Wot Gorilla?

 

!S -Jupp-

Edited February 11, 2016 by Jupp