> load and play in a loaded savegame
> create a new world
> *crash*
=> windows XP
=> pak128-57
=> winSDL-101.1-2070
Error in pak128 which will appear also during quitting due to some buildings in wrong roatation (usually). At least this is my guess.
On a completely different note, yours is an example of a completely unusable bug report, because I need exactly to know:
a) what has happened (division by zero, wrong adress)
b) The last lines of the logfile (simu.log)
c) The savegame in question in this case to reproduce
If it is just an asserting, you can click continue (and report it).
It appears with all savegames.
There is nothing writen in simu.log.
Quotea) what has happened (division by zero, wrong adress)
How I can know it ?
Aparently not with all, as it does not appear with MY savegames.
And windows should tell you wat error happend, when you click on details.
Windows doesn't tell me thare was an error, When I want to load a savegame, I click on it, the loading bar shows (empty) and the game crash.
Quote from: Topic title
create a new crash : )
A topic title like that is not useful. :-\
Please gauthier, make topic title more relevant next time ;)
[Guidelines] How to post a Bug Report http://forum.simutrans.com/index.php?topic=56.0 (see item 3)
Plus, topic renamed from "create a new crash : )" to "Win 101.1 r2070 pak128 - Crash in loaded savegame".
What does it mean "The game crash"? Either there will be a windows dialog popping up, saying that "this program has done xxx and must be closed. You can get more informations by clicking on retry"
This is a real crash. Otherwise the programm will show an internal dialoge, showing the message why it crashes. THis is then also written in the logfile as the last three or four messages. This is then also needed.
In your case it could also crash loading a vehicle with a wrong good in the savegame. Without any definite error message I have zero clue and cannot fix anything.
The file default.sve could be broken - renaming it (after stopping ST) might help.
Oh, and that Pak128 version is rather old (in terms of nightly builds).
I'm going to test a newer pak128.