Static.ini compatibility
#1

I've been to several threads that have folks showing objects and giving the object number as the descriptor for that object. The unfortunate thing is that now we can so easily add objects and change their place in the static.ini file, my object #100 in not going be your object #100. I feel we're going to have to start using the actual name of the object itself - in my case object #100 is VehicleOpelBlitz36s.

I spent the better part of a week going through the static.ini and moved everything around so, when I start to build a mission, I start with the biggest ground objects and work down to the smallest details: revetments/blast pens, move on to hangars, then fuel tanks, control towers etc. I've added objects at pier height so there are trucks and supplies, as well as men, working away alongside the ships. I've sunk a bulding so its roof can be used as the ramp at the end of the large pier section (PortFloor) on shore - I called these objects Pierramp_2 and Pierramp_1 - and are objects 222 and 223.

This is MY logic at work and I've put all the relevant objects together in sections. I've also added over 150 humans - uniformed, casual, and half naked for the tropics - all at different altitudes so they fit into towers, on aircraft wings, on the scaffolds, climbing stairs etc. That really throws the list off kilter for anyone else. CanonUKs objects from his Channel map will rearrange my static.ini again as objects he's incorporating will be added to the appropriate sections.

So, again, if you want to let us know what objects you're using to detail something, please, please, tell us the NAME of the object. I suppose we could take a screen shot of a picture you've posted, if you have one, and then could go through our own list and match it that way, but it would just be easier if you gave the name.

Thanks for letting me get this off my chest.

Great days all.
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 2 Guest(s)