Game closes after splash screen

[defiantsquid1]

GeneralsVR version

v0.2.0-alpha

Headset and connection

Oculus Rift, wired

GPU

Radeon Pro Vega 64

What happened?

First of all let me say thank you for even attempting this! Apologies in advance if I've missed a step in my excitement to play, and for my convoluted setup - will share Debug below and some device details in case it's relevant.

Working with an Oculus Rift with a wired connection and Meta Quest Link app. Running Windows 10 through Bootcamp on an iMac Pro (It's not pretty but it mostly works)

Did a fresh install of Generals and Zero Hour on Steam to remove any potential conflicts with GenTool or GenPatcher just in case. After download and setup, clicking the GeneralsVR desktop shortcut or Start command file and selecting Play shows the Zero Hour splash screen with Community Patch 1.04 info, then closes.

Same result with SteamVR open or not, no connection appears to be made to Steam (i.e. it displays 'Play' unchanged) or the headset during this process. I also tried rolling back to v.0.1.6, v0.1.5, and v0.1.4 but no dice.

Thank you!

How can we make it happen again?

No response

Log file

DebugLogFile.txt

[Gonzorro]

Thanks for the detailed report and the log, that made this easy to pin down.

Your log dies right after "Create Direct3D8" with nothing after it and no crash dump, which pointed straight at the DXVK layer. Direct3DCreate8() was hard-crashing instead of failing cleanly on your setup, so the whole process just vanished with no error and no chance to log anything.

I've fixed the crash itself so it now fails gracefully with a proper error message instead of silently closing. That said, this doesn't necessarily mean VR will work on your card. The Radeon Pro Vega 64 via Bootcamp is an unusual combo and the underlying issue may be that its Vulkan driver support isn't solid enough for DXVK to translate through. The fix means you'll actually see an error dialog telling you D3D init failed, instead of the game just disappearing, which should at least confirm what's going on.

This will be in the next release. If you get a chance to test it and it still doesn't work, the error dialog text (or a fresh DebugLogFile.txt) would help me figure out if it's fixable or a hardware ceiling.

Thanks again for sticking with it through the version rollbacks, that kind of thoroughness makes bugs like this way easier to track down.