Virtual Fighter Maneuvers Playtest (4192060)

[her001]

Compatibility Report

• Name of the game with compatibility issues: Virtual Fighter Maneuvers Playtest
• Steam AppID of the game: 4192060

System Information

• GPU: AMD Radeon RX 7800 XT
• Video driver version: Mesa 25.2.7
• Kernel version: 6.17.9
• Link to full system information report as Gist: I can share if needed.
• Proton version: 10.0-3

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [ ] that I have checked whether there are updates for my system available.

Symptoms

When running Proton 10.0-3, the left eye renders fine, but the right eye seems to be in the wrong position and potentially distorted. I am using a Valve Index.

I can attach a Proton log if needed.

Reproduction

1. Launch game (must be in the playtest) with Proton 10.0-3.
2. After the game starts rendering (in the loading screen, in the main menu, and when playing), right eye position and distortion issues should be visible.

Workaround

Switch to Proton Experimental (as of right now, should be the 2025-11-26 version). Afterwards it appears to work fine.

[her001]

Loading into the game again, I am getting the offset right eye/right eye distortion bug even when on Proton Experimental (as well as Proton 10.0-3 and 9.0-4). This time I could not reproduce the working case. There was an update to the game in the time between my initial tests and this one, so I am not testing under the exact same conditions.

I have attached a Proton log, in case it is useful (with .log file extension added on because GitHub wouldn't allow it uncompressed or with the .xz extension): steam-4192060.tar.xz.log

[her001]

Since I shared this in the official Discord for the game, but apparently everyone refuses to write here:

• This is also happening with Nvidia graphics.
• This happened before with Beat Saber: https://github.com/ValveSoftware/Proton/issues/6638
• As with Beat Saber, lowering the render scale works around this. The default render scale was changed in VFM 0.45.1, which should have fixed this. Alternately, a launch option can be used: -renderScale 1.3.