From: De Eye-lands, Mon
Every update is different, depending on which dat files were modified. Some dat files update smoothly and easily. Others do not. For the latest babes scenario update set, the air and device (wpaxxx.dat and wpdxxx.dat) files update smoothly and easily. The locations (wplxxx.dat) file is one of those that do not. The new LI and refinery updates are in a certain place in the locations file. These data will NOT update to existing (ongoing) game files. This is because the economics engine is separate and independent, and the calculation basis is set on the first save of the scenario, and also because of their "secondary" placement in the Base panel. Here’s why.
In the scenario editor, there’s two parts to the panels: one part is “native” data; the other part is “pointer” data. Native data is cool; pointer data is a nightmare.
Native data (sometimes called primary placement data) is the stuff that goes into the top half of each panel. It’s the stuff that has “name” buttons or check boxes, stuff like that. It’s data that is unique and specific to each dat file.
Pointer data (sometimes called secondary placement data) is the stuff that goes into the list of Wpn fields in the bottom half of the panel. It’s pointer data because it comes from another dat file and the Wpn list is just a list of pointers that point to places in the other file. Note: The entire Wpn section is secondary data; the list, the numbers, ammo, turrets, facing, what-have-you.
Native data updates nicely, but secondary data is problematic. A savegame has an image of the original scenario and a pointer to the scenario file. When a scenario with modified data appears, and you allow updating, the new data is captured, but ships, airgroups, locations (things that rely on secondary data), that are ALREADY in-game, don’t update secondary data unless and until they are “processed”.
Processing means that secondary data is what it was until an event happens that makes the engine consult the database for something new, like a new ship/group/unit entering the game, with no prior image. Also, a ship or group or unit can upgrade (i.e., change the present image to a new one from the database). Remember the sub split-tube thing couple years ago? Newly arriving subs were ok, but pre-existing subs were a mess until they upgraded or went to a shipyard for something? Same thing – no update until processing.
In this specific scenario update set:
Changes to the Device file are all native data, so it updates nicely and easily.
Changes to the Aircraft file are all native data, so it updates nicely and easily.
Changes to the Locations file are all secondary data, so they won’t update until “processed”. But, locations data of this particular kind are not “processable”, so the changes won’t update except for a restart.
Hope this helps. JWE
Nous n'avons pas peur! Vive la liberté! Moi aussi je suis Charlie!
Yippy Ki Yay.