OpenVR-MotionCompensation

My thoughts exactly. I've been away for RL reasons and will continue to be for some time so I didn't know any of this was happening! Dschadu you are a true hero to this community! I do still absolutely believe that all of us who will benefit from this should pool together money to pay you for your work. If you refuse that, maybe we can send you a gift.

Truly, words are not enough!

Exiting news!
First: I launched a new website! It contains all information about OVRMC. Its more user-friendly than GitHub and is easier for me to keep up to date:
https://ovrmc.dschadu.de/

OVRMC v0.3.1 is here!
https://ovrmc.dschadu.de/en/Download

Changes:

• Removed unnecessary calculation if set Zero mode is active
• Moved all settings to a new page
• Added shortcut to Enable / Disable Motion Compensation
• Added shortcut to reset Zero Pose
• Added Offset settings for virtual drivers
• Added "press and hold" function to some buttons to speed up value changes
• Changed the MMF to a new format (v1)
• Fixed occasionally jumps in motion compensation
• Fixed bug in the acceleration calculation
• Fixed virtual keyboard position
• Fixed shortcut save behavior (was saved 2 times)

Please check https://ovrmc.dschadu.de/en/kownissues for Known Issues!

FlyPT Mover Virtual Tracker release:
https://ovrmc.dschadu.de/en/virtualdevice
This makes a physical tracker unnecessary if you use FlyPT Mover as motion cuing software!


Of course, if you like to compile the software yourself or you want to download it from GitHub:
https://github.com/openvrmc/OpenVR-MotionCompensation/releases
https://github.com/Dschadu/motionPose/releases/tag/v0.2.1

Any feedback is welcome! If you need help, you can ask here or join our Discord!

Dschadu, might you provide a Patreon or direct PayPal link so those of us who choose to do so can send you some money (monthly or single tip) as a thank you for creating and maintaining this? I can not afford to contribute as much as I would like, but I would really like the opportunity to send what I comfortably can. =)

This is amazing work, thank you so much @Dschadu! I checked your website and couldn’t find a PayPal link to show my gratitude, please do provide one, this is outstanding work.

Under supported devices I see that combining a WMR HMD with a SteamVR tracker is shown as ‚works‘, can someone please explicitly confirm? If so, that will make me keeping my G2 come October much more likely.

@Twak3r actually your WMR controller will now work! At least one Reverb user is doing it now and says it works flawlessly. =)

Reverb motion compensation confirmed 100%, with it's own native controller mounted in front of you.

I'm trying to convince our modest saviour to add the paypal link to his sig and website. Here it is: https://www.paypal.com/donate/?cmd=_s-xclick&hosted_button_id=SEGY77GY3H5K6&source=url

Thanks, done!

It‘s fantastic that I‘ll be able to use the WMR controller for this, now I‘ll have to figure out a proper mount as well as an energy supply solution to power those insanely hungry LEDs.

Thanks Trip, being probably the Reverb user you refer to, having logged in the past 3 days many wonderful and exciting full 6 DoF flying hours in IL-2 with Reverb and WMR controller in front of me (NO lighthouses!), I can only agree with you.
Motion Platforms and VR are expensive hobbies, even more so in combination, and many of us have invested hundreds or even thousands of $ for hardware. But, as we all know, the return value in joy heavily depends on the right software.
Therefore the work of the non-professionals working in spare time for the community really deserves some reward!
So let's show our appreciation of that work!

@J-1775 You guess correctly my friend. =) Also, very well said!



@twack3r Hot-wiring the controller should be no big deal. I'd basically 3D print a fake battery with contacts at the ends and run a pair of wires out of it. What output power supply you need is easily determined based on the battery. Probably 1.5 volts (single standard non-rechargeable AA battery). I'm sure the internet will provide an appropriate power supply for the job.

I'd volunteer to make the fake batteries, but my 3D printer is packed up along with nearly everything else I own as I am in the middle of moving. It will be some time before I've got things back up and running.

Before (vive tracker behind headrest):
and after (now)
You see, a rough and ready "temporary" solution, but works so well, that I probably leave it like that...
My seat is isolated against the base, thus NOW I can power up Jetseat and Buttkicker about as much as I want, with almost lowest filter settings.

