Take care with copies of your scenarios in windows explorer
Posted: Sat Jan 30, 2010 4:47 pm
Searching the origin of some bugs I encountered when I deleted units in my scenarios with a great number of units, I made lot of test and probably founded myself the cause of pb : when you have created a scenario, you MAY NOT realize a copy of this scenario in the windows explorer with "copy file" function. If you do, and if you try after that to modify this copy in the editor by erasing somes units, then it will causes crash at start game (not valid scenario message)
So : you must always continue the work on your own creations with your original scenario, and not with a copy of this scenario made out of the editor in the windows explorer, for example a copy made for security, as I did) : I had always crashes with security copy of my scenario when I reworked on, and I have never crash when I continue the work directly on my original scenario.
conclusion : DO NOT COPY OF YOUR FOG SCENARIOS UNDER OTHER NAME WITH THE WINDOWS EXPLORER, CONTINUE ALWAYS THE WORK WITH YOUR ORIGINAL SCENARIO CREATED IN THE EDITOR
Second : Do not rename in windows explorer your scenarios after they have been created in the editor : I tried that for experimentation and received the same message some players have given on the forum : "file is not valid Fog scenario".
So : you must always continue the work on your own creations with your original scenario, and not with a copy of this scenario made out of the editor in the windows explorer, for example a copy made for security, as I did) : I had always crashes with security copy of my scenario when I reworked on, and I have never crash when I continue the work directly on my original scenario.
conclusion : DO NOT COPY OF YOUR FOG SCENARIOS UNDER OTHER NAME WITH THE WINDOWS EXPLORER, CONTINUE ALWAYS THE WORK WITH YOUR ORIGINAL SCENARIO CREATED IN THE EDITOR
Second : Do not rename in windows explorer your scenarios after they have been created in the editor : I tried that for experimentation and received the same message some players have given on the forum : "file is not valid Fog scenario".