In my current game (exp 8.2, britain standard), I do get seemingly random crashes every now and then :(
I do use a very large map, but my system is very new and well-equiped.
James, you may find my game interesting to look at:
http://www.megaupload.com/?d=107ZX4MN
I must say playing it has been very enjoyable :) my 3 major annoyances during playing were:
1) city growth too fast
2) field sprawl (this is fixed now, right?)
3) Teleporting trains when leaving a station. Why is this happening? I think it may be pakbritain-specific.
All in all, it is still very enjoyable and the crashes are not a blocker. Thanks for making this game so great!
Brambo,
thank you very much for your report. I do not have time to investigate this evening, but I shall have a look when I get a chance. Field sprawl has indeed been fixed; town growth will be different in the next version of Pak128.Britain-Ex.
As to teleporting trains - you are the first to report this phenomenon. Can you elaborate on when it occurs? Is your attached saved game a scenario in which I can reproduce it?
I think I've seen the teleporting trains before.
Unfortunately I don't have save game of it, but I believe one of my older save games, 1984, would have had it. It totally slipped my mind to report it.
The train would stop at a station, then when it heads off to its next destination it will jump several tiles and the carriage consist reverses, stalling the train until it finishes the loading and reversing time. Usually seemed to happen on quad tracks, but I've seen it happen on double tracks, and not at the end of the line.
it only seemed to happen with pax and mail trains. I didn't quite play the game out with anything other than steam.
I have seen this teleporting happen to.
W
I saw the crashes, when put in the config file "0 = distributed approach (default)", with "1 = centralised approach" all is well.
I can't reproduce this in the 9.x branch, I'm afraid, after fast-forwarding and leaving it for well over an hour. There were some crash bugs fixed between 8.2 and 9.x, so it may well have been fixed by now. Thank you for the report :-)