Question on the installation of Part 14. The instructions call for restore point method. In the past this included reinstalling MME-12 afterwards. I do not see that step in the instructions for Parts 13 and 14. So its not required? Sorry if dumb question. Followed instructions for 13 and 14 to the T and managed to break my stable WAW install with map loading .ini errors. No biggy I will reinstall CUP. Just wanted to know about the restore method at this point. Kudos to all for the magnificent work!!
For #WAW Part-12 we wanted to ensure that everyone had the latest MAPMODS/all.ini from SAS Modular Map Expansion 12.
WAW Part-13/14 were made subsequently to Map Expansion 12 and already contain the most up to date MAPMODS/all.ini. There is no particular reason for any errors, but then the reason is seldom ever so easily apparent.
Instead of leaping to any conclusions we need to know what maps exactly and what is the nature of the error? If you get stuck and ALT/CTRL/DEL out of Il2 Logfile.TXT will still record the last thing that happned. I have been in and out of FMB all week with no errors but then we have probably been to different places.
Even without a precise logfile.TXT; if we know what maps to try the first thing is to replicate the error. I am not aware of anything being overlooked but if the errors are there and we share them that is actually good news and usually solved quickly and painlessly.
One more thing - I'm assuming the phrase
"map loading .ini errors" refers to FMB? Please clarify. If its a QMB failure that's something else altogether. QMB Missions (NOT maps, NEVER call them maps) are missions that do indeed load maps and scenarios but are not an accurate test of a map itself. This is because there are many other parameters wherin QMB can fail long before loading the map!
This is a very important distinction that modders and users need to be clear about -
MAPS in FMB are integral to the simulator. Map errors are located in the SFS files and the INIs that configure them.
MISSIONS in QMB are NOT integral to the simulator - They are effectively an addon that makes use of the SFS files and INIs but does not reliably indicate anything else about them. If your QMB doesn't work everytime we know where to look and can do a bit of mission tweaking.
So: MAPS - Means Full Mission Builder core program (FMB) and MISSIONS means Quick Mission Builder (QMB). MISSIONS may also refer to specific FMB created missions or campaigns but the distinction is clear.If your FMB fails to load properly, that's a bigger deal and indicates something wrong at the core package level.
Can't say or do anymore than that, we need some info.
Stability:The purpose of a
"Restore Point" install is stability. Assuming you want the additional mods featured then, not always but sometimes, the
"Restore Point" install ensures a clean mod folder free from accumulated errors, either yours or mine. With Part-14 the new Command and Control required the removal of many classfiles and the replacement of others. I have always worked to avoid complex install instructions and conditions. The safest course in this case was to create a new #WAW - The same conditions also required a new #JTW folder for that update.
...it is maps isn't it? - Go on then, lay it on me...
