OpenVR-MotionCompensation

Hi ,
Try to change this value : Center of rotation ( Heave ) like -1500 to -2000 or +1500 to +2200
Depend the game somtime is -1000 . that work for me but may be not for you !
Good chance !

Thank you so much for the response. Please excuse my ignorance, but where is this setting located? I don't see it anywhere in OpenVR-MC or SRS, but I'm still getting used to SRS.

Sorry for the delay . I use FlyPT Mover

Thanks for the response. If I can't get this working properly with SRS, I might give FlyPT a try. Or I will just go back to SimTools.

I do not understand, I use very basic glasses, the lenovo explorer, and never need these programs, if when the car moves a lot if the track is bumpy, but in real life your eyes also move at those speeds, even but, honestly, it seems real to me like that, without movement compensation and I never get bothered.

Same for me, but I haven't tried a flight sim in VR yet (most people I've seen here say that motion compensation is important for flight sims). I find that it feels natual for the sim to tilt side to side without any compensation but I can imagine pitch motion being an issue at high ranges of motion.

Dear Dschadu, I bought a wit motion tilt sensor, to send the angles to openvrmc but I found out that I can't use it with sim tools. Is there hope to implement support in the near future?

It would need a custom driver. An example is available at https://github.com/Dschadu/motionPose You would have to adjust it to take values from your motion sensor.

I personally want to make a driver that takes values from a com port, but it is not progressing due to lack of time and programming skill. No time to dive into it.

thanks for the info friend. have you used this driver you mentioned? how was the experience?

Yesterday morning i installed the openvr motioncompensation 0.3.5 with one of my indexcontrollers attached to the seat of my p3dof. I tried it in MFS2020 and everything worked perfect. Later in the evening when i was gonna play again it didnt work. As soon as the seat moves i fly around really hard in the cockpit. Like alot worse then without motioncompensation. Ive tried reinstalling steamvr, and the motioncomp but the same thing happens over and over. What could have gone wrong?

I got it working. It was somehow the placement of the controller. Even if it had worked earlier. I moved it upwards abit and suddenly it was working again.

I was wondering if there is a virtual tracker plugin/interface somewhere for simtools ? or is it planned for v3 ?

Just tried openvrmc + SRS + witmotion tracker. Works extremely well!! One issue I’m having is trouble reading the VR menus in AMS2 because the SRS “joystick” markers are on the way in VR. Anyone know how to turn these off?

@Dschadu , I have constructed a tracker of my own. It is two potentiometers that measure pitch and roll of my Dofreality 2dof platform. An arduino converts the measurements to degrees, opentrack bridges between serial comms and udp, which then feeds into FlyPT Mover. FlyPT Mover then forwards the angles via MMF to OVRMC.

This gives me a stable, vibration proof and to the tenth of degree accurate reading of my pose.

My measurement output is in positive/negative degrees of roll and pitch, horizontal is 0 degrees. In Flypt Mover I can see the values arrive as intended.

The Dofreality 2dof has a single cardanic pivot point just below the seat. In OVRMC I have positioned the arrows origin (intersection) exactly in the pivot.

Two problems:
1- Although I am feeding the pose in degrees into OVMRC, the compensation is way too big. I feel it is quite accurate when I scale down the degree values to 35%. This will compensate for roll and pitch.
2- Although I am only feeding pitch and roll into OVRMC, I am getting a massive movement in heave influenced by the pitch value, and a massive sway depending on the roll value. I am feeding 0 heave and 0 sway to OVRMC. So I am moving violently around the cockpit in dimensions my rig is not moving in.

What is going on?

Interesting that you are using opentrack to send the arduino serial data to mover via UDP. I am heading down the path of putting an encoder on my rig for the same reason as you and I just confirmed using a leonardo as a joystick emulator allows me to pull the data into mover that way. I wonder if one of these methods has lower latency.

As for the issues you are observing I am no expert but it sounds like the center of rotation is off (which was a bug for lighthouse headsets like the index). I think that is solved now, are you using an older version of OVRMC?

I think you are on 0.3.5? Try 0.3.6. this bug should be fixed.
No release yet, as I always forget to do so... Since months... Sorry

What I did was just do the angle calculation (a simple multiplication) on the arduino, but other than that just blast out the raw measurements to opentrack, since it has its own filtering. I am also measuring vibration (or at least my pots are vibrating) , which needs filtering. Since OT offers filtering, I thought it might give better performance to do that on the i12900K rather than on the Atmel . In my joystick scripts however, I use this library for filtering, together with this library for the joystick output which works well for me. And OVRMC itself also offers some filtering (which I have pretty much reduced to a minimum right now).

Never cared about the latency of my joystick scripts. My current pose measuring script puts out 3000 frames of measurements per second when letting it run as fast as it can, so there is no discernable latency there. Usually my joystick scripts put out 30 to 50 positions per second, never tried to let them run free, probably the included filtering will slow them down quite a bit. OTOH, opentrack filtering will also induce some delay. Due to the apparent bug in OVRMC, it has been hard to judge end-to-end latency, but there appears to be some. That can also be Flyptmover, doesn't need to be Opentrack.

Best approach would be to incorporate serial communication (and maybe a filter) on the basis of this, but I have been staring at it for some time, and it is just above my paygrade. I am not an IT professional.

I am still on the current release version v0.3.5. Would appreciate a compiled version of v0.3.6.

Thanks for your efforts, still on 0.3.5, a release of 0.3.6 would be appreciated!

New OVRMC Version 0.3.6 is now released!

This release should finally fix the virtual tracker behaviour.

Direct download: https://dschadu.de/binary/OpenVR-MotionCompensation_0_3_6.exe
GitHub: https://github.com/openvrmc/OpenVR-MotionCompensation/releases/tag/0.3.6