New game fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open StuntRally
2. Start a new game.
3. Open the ingame options.
4. Start a new game.

What is the expected output? What do you see instead?
A new game should start. Instead, the track starts to load, then the game 
crashes.

What version of the product are you using? On what operating system?
StuntRally v3 on Wine 1.2 on Mac OS X 10.6.4

Original issue reported on code.google.com by timothyf...@gmail.com on 2 Aug 2010 at 11:05

[GoogleCodeExporter]

I had no idea it would be even possible to run this on Mac.
But this doesn't help me, if I you had found a crash please include:
_log.txt, _ogre.log, _ogreset.cfg, _game.cfg
those files are in the same dir where StuntRally.exe
You can zip them and attach here, this way maybe I will know what went wrong.

Original comment by Cry...@gmail.com on 5 Aug 2010 at 5:05

[GoogleCodeExporter]

The wonders of Wine! Here are the logs.

Original comment by timothyf...@gmail.com on 6 Aug 2010 at 10:26

Attachments:

• Logs.zip

[GoogleCodeExporter]

So you run it, and you can drive at first start, just clicking new game crashes 
the game ?
If that's the case its probably something wrong in reloading stuff.
Did you try both rendering systems DirectX/GL, the same behaviour ?
My log is poor commented right now I can't see what crashes the game.
Anyway you have ATI Radeon X1600 ? Isn't the performance (Fps) to low to play ?

Original comment by Cry...@gmail.com on 6 Aug 2010 at 1:20

[GoogleCodeExporter]

Yep. DirectX gives the exception 
'OGRE EXEPTION(3:RenderingAPIException): D3DXLoadSurfaceFromMemory failed in 
D3D9HardwarePixelBuffer::blitFromMemory at 
..\..\..\ogre-svn\RenderSystems\Direct3D9\src\OgreD3D9HardwarePixelBuffer.cpp 
(line 663)
and the logs attached.
I'm guessing this is something Mac based.
Yeah, it's the built in graphics card in my 2006 iMac. If I turn the view 
distance right down and reflections and shadows off I can get >10fps most of 
the time.

Original comment by timothyf...@gmail.com on 6 Aug 2010 at 6:13

Attachments:

• [DirectX logs.zip](https://storage.googleapis.com/google-code-attachments/vdrift-ogre/issue-2/comment-4/DirectX logs.zip)

[GoogleCodeExporter]

Well, I would say this is reallty too low, I feel comfortable playing at 60 
fps, 30 fps is acceptable but below 20 it can't be played. The current 
rendering requires some graphic power, that laptop and build-in cards just 
can't handle, so your card is definitely below minimal requirements.
If the zandvoort starts and other with terrain don't this just means that 
terrain requires more than there it is (and would render slow if at all). 
Strange is that it crashes right at start in making fonts, which actually GL 
has passed.
But since this is rather a hardware problem I'm closing it.

Original comment by Cry...@gmail.com on 6 Aug 2010 at 6:55

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 6 Aug 2010 at 7:02

• Changed state: WontFix

[GoogleCodeExporter]

I agree the DirectX and low fps problems are hardware, but I don't see that the 
restart problem is.

Original comment by timothyf...@gmail.com on 6 Aug 2010 at 8:28

[GoogleCodeExporter]

This could mean that there are no resources (system memory or graphics card 
memory) to create the terrain. If it would happen on (at least) HD 3870 or GF 
8600 I would consider it my error.

Original comment by Cry...@gmail.com on 8 Aug 2010 at 11:07

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 8 May 2011 at 1:44

• Added labels: Type-Crash
• Removed labels: Type-Defect

[GoogleCodeExporter]

I CANT OPEN THE GAME! ;-;

Original comment by Gantanim...@gmail.com on 10 Mar 2015 at 4:35