OpenXR motion compensation not working
I'm using a motion platform controlled by SimHub, which incorporates motion compensation from an OpenXR API layer. Enabling this layer crashes the game to desktop before it starts. Everything else w...
Forum Discussion
@jazzbutter 10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000% bro!
We still cannot use motion compensation. The author of OpenXR Motion Compensation https://github.com/BuzzteeBear/OpenXR-MotionCompensation says that the anti-cheat is interfering. EA needs to fix on their side
The new v0.3.9.0 of the OpenXR motion compensation layer now has signed binaries, which should fix this problem. I'm away from home on holidays and haven't been able to test it yet. Anyone else can confirm if this now works properly?
Update: It does seem to work now, with the new version. I have only tested it on a non-motion rig, so whether the motion compensation actually works or not is still untested, but the game loads and plays just fine with the motion compensation layer installed and running. Which tells me that this is probably properly fixed now, with the signed binaries. Happy days!
Did you confirm this was working? I just got a motion rig and installed v0.3.9.0 of the OpenXR motion compensation. After that EA WRC would not launch past the initial splash screen. I uninstalled OpenXR MC and then EA WRC worked fine again.
With motion compensation installed I get this error in the Windows Event Viewer:
EAAntiCheatService
Failed to obtain Origin directoryI know this error can occur if the game is not installed in the default Steam path, but I have the game installed to the default C:\Program Files (x86)\Steam\steamapps\common\EA SPORTS WRC folder, so it's not that.
So the EAAntiCheatService error in the event log was a bit of a red herring, I found I got the same error regardless even with OXRMC uninstalled and the game still works.
I did manage to get OXRMC working in the end. The issue seems to be just a problem with the latest v0.3.9.0. Using the previous v0.3.8.0 that has unsigned binaries works perfectly. I don't think the driver signing has anything to do with any problems.
Featured Places
