After quite a bit of testing, the 4 way lighthouse tracking doesn’t appear to be working with the steamVR patch. I was getting issues with some serious drift of one of my controllers or trackers, and at first I thought it was some sort of interferance, but I put back the old steamVR and the issue has gone away. I’m not sure what the patch does, but maybe it doesn’t do everything needed for extra lighthouse devices. Sometimes it would work, but about 75 % of the time it wouldn’t … and one or two trackers/controllers would have that severe drift problem… It seemed like the IMU would drift quite a ways before the lighthouse tracking would correct it. creating a drift pop back into place pattern…
Just thought I’d update in case anyone else was trying this.
The patch actually do nothing for lighthouses. It only fixes crashes for trackers, but SteamVR plugin itself has a lot of hard-coded stuff, so it’s expected that it doesn’t work with additional lighthouses, especially if they get device IDs before controllers and trackers.
SteamVR gives IDs to additional devices as they turned on (starting at 3), so I’m sure that UE4 SteamVR plugin can either work or not depending on a sequence lighthouses and controllers were enabled.
Thanks, yeah I realize this patch wasn’t intended to fix the multiple lighthouse issue at all. Just curious if you think that If I turned the additional lighthouses on last all the time it may work more consistently? I do think order of connection of the devices made a difference in whether it worked or not. If you think there’s an order that it may work more consistently, i may try again. I really need the more robust tracking working for my application…
@YuriNK, I can’t seem to get the Output Pin of the Vive Tracker (pin 1) to register any haptic events from Unreal. I also tried Force Feedback and that didn’t work either. The pin seemed to just sit at 0 volts when it should go up to 3.3v.
Any idea why that might be the case? Could you please help? =)
Hmm, I am currently using the non-beta version of SteamVR and my inputs are working fine. But the haptic *output *pin (pin 1) doesn’t seem to be working - is it working for you?
@YuriNK Thanks for the compiled binaries! This looks great however, when I try it in 4.20 with the current stable SteamVR, I do not get any inputs from the Tracker Pogo. Do you know if it should work on current stable SteamVR?
I am having an issue where my Vive Trackers are sometimes rotating when I start UE4. Before I press the VR Preview button in Unreal I can see them in my headset in the correct position. However, once I press the VR Preview button to start the Unreal scene, some of the trackers rotate around to face the wrong way…and it is the actual orientation of the tracker, not just the display mesh. Any ideas to prevent this?
Where do you see this will be fixed?
All of these bugs will be fixed in 4.21?
bug fix: crash at the engine startup with 4+ Vive Trackers
bug fix: with 3+ Vive Trackers: any input event from the left motion controller cause crash
bug fix: Steam_Generic_Trigger, Steam_Generic_Touchpad, Steam_Generic_Grip, Steam_Generic_Menu events for Vive Trackers declared, but not initialized
bug fix: bad mapping of Vive Trackers to EControllerHand after turning off and on one of the trackers (multiple trackers could be mapped to the same Special_N key)
I wanted to mention that I had narrowed down further on my issue with using 3 vive tracker pucks and the 4 way lighthouse tracking causing a crash. The error seems similar to error we get when using 4+ vive trackers, but I wanted to mention i also noticed there seems to be an additional issue with the order of registering of the 3rd and 4th lighthouses. They must be turned on after the 3 vive trackers are turned on for everything to work correctly, or you will also get a crash. Would it make sense for me to add this to the bug report if they are fixing in 4.21? Can produce the stack trace etc. Would really love to have this fixed same time if they are going to fix it.
Changes were commited to vr-dev branch at github. They implemented new SteamVR input system based on actions and fixed wrong arrays size (caused crashes).
You definitly should report about order of registering of the 3rd and 4th lighthouses.
Thanks good to know. Would you have any suggestions for me on how to report in a way that gets the people working on this to notice quickly? This will be my first bug report so could use any tips you might have. Really want this solved… it’s such a pain to have to turn off the 3rd and 4th lighthouses before registering trackers each time i restart steam VR.
I submitted the bug, but they didn’t add it, and just added a small note of mine to UE-54387 as it has the same stack trace. They said to reply if it’s still an issue with 4.21 preview when it’s out in a couple of weeks. I think it’s separate bug in that it either crashes or works based only on ordering of the lighthouse devices in steamVR (with the same ammount of registered devices). Will try again when 4.21 is out with that version and report again if it’s still broken.
&d=1534437022