- This topic has 5 replies, 2 voices, and was last updated Aug 28, 2025 7:20pm by
.
-
Posts
-
Kingdom CD1 stopped working after upgrading vorpX to 25.1 – the game won’t start. I had to install a previous version.
Can’t replicate that here. The only weird thing I encountered is that the first loading screen only gets displayed in the left eye when the game is launched with G3D activated. That definitely wasn’t the case with older vorpX versions. Fixes itself once the main menu is reached though, so not really an issue.
Please provide more detail. What exactly happens? Is an error message displayed?
Ideally create a trouble shoot data archive in the config app and send that together with your more detailed issue description to support at vorpx dot com.
Thanks for response.
A few minutes ago, after launching vorpX, it automatically updated to version 25.1.0, which caused Kingdom Come Deliverance 1 to stop launching. Without the “use alternate hooking method” option, which was disabled by default in the older version of the application, vorpX won’t connect to the game. It causes the GUI to behave jerkily when the game starts. With the “use alternate hooking method” option enabled, the game starts, vorpX displays the message “attaching to Kingdomcome.exe,” and then crashes. Without the vorpX service running, the game (Epic version) runs normally. I don’t want to troubleshoot this version of vorpX because I don’t want to waste my time. I want to have access to the previous version that KCD1 works with. And what do I see on the website? – DOWNLOAD NOT AVAILABLE ANYMORE The cutting edge branch and the regular branch have been reunited with vorpX 25.1.0KCD1 works perfectly fine with vorpX 25.1.0.
If for some reason it doesn’t hook on your machine, which would be fairly weird, wait until the trouble shoot dialog appears and try the trouble shoot options that are offered there.
If that doesn’t help, try a factory reset (config app > trouble shooting page).
Thank you for response.
Resolved by chatGPT :)
The culprit was the OpenXR “Quad-Views Foveated” layer (Mbucchia). The log shows a repeatable crash right at the moment the OpenXR device is initializing, and the stack trace points to XR_APILAYER_MBUCCHIA_quad_views_foveated.dll → “ACCESS_VIOLATION at 0x0”. This happens right after OpenXRDevice: Initializing device.
If you happen to use SteamVR as your OpenXR runtime, configure vorpX to use SteamVR directly instead.
Valve’s OpenXR implementation is not only outdated (i.e. doesn’t support the latest OpenXR version). It also, spec violation one, has no 32-bit support for older games. And, just as bad, messes up two OpenXR functions, spec violation two, that are used to snychronize frame timing in more complex multithreaded environments, causing severe FPS drops with vorpX compared to working OpenXR implementations or using SteamVR directly.
They ignore reports from several devs in both regards since several years, so they probably won’t fix any of that.
TLDR: Valve’s OpenXR objectively sucks. Do not use.
- You must be logged in to reply to this topic.