OpenTTD

Tasklist

FS#156 - ai/default/default.c:1804: AiStateBuildDefaultRailBlocks: Assertion `!CmdFailed(r)' failed

Attached to Project: OpenTTD
Opened by Kernelpanic (Kernelpanic) - Saturday, 06 May 2006, 22:53 GMT
Last edited by Celestar (Celestar) - Wednesday, 10 May 2006, 12:02 GMT
Type Bug
Category Core
Status Closed
Assigned To No-one
Operating System Linux
Severity Medium
Priority Normal
Reported Version 0.4.7
Due in Version 0.4.8
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The attached saved game crashes after some 20-30 seconds with the message "ai/default/default.c:1804: AiStateBuildDefaultRailBlocks: Assertion `!CmdFailed(r)' failed". I am using openTTD 0.4.7 with openSUSE 10.0. This happens with the version I compiled myself as well as with the .deb package (which I converted using alien and then installed with rpm).
This task depends upon

Closed by  Celestar (Celestar)
Friday, 19 May 2006, 12:08 GMT
Reason for closing:  Fixed
Comment by Darkvater (Darkvater) - Tuesday, 16 May 2006, 21:43 GMT
Ok, this doesn't crash for me. Am I missing something here? Different openttd.cfg, already fixed in branch/0.4?
Doesn't crash in branch/0.4 or in 0.4.7 both with new AI on or off
Comment by Kernelpanic (Kernelpanic) - Wednesday, 17 May 2006, 20:46 GMT
I just verified the crash happens for me with statring openTTD, modifying the settings to Euro, German language and German names, and then loading the savegame as well as with just starting openTTD and loading that savegame. In both cases after 20-30seconds openTTD crashes with the given message.

I tried to locate an openttd.cfg file on my system but didn't find any (neither ~/.openttd/ nor /usr/share/games/openttd/). Where is it supposed to be if it exists?

Do I have to take care of special file permissions/ownership of the files in /usr/share/games/openttd/? They currently all belong to root and are world-readable.
Comment by Darkvater (Darkvater) - Thursday, 18 May 2006, 08:26 GMT
You can do a search for it. I never install openttd myself so for me it is in the same directory as the executable itself.

Loading...