Hi everyone
I sent this to team@64.simutrans.com (email in debug log) but it seems that address is no longer valid.
I recently downloaded Simutrans 111 and PAK 128 2.0.0 and have been playing a game (which was previously played on version 110) I have been able to save and load games successfully on version 111. Suddenly when I try and load a saved game I get the windows message "simutrans.exe has stopped working."
The detail as presented by windows is
Problem signature:
Problem Event Name: APPCRASH
Application Name: simutrans.exe
Application Version: 0.110.0.7
Application Timestamp: 4eb07550
Fault Module Name: simutrans.exe
Fault Module Version: 0.110.0.7
Fault Module Timestamp: 4eb07550
Exception Code: c0000005
Exception Offset: 0026262d
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 7177
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
if that helps anyone.
I have tried to start simutrans with the following "simutrans.exe -log n=1 -debug n=4" The resulting log file shows no indicative error messages. It is available if anybody wants it.
I have no addons.
I have tried to load the game with fresh versions of the binaries and PAK128 with the same results.
Any ideas welcome - I would be so sad to loose all the work I have put into this map.
Regards
Yoda
pak128 2.0 is completely incompatible with pak128 1.4.6. You should rather use this pak together with version 111 to continue old savegames. Using pak1.4.6 from sourcefore instead 2.0 should pose no problems. The easiest way to update simutrans with existing savegames is to only install the new binary.
However, if you loaded this game before in pak128 1.99 or so, then I rather suppose the savegame is corrupted.
This crashlog is unfourtunately not useful, I only learned you are using vista in South africa setting ... If anything the last ten lines of simu.log could tell something.
You can upload your savegame at some file host and we will have a look at it.
moving this to incorporated as the thread opener did not respond.