Ephinea PSOBB crashes with add-on plugin and DXVK artifact build which addresses #3117 about dxvk HOT 6 OPEN

I tried using the addon on Linux through Proton with a AMD GPU and couldn't get it to crash. But will try also on Windows.

from dxvk.

I tried using the addon on Linux through Proton with a AMD GPU and couldn't get it to crash. But will try also on Windows.

Yep, you're right. We have had a couple of people test on Linux and it appears fine there with Proton or WINE.

This appears to be a Windows only issue. It's weird that this happens when the addon is used with the new DXVK under Windows. I know the addon loads through dinput8.dll... Does DXVK use parts of DirectInput?

I'd love to provide more data to you, but the Event Viewer log when the game crashes just has some bogus offset data in it.

Example:

Faulting application name: PsoBB.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xffff06fb
Faulting process id: 0x0x4C30
Faulting application start time: 0x0x1DAAC80C859B4A3
Faulting application path: C:\Users\Terry\EphineaPSO\PsoBB.exe
Faulting module path: unknown
Report Id: efed9e40-fb2b-4e07-bc25-123be82fdd54
Faulting package full name:
Faulting package-relative application ID:

That fault offset is crazy. So I couldn't look at the code in memory to attempt to help debug.

Another time it was 0xffff132d, another time 0xffff07d9, and another time 0xffff1327.

The offset it crashes on isn't useful at all.

I've tried compiling the game's DLL without VMPROTECT as well to see if VMP hated DXVK + addon combo, but that didn't help at all. Still crashed.

I've even tried changing the addon initialization LUA to do nothing, but it doesn't even appear we're getting to the part where the addon tries to initialize. Crash seems to be happening way before.

from dxvk.

Might be worth trying with #4026

from dxvk.

I know the addon loads through dinput8.dll... Does DXVK use parts of DirectInput?

It does not. However, a lot of mods/game fixes will load using dinput8.dll and override various unrelated method calls. Or, better said, dinput(8) is a common way to inject custom code into a process. Without access to the source code of the plugin it's rather hard to tell if it's messing with anything dxvk would care about.

Edit: Noticed you linked to a GitHub page above, and if that's the pulgin in question here, it looks capable of doing a lot of potentially problematic things. Why exactly that causes an issue with dxvk on Windows is anyone's guess.

from dxvk.

Hello! Sorry for the late reply. I've had a busy day and finally got around to setting up an environment to compile DXVK and add the changes from #4026 into it. I also got the quick commit that was done today for "Fix strange type in dynamic vertex upload"... ANYHOW, compiling all that, with both files updated, the addon still crashes in Windows with DXVK. 🤷

It's not a big deal, I suppose people have other API choices like D3D8, 9 (through 8to9), 11 and 12 (through dgVoodoo) in Windows for PSOBB that work with the addon, so not a big deal. Seems fine on Linux which is probably what DXVK is primarily for anyhow.

Maybe someday it'll be figured out... and then maybe not. Probably will have to work with the addon devs on this one.

Anyhow, thanks for your input!

from dxvk.

I've tried on Windows now but still haven't gotten it to crash

Do you apply any specific settings?
Also were the other Windows testers also using Nvidia?

from dxvk.