Scrolling or click on area crash to desktop

[ma5owat]

I have encountered a problem where the program will crash when either scrolling to Runthall or selecting the area from the minimap.

I did find a solution to the problem by using the TTDX Editor, modifying a few setting (Town ratings) and then saving the file. It worked fine for a while then had crash when viewing another area. (I think it probably would work with just opening the file then saving but I didn't try)

It has occured with both 2.5b8 and 2.6a and I have tried different setting in the ttdpatch.cfg and removing all GRFs except TTDPBASEW.

The config file I am using now still replicates the error.

My current newgrf.cfg file contains:

Code: Select all

newgrf/TTDPBASEW.GRF
#DISABLED#newgrf/ARCTICSETW.GRF
#DISABLED#newgrf/CARGOSETW.GRF
#DISABLED#newgrf/COMBROADW.GRF
#DISABLED#newgrf/DBSETW.GRF
#DISABLED#newgrf/DBSETXLW.GRF
#DISABLED#newgrf/EUROADSTW.GRF
newgrf/JCINDSTAW.GRF
#DISABLED#newgrf/LONGBUSESW.GRF
#DISABLED#newgrf/MCTRUCKSW.GRF
#DISABLED#newgrf/NAVISTARTRUCKSW.GRF
#DISABLED#newgrf/NEWCARGOW.GRF
#DISABLED#newgrf/NEWSHIPSW.GRF
#DISABLED#newgrf/NEWSTATSW.GRF
#DISABLED#newgrf/PAPERW.GRF
#DISABLED#newgrf/SCANIATRUCKSW.GRF
#DISABLED#newgrf/SPITZERTRUCKSW.GRF
#DISABLED#newgrf/TEMPSETW.GRF
#DISABLED#newgrf/TROPICSTW.GRF
#DISABLED#newgrf/TTDPATCHW.GRF
#DISABLED#newgrf/TTRS2W.GRF
#DISABLED#newgrf/USROADSW.GRF
#DISABLED#newgrf/USSIGZW.GRF
#DISABLED#newgrf/VOLVOTRUCKSW.GRF
newgrf/USSETW.GRF
#DISABLED#newgrf/USSTATSW.GRF

[Dave]

This problem and the other one you have in the other thread are both old problems which were supposedly fixed long ago. But... If you're using the latest 2.6a...

[ma5owat]

Sorry if those were duplicates, I checked the to-do list and tried searching for similar posts.

[Commander238]

+-----------------------------------------------------+
| Crash to desktop when viewing one town |
+-----------------------------------------------------+

Hello, I played a single scenario, using the newest nightly TTDPatch-Win32-Nightly-r1784
and today, the game crashed to desktop. I have got a savegame long time ago before it crashed
(everything ok) and another save short time before the crash.
The crash is independent from the .grf files, so my newgrfw.cfg and my .grf files are probably
not important. If I delete them, the problem remains.
The action which causes the game to crash is the following -
I sroll the view to the town named "Wertmünster" (aka "Würzburg" using German Towns .grf file).
Easy select Towns -> Wertmünster.

Files:
CRASH000.TXT - crashlog
NewGrfW.cfg - newgrf - not important
TRT05.SV1 - United Transport, 17th Oct 1965 - savegame ok
TRT06.SV1 - United Transport, 23rd Mar 1973 - savegame before the crash
TTDPatch.cfg - my ttdpatch config

[Lakie]

I assume you've tried this (since its a sticky) before reviving his thread about this bug?

~ Lakie

[Commander238]

Hi Lakie.

I have read that sticky thread, but it didn't solve my problem.
I already had the appropriate TTDLOADW.ovl for my version. I rebuilt it when I was upgrading to TTDPatch-Win32-Nightly-r1784 as I always do it manually.

But I have new information for you.
More than using debuggers, I like to use Paint, so I found the exact location of my crashing area.
In fact, it isn't the town itself. It is the yellow player's airport. Some buggy accident placed the airport over pink player's headquarters and probably also over a hill! See the attached pictures. The game crashes always if I try to look at the highlighted green area. Giant screenshot also crashes.
So there is one (maybe unrecoverable) error on my scenario. But there is also an AI airport-placing bug in the newest nightly r1784! See, that the pink player still exists and where is his headquarters? On a hill under the airport

I started the game on the 1st Nov 2007 with the newest Nightly r1781, updated nightly and OVL on 3rd Nov and continued playing, saved TRT05.SV1 already with Nightly r1784, and I forgot to make saves frequently, so that my autosave included the crashing area and my last ordinary save was 9 years older. I resaved the autosave to the TRT06.SV1 file. It didn't help.

Please tell me how the yellow idiot AI could place an airport so badly?!

[DaleStan]

Not this airport-placement bug again.

We need a savegame from a few game-days before the AI misplaces its airport before we can find and fix this bug.

[Commander238]

Ok, I understand your point DaleStan.
I will save my games more often and hopefully I will get a savegame few days before a next crash. But it might be rare...

I don't know yet, how can I fix the current savegame. Probably I will start again from nine years ago, because If I let the yellow player go bankrupt (airport vanishes) and buy the pink player (HQ vanishes) the area still causes a crash... I tried also TTDX editor, but I don't know what to change and only resaving the scenario in editor didn't help me.

[DaleStan]

It's not you personally. It's this impossible-to-find bug.

Also, it's not the crash that's significant. It's the building of the airport that's significant. Unfortunately, this doesn't cause a crash until you look at it, which makes it at best tedious to detect.

[minime]

Do you think that if you set up a scenario with 2 cities on islands, and set aibuildairchance to 100%, it would make this bug a bit easier to replicate?

It just occurred to me, but I don't have time to try it now myself.

[Chris 'Awkward' McKenna]

Probably not helpful, as I didn't get a savegame near the time the airport was built, but one AI player managed to build an airport not only on a hill but also on top of one of my railway lines! I didn't notice for a few years until I spotted the train wasn't making money, as it had a route to a depot, just not to one of its two stations.

[Commander238]

@Our kind Developers
It would help us, when there was an option to make frequent autosaves,
for example each month and named for example Autosave+Date.
So then if I find a train not making money, then I load a couple of autosaves and find the autosave just before the AI placed the airport.

[JGR]

If you post the savegame, it's possible to "neutralise" the affected tiles by effectively changing them to grass, without looking at them, (using OllyDbg).
While a bit of a kludge it makes the game playable...
I've done this at least once before, and it doesn't take me long...

JGR

PS. if you do post it, I may not be able to do this immediately, as my schedule is very busy from 18:45 (France) to 17:00 tomorrow...

Edit: I see you posted it up thread (doh)...

Edit 2: Done, the problem was not the same as last time so it took be a bit longer than I suspected. I ending up just cloning brown ground over the entire airport, using cht: clonetile (added features soon to be committed ).

[Commander238]

Hi JGR,
thanks a lot! It works.

[Commander238]

HI ALL DEVELOPERS!
Bug to solve here.

As I promised, I've made a better example of the bad-airport-placing bug, using the idea of Minime.
I made an extra scenario designed to show AI's building inteligence :-]

Scenario:
- only islands
- AI cannot build bridges because of the land coasts

Savegame:
- I set Airportbuildchance to 100% and other chances to 0%
- I prepared my own money source: 2 coal mines to connect with two power stations...
- I set year to 1975 to enable big airports
- at April 7th AI starts to build.
My savegame is saved 5 days before the certain bug occurs.
AI builds two airports. One on top of houses, one on top of the sea!

LOOK AT MY FILES...

EDIT:
I realized, that this bug somehow depends on attached GRFs. So I added them also to the archive.
If I remove Ttrs3w.grf, the AI doesn't build a bad placed airport at April 7th.
But it could be only an accident. AI could build it possibly later at some other place.
For sure, now you will be able to reproduce the silly bug.

EDIT2:
I used only this version of TTDPatch and TTRS:
TTDPatch V2.6 alpha 0 r1786 (Windows)
Total Town Replacement Set (v3) Dec 08 2006 17:11:28 GMT

EDIT3:
The ommiting of Ttrs3w.grf doesn't solve the bug. It happened again.
But if you don't copy my GRFs, then the bug doesn't happen immediately at April 7th.
So I reccomend to try it with my GRFs.

[DaleStan]

Until this bug actually gets fixed, I'm pretty sure it will go away if you turn newairports off.