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.
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.0