Cyrem wrote:Hey Dege,
Like Jessietail a few pages back, I have a similar issue with LEGO Rock Raiders. v2.53 was the last working version(with some lighting issues) of voodoo before the newer versions caused problems running the game. I have a GTX 970, tried the latest version 2.55.3 and the game locks up a few seconds into a level after the mission briefing disappears.
Not sure if it this helps but this is the last error it x32dbg logs. Tried different levels in case it was particular, same error every time.
- Code: Select all
EXCEPTION_DEBUG_INFO:
dwFirstChance: 1
ExceptionCode: E06D7363 (CPP_EH_EXCEPTION)
ExceptionFlags: 00000001
ExceptionAddress: 75E4DDC2 kernelbase.75E4DDC2
NumberParameters: 3
ExceptionInformation[00]: 19930520
ExceptionInformation[01]: 0019E3AC
ExceptionInformation[02]: 6F8F0570 d3d11.6F8F0570
First chance exception on 75E4DDC2 (E06D7363, CPP_EH_EXCEPTION)!
In the leadup to that (other than Guard page exeptions, the last debug string from voodoo was
- Code: Select all
DebugString: "[dgVoodoo] INFO: DirectDrawSurface (09881510)::QueryInterface: Aggregated Direct3DTexture (17B65AD8) object is created and initialized.\n"
Thanks mate!
I also debugged the problem with DebugView++ and the debug version of dgVoodoo 2.55.3
It (sometimes) reports the (game) error
- Code: Select all
C:\Dev\SourceSafe\gods98_dx6\gods98\src\Files.c(330) : Error in call to File_Open
(Though this might just be the game trying to load a sound file for the item)
But the problems start after the message.
- Code: Select all
D3D11: Removing Device
Then the following warning is spammed:
- Code: Select all
[dgVoodoo] WARNING: DirectDrawSurface (09E21B40)::Lock: Failed, HRESULT: DDERR_GENERIC
From that point onwards, all rendering stops (the game looks frozen). However, the game continues to run and you can still perform actions in the game (indicated by the sounds). The game remains fully operational aside from not showing anything.
There are still a lot of DirectDraw calls that do seem to succeed (don't show signs of failing), but these are not reported as dgVoodoo messages.
As Cyrem stated, this error did not occur under version 2.53
(After a while of gameplay (~15 minutes) I do get this same problem. This might have a different cause however)