search

ThirteenAG / WidescreenFixesPack

Plugins to make or improve widescreen resolutions support in games, add more features and fix bugs.
https://thirteenag.github.io/wfp
MIT License
2.23k stars 212 forks source link

[GTA SA] Game doesn't start #695

Open Alyxsqrd opened 5 years ago

Alyxsqrd commented 5 years ago

The new widescreen fix update for San Andreas (I'm guessing after you guys ditched wshps.asi) makes gta_sa.exe not start at all on Windows 10 (1903/1803). Here's what I collected from Windows Event Viewer:

Faulting application name: gta_sa.exe, version: 0.0.0.0, time stamp: 0x427101ca
Faulting module name: vorbisfile.dll, version: 1.2.0.0, time stamp: 0x5d0e48a8
Exception code: 0xc0000005
Fault offset: 0x0000134a
Faulting process id: 0x1a40
Faulting application start time: 0x01d538e1e4eb0f96
Faulting application path: C:\Users\<my username>\Desktop\GTA San Andreas\gta_sa.exe
Faulting module path: C:\Users\<my username>\Desktop\GTA San Andreas\vorbisfile.dll
Report Id: cbb07ce9-1c02-4bda-a9b4-b0c79507ede8
Faulting package full name: 
Faulting package-relative application ID:

I can run the game just fine without Widescreen Fix (using the original vorbisfile.dll from the game.)

Help! D:

Alyxsqrd commented 5 years ago

Update: All my drivers are updated, I ran sfc /scannow and DISM commands to fix my system files, but no luck...

ThirteenAG commented 4 years ago

Please provide a crash dump. And try to move the game away from program files.

BusyOne commented 4 years ago

@ThirteenAG Same problem, moving away didn't help. Here is a crash dump: gta_sa.exe.9204.zip (Sorry for bad English if it is.)

Alyxsqrd commented 4 years ago

I don't know how to make a crash dump. Also the game was never in the Program Files folder in the first place. For now I have temporarily replaced the Widescreen Fixes vorbisfile.dll with Silent's ASI Loader (but keeping the Widescreen Fix ASI) and now the game works fine.

ThirteenAG commented 4 years ago

Well, I see a crash inside vorbisfile.dll, but it's hard to debug it because I can't reproduce the problem. It happens here. So it seems like original vorbisfile.dll wasn't loaded for some reason.

If you rename vorbisfile.dll to vorbisHooked.dll, and then use vorbisfile.dll from widescreen fix, does it work that way?

BusyOne commented 4 years ago

Well, I see a crash inside vorbisfile.dll, but it's hard to debug it because I can't reproduce the problem. It happens here. So it seems like original vorbisfile.dll wasn't loaded for some reason.

If you rename vorbisfile.dll to vorbisHooked.dll, and then use vorbisfile.dll from widescreen fix, does it work that way?

@ThirteenAG For me it is worked! (Sorry for bad English if it is.)

ThirteenAG commented 4 years ago

Yeah, weird. It should work in both cases. :/

BusyOne commented 4 years ago

For me on Windows 10 build 1909, it is working now! (Sorry for bad English if it is.)

CrezyDud commented 2 years ago

-n- (Sorry for bad English if it is.)