Pimax 8KX + OVRMC (or YawVR Tracker) for motion compensation

Hi, I’ve have a problem with the OVRMC and with the YawVR Tracker (of the Yaw2).

I’ve the Pitool .275 (the .277 gave me a lot of SteamVR errors), and the problem is that the OVRMC didn’t work with it. I follow all the steps correctly and it activates, but when a yaw movement happend, the borders of the screen turns black and the image didn’t follow the headset (the same configuration is working fine with a Quest 2).

I think that this is a rendering issue between the Pimax Driver and the OVRMC, because I had the same behaviour with a Quest 2 + VD before disable the VD Rendering pose.

I’ve also tried to used the PiTool motion compensation option, but it didn’t recognice the YawVR Tracker, only the Index Controllers. In SteamVR all the components are up and running (Pimax 8KX, Index Controllers, Base Stations and YawVR Tracker).

1 Like

He has the YawVR 1 device. But @vrgamerdude might have some ideas.

Let me know if I should cancel my Yaw2 order. Also have an 8K and damnit if I’m out 2k for something that doesn’t play nice with Pimax.

Wait, why don’t you just use PiTool MC with the Index Controller as a reference tracker?

OVRMC is buggy at the best of times - I use it daily but only due to a lack of an alternative.

1 Like

Because to work with it, the controller must be in a fixed position solidary with the Yaw2 (to act as a tracker).

The Yaw2 provide a virtual tracker which already send the position of the simulator to SteamVR, so it’s a better solution. The only thing left is that the PiTool software support it as a tracker input.

1 Like

So fix the Controller to your YawVR?

Virtual trackers are great because they forego all the troubles coming from occlusion, vibration etc. but, as you noticed, they can be difficult to get running in sw.

Alternatively you could use SRS and use their witmotion MC solution.

1 Like

The virtual tracker is working fine, as SteamVR and the OVRMC recognices it and receive the data it send, the only issue left is the support from Pimax.

The OVRMC is working fine with other headset, so it demonstrate that the Virtual Tracker is good enough. The problem is an incompatibility issue between the OVRMC and the Pimax drivers (which are the responsibles for the rendering).

The SRS motion compensation is a virtual tracker as well and it use the OVRMC, so I’m pretty sure that the issues will be the same.

That would mean no Pimax user would be able to use SRS and OVRMC. Which is not the case.


That’s why I writed this post, to know how if other Pimax users have similar issues with the OVRMC, and if not, how they configure it (Or if they uses other motion compensation software).

Until now the only answer I found is from @vrgamerdude, but he uses the PiTool MC with a Vive tracker, not the OVRMC.

So I’m asking to @PimaxQuorra if he could talk to the SW team to study the possibility of adding the Virtual Trackers as a input for the PiTool MC.


Well I haven’t used PiTool for more than a year now but I can definitely confirm that I was able to use my 8KX without a hitch together with OVRMC via both the SRS witmotion tracker as well as an Index controller.

I do not know if PiTool has since lost that functionality but I‘d be surprised if it did.

My money is on a specific issue with the YawVR virtual tracker and its translation into the correct pose once PiTool is in the mix.

1 Like

Oh that’s interesting.

Which version of OVRMC do you use and which steps do you follow to enable it?

I’ve also use the SRS for racing games, but I don’t have a witmotion tracker, so that’s why I wanted to use the YawVR Virtual Tracker (as the OVRMC recogniced it and it is working fine with the Quest 2 + VD).

1 Like

3.6 now, with the 8KX it was 3.5 with a custom .dll from the discord.

Check the discord for in depth help:


Please file a ticket and allows our tech specialist to check it for you.
Could you please download the tool and export logs to help us analyze the issue?


So glad to see you guys considering support for Motion compensation to be important! Thanks for your efforts!

1 Like

Today I could save a Log and open a ticket explaining the problem.

I hope that the team could solve this issue.

Also I’ve tried with the latest PiTool 280 (Beta), and the problem is still there.