• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.

HP Reverb Controllers failed

Robbswam

New member
Joined
Dec 1, 2020
Messages
5
Reactions
1
I can not get the HP Revrb 2 controllers to work in STEAM VR very well.. and they do not work at all in VAM.. can anyone point me towards a solution ?
 
There are some settings in VAM itself that can cause this. I had an issue with my right controller, took forever to figure out.
 
any tip about reverb is welcome (considering the rarity of the argument in all Vam forums, besides negative critics)
That's been my only issue really. The software sucks balls compared to Occulus and it's just less stable but the video quality is better which is what really matters for VAM. (as opposed to gaming) I also hate the garden hose cord.
 
A combo of these two posts helped:

The last post in this thread has the important info. I feel like I had to use desktop mode for some of it.


It was sort of finicky, but if you play around with it a bit you Should be able to save your own (persistent) defaults.
 
Last edited:
my issue was resolved when I reloaded and resynchronized VAM with Steam = it was in different folders, and couldnt find the correct pathways for the dlls and drivers - so the controllers worked in steam but not in VAM = now they work well
 
i actually had to reload the entire program from scratch to get them to be recognized. I installed to C: and then transferred the entire vam package into a seperate drive, and than migrated all the saves, skins, textures, looks, morphs and scenes etc etc... from the previous build.
 
glad you solved the issue. The problem with my reverb g2 was just that "action" (using the steam word) of showing targets controls when in edit mode and pressing the button B: it works, yes, but just always temporary so that there is not the time to aim and select the control I must edit. With that pc keyboard shortcut (hot key T) now I can see all the controls static in VR and so I can select a target as I could do easy with my old oculus rift s. But of course this is not a so good compromise. Maybe I should check in my windows 10 register if there is the same issue with Steam vam folder directory.

I ran into this too, and set mine up so that "show control nodes" is mapped to the left VR controller and grab is mapped to the right. I think both triggers are mapped to select, but I don't edit in VR much so I can't remember off the top of my head. IDK if you've run into this, but the control nodes only show if the menu is open. Being in edit mode isn't enough. If the menu isn't open they only show if you point directly at them, which isn't exactly helpful.
 
Back
Top Bottom