search

Cxbx-Reloaded / game-compatibility

Cxbx-Reloaded game compatibilty list, using GitHub issues
GNU General Public License v2.0
115 stars 29 forks source link

TechCertGame [FFFF4004] [1.1048576] #107

Open PatrickvL opened 7 years ago

PatrickvL commented 7 years ago

Issues

From @furrya on May 6, 2017 4:8

Cxbx-Reloaded Version 8c9f308f (May 5 2017) crashes with error screenshot_3 screenshot_4 screenshot_5 KrnlDebug.txt Xbe.txt

Copied from original issue: Cxbx-Reloaded/Cxbx-Reloaded#445

PatrickvL commented 7 years ago

From @LukeUsher on May 7, 2017 18:23

Renamed to include XDK version as there are multiple versions of TechCertGame

PatrickvL commented 7 years ago

From @jarupxx on May 9, 2017 11:50

Basically, DirectSound_CDirectSoundVoice_Use3DVoiceData is followed by DirectSound.CDirectSoundBufferSettings.SetNotificationPositions. Therefore, adding OOVPA of IDirectSoundBuffer_SetNotificationPositions probably will work.

Voxel9 commented 7 years ago

So I've noticed something a bit peculiar... In TechCertGame 4627, when you enable vibration in options, when starting the game it will just either crash or freeze. But when disabling vibration, the demo is fully functional (with the sound issues still of course).

You can see what I'm talking about here https://youtu.be/dTjb2Ns6y04

Why would the vibration option have an impact on the emulation like this?

EDIT: Just tested 5849 and 5558; both show same symptoms.

LukeUsher commented 7 years ago

That's rather interesting. Vibration/Force Feedback is not emulated, but it shouldn't cause a crash, it should just be ignored. This could be a missing patch, needs investigation.

BelleNottelling commented 7 years ago

Hmm was it a mistake for me to add the audio issue tag here? I figured that because it was a DirectSound error I'd be correct

LukeUsher commented 7 years ago

Maybe, but maybe not.

The function name in the error message is not always the function the crash happens in, but in fact the nearest function we have an OOVPA for, it's impossible to log function names that we don't have in the OOVPA database, so it's not always a good idea to assume it's correct.

That said, the fact that the exception occurred only 0x18 bytes away from the mentioned function, implies that it could be directsound-related crash. This is purely speculation, but, perhaps there's a sound that plays when vibration is enabled.

It needs further investigation

Margen67 commented 4 years ago

New xbe dumps are needed in order to fix the issue title. I will reopen this once they are provided.