Game crashes when you try to start a race while already in a race

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start a new game and race about for a bit
2. Exit to menu
3. Attempt to start a new game

What is the expected output? What do you see instead?
Should have started a new game, I just get a 'This program stopped working'.

What version are you using? On what operating system?
v4 on Win7.

Please provide any additional information below.
* If game crashed please inculde files: _game.cfg, _log.txt, _ogre.log,
_ogreset.cfg right after crash, found in the same folder where exe.

Original issue reported on code.google.com by oskar.ko...@gmail.com on 11 Aug 2010 at 12:38

Attachments:

• _game.cfg
• _log.txt
• _ogre.log
• _ogreset.cfg

[GoogleCodeExporter]

Same thing here.

Original comment by Meral.Ha...@gmail.com on 11 Aug 2010 at 3:03

[GoogleCodeExporter]

We need to clarify one thing: can you start any track or just zandvoort ?
Let's make this test: run the game, on tab [Game] select track: Test2-Asphalt, 
click the button [Change Track], now hit Alt-F4 (close game). Run the game 
again, press New Game - it should start on the Test2-Asphalt track. This is the 
map with smallest terrain (129). Repeat this scenario for Jungle1-T track (its 
513) and for Savannah1 (1025) - never by pressing New Game more than once.
If those tracks can load just after game's start it's ok - then the reloading 
of track has issues. But if the game won't start on any other tracks, just 
zandvoort this is a hardware issue, meaning the terrain can't be created on 
your gpu (even the smallest one). Strange is that there is nothing in the log 
about it. Also you can check if both render system give the same result (at 
Ogre dialog). But I would suspect that GeForce 6200 is way below minimum 
requirements for terrain.

The game still needs a cleaner rebuild of all dll's and a check on debug 
version which never run without errors. This will probably be the aim of next 
release to clean. Version 4 was a bit quicker mainly to solve the crash at 
startup problem and let people run the game finally.

Original comment by Cry...@gmail.com on 11 Aug 2010 at 7:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm sorry to disappoint, but I can't reproduce the error anymore.

Since I think a GTX 270 should be able to load bigger terrains, I just started 
the game loaded zandvoort and drove around a few corners. Then I loaded one 
track after the other without restarting the game and it worked.

Original comment by Meral.Ha...@gmail.com on 12 Aug 2010 at 10:06

[GoogleCodeExporter]

This is good, just as I tested on my GeForce 8800 and on 9600.

Original comment by Cry...@gmail.com on 12 Aug 2010 at 10:16

• Changed state: Opened

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 14 Aug 2010 at 8:16

• Changed state: Solved

[GoogleCodeExporter]

Heya,

been away for a while. I can still reproduce this bug.

If I understand you correctly, you want me to change the track, exit game, then 
run the game again and race on the previously selected track. That does work 
indeed.

What doesn't work is when you're already in game and on a track, then you exit 
to game's menu and change the track selection and then press 'New Game' without 
exiting the game first. I actually get a frozen frame from the new track with 
the car on it, then the screen flickers and crashes.

If the graphics card is to blame due to not enough memory, perhaps the old 
track is still in there?

To test that, I ran the game, drove around for a bit on the smallest track, 
then tried to start a new race on the same track. Again, crash.

Otherwise, all the tracks work fine on the Geforce 6200, as long as you restart 
the entire game every time you want to restart your race.

Original comment by oskar.ko...@gmail.com on 29 Aug 2010 at 7:58

[GoogleCodeExporter]

This is odd, looks like it's not graphics card fault or it's memory. Maybe 
something in recreating physics. But if you see something from the new track, 
the rest is still loading, so could be trees too.
Anyway since this isn't a big error and I'm unable to reproduce it (it probably 
won't happen on GeForce 7800 and above) I can't fix it.
I'm also now more focused in putting together an editor for tracks.

Original comment by Cry...@gmail.com on 2 Sep 2010 at 4:38

[GoogleCodeExporter]

I had this problem in v3, but v4 fixes it (and is much more stable all round). 
Thanks

Original comment by timothyf...@gmail.com on 2 Sep 2010 at 6:46

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 12 Dec 2010 at 6:58

• Changed state: Fixed