Page 1 of 1

Take care with copies of your scenarios in windows explorer

Posted: Sat Jan 30, 2010 4:47 pm
by welk
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".

Posted: Sat Jan 30, 2010 5:07 pm
by Examinondas
These threads may be helpful:
viewtopic.php?t=14404
viewtopic.php?t=14034

Posted: Sat Jan 30, 2010 5:38 pm
by welk
Thanks a lot for information :wink:

I think it would be better for all players if this kind of information was directly integrated in the game doumentation. Informations and tips about how to use the editor are very poor and it is not good for the Fog editor reputation. I think lot of designer will be very disappointed by the poor informations that are given by slitherine "manual" :roll: (I am one of them)

Posted: Sat Jan 30, 2010 6:08 pm
by Brigz
This seems to be a very common problem for players trying to run user made scenarios. As one of the above links says, the name of the folder holding the scenario must match exactly the the "gn=" name in either of the *.fogsg files. I think this might account for 90% of invalid scenario reports.

If you just double click on Scenario0.fogsg or Scenario1.fogsg it should open with notebook (or other text editor) and you can see the valid scenario name in the first few lines. This name has to be exactly the same as the scenario folder name.