>>now I‘ll have to figure out a proper mount as well as an energy supply solution to power those insanely hungry LEDs
@twack3r: I use this special kind of re-charagabels RoHS ( the ones with the inbuilt USB micro port) with very steady 1.5V output. They only have 1600 mAh, thus I have to recharge them after about every 30min Beat Saber session, but obviously the FF is most power hungry, as just for tracking they hold much longer! And charging is quite fast. They're expensive, however, thus maybe you look into Trip's solution.

@Dschadu: Where shall we report issues, right here or at Github? I moved straight from 0.2.3 to 0.3.1 (dash still showing "0.3.0", but minor issue) and every time I hit "apply" I had a "Set Device Mode" error: "Device not found".
However, when I removed my left Reverb controller and used the right one, everything behaved as expected! Not a real issue, but somehow a bit "strange".

d’oh missed this, will try with the new values. Thanks so much!

@J-1775 Have you had any problems with the WMR controller shutting down on you? Others are having this problem and if you aren't maybe we can figure out how to help them get the same results as you.

I'm not certain whether I correctly understand the question. The tracked Reverb controller shutting off to often or going into standby?
Indeed, the Reverb Controller shut off much earlier than a Vive tracker. However, I remember sometimes blindly searching for the Vive tracker and its button behind the headrest...
I activate OVRMC very late, just before I takeoff or taxi and check that the Controller's LEDs are on when I press "apply". Once the platform is moving, the Controller stays activated usually for as long as I fly.
Usually I test the compensation by rolling a few yards and then hitting the brakes to make the platform pitch over.
It happens that I have to remove the checkmark, hit apply, put in the checkmark again and once more "apply". A good signal that motion compensation has kicked in is when I have to recenter.
Sorry if I misunderstood the question...

Yes you understood correctly. There are reports of these controllers turning off during "smooth parts" of simulator usage. Could be a problem specific to smaller travel sims or non-6DOF maybe?

To start with: the Reverb controller is the only WMV controller I know. Assuming that other controllers show similar behaviour it's certainly fair to say the Vive trackers are easier to use for an MC use case! And, of course, they have a better form factor, are easier to attach.
While setting up a new flight I have taken the habit of tapping one of the controller's buttons to keep it active. I noticed no side effects with that. However unticking the check box in OVRMC and re-ticking before a flight should also help.
I remember one landing where MC was gone. Maybe that was after a long steady approach?
My experience so far is restricted to IL-2, where I always have "Turbulence" set to at least 1 m/s, in heavier aircraft to 2 m/s. Maybe that is enough to keep the controller "alive"?
That said, we may also assume that the individual platform probably makes some difference. I use a GFORCE FACTORY 6 DoF.
I'd also assume that racing exerts a steadier flow of telemetry data than a steady flight does...

There is indeed more on the downside from switching from trackers to WMV controllers, especially tracking FOV. I attached mine on the left side of the joystick base. Whereas I can turn my head to the left quite far, turning it far to the right side may interrupt the tracking. However, the Reverb G2 will have increased tracking FOV and also redesigned controllers. Thus for me it's "don't worry, wait"!

However, if early controller shut off is a permanent problem for a number of us, we should maybe open a new dedicated thread (or is there already one?), as the problem is not directly joint to the OVRMC software. On the contrary, with inbuilt keybinding for switching MC on and off it probably has all features we can ask for to ease our problem.

FYI, my understanding is that all WMR VR sets have identical controllers. That is, until Reverb G2 comes out anyway. Lot of excitement for better WMR hand controllers finally becoming available, and they will be compatible with all WMR HMD's.

I'm suggesting Bikkies come chat with you to see if he can sort his issues with your help.

This is exactly what has deeply intrigued me for a long time! Not that I'd understand it now (and don't waste any time by trying to explain it any deeper to a dummy!), but I'm glad to hear that you guys dealt with this problem and that some immensely clever programmer/analyzer obviously even found a solution how to "neutralize" it! THUMBS UP!

The latest version is truly freaking AWESOME!

The software compensation works fantastic with mover. Beyond words guys!

Thank you for creating this plugin - I am however having an issue when trying to apply my settings to the virtual tracker. It just keeps giving me the error “Device not found.” I have the proper device selected from the drop down menu. I have FlyPT outputting and the virtual tracker shows up in the steam VR device menu. I have the XYZ axis placed correctly on my rig. Any other ideas why I might be getting this error? Thanks in advance.