The Index thread (please keep to subject)

Ya, I started to have lots of controller issues playing Lone Echo with 2.0 on my Vive Pro.  For now I’ve uninstalled Revive and will just continue using my Rift cv1.  TBH I’ve never had a lot of luck with Revive.  I’m not sure but some SteamVR updates seem to adversely effect it.

Just checked the Revive forum, and it does not seem that many/any had the troubles I experienced ( https://github.com/LibreVR/Revive/issues ). But it easily gets complicated, because v. 2.0 is rather old (from January 30 2020), and when I installed it yesterday both Oculus had launched a new update and SteamVR was recently updated too. And I got both CV1 and Index connected (HDMI + DisplayPort) - so many things could go wrong. 

I installed v. 2.0.0 on top of 1.9.2 - I did not first uninstall 1.9.2 - but I never did that before when upgrading Revive. 
Did notice that my Revive Dash did not update correctly - which was strange. I guess I should have heard the alarm then...

Revive 2.0 does seem a bit different:

I have multiple libraries - and quite a lot of games, maybe Revive choked on that, crashed and caused trouble with my hmds and screen configurations... 

Revive 1.9.2 only registers games on the default Oculus location (where I have like 50 games) - but it also uses Oculus SDK 1.43, which was one of my favorite SDKs before the unified Rift + Quest approach. Maybe not a bad idea to hold on to 1.9.2 for now. 
Note that when Revive works, it does not just work - it works perfectly. Had an interesting experience in Spice and Wolf, where you can set ss to 2.0 in-game - even when using Revive. Using ss 2.0 did cause some stuttering, but setting ss 1.0 in-game and forcing res 200% using SteamVR gave me much better performance (solid 90 fps or really close). I did not check if the same res was used (FpsVR as OTT does not work for the Index), but image quality looked similarly super-sharp using either ss 2.0 or res 200% (but again human perception might be a bad measure, lol). Still it did not seem that ss 2.0 and res 200% was the same, even if it looked similar. Might explain why I often get surprisingly great performance using res 200% with the Index. Need to investigate more. 

Thanks for all that Rune.  I’ll give 1.9.2 a go and see if this helps sort out the controller problem I had with 2.0.

TomCgcmfc said:

Thanks for all that Rune.  I’ll give 1.9.2 a go and see if this helps sort out the controller problem I had with 2.0.

The dude behind Revive once explained that one problem was that changing some settings for one game may negatively affect other games - so finding a great balance was a challenge. Like Defector, which did get worse before it got better etc. In short the newest version may not always be best, depending on the game you're playing. I think 1.9.2 especially was optimized for Stormland. 

Well I tried 1.9.2 and it did seem to work a bit better.  However, some of my Vive controller actions like turning on/off the headlight and helmet do not seem to work in Lone Echo.  I tried going back to earlier loads to just before these got calibrated but it did not make any difference.  So, out with Revive again and onto my good old cv1, lol!  Too bad because the graphics with my Pro's oled's was stunning.

TomCgcmfc said:

Well I tried 1.9.2 and it did seem to work a bit better.  However, some of my Vive controller actions like turning on/off the headlight and helmet do not seem to work in Lone Echo.  I tried going back to earlier loads to just before these got calibrated but it did not make any difference.  So, out with Revive again and onto my good old cv1, lol!  Too bad because the graphics with my Pro's oled's was stunning.

It can be hard to hit the imaginary helmet buttons, but if it works with CV1, you should be able to do it using Revive too, at least some have got it to work, although it's an old thread:

https://www.reddit.com/r/Vive/comments/6ok4j6/lone_echo_press_button_on_side_of_visor_stuck_no/

New Index weirdness today.

I was in the middle of a tandem Alyx experience (voice chatting with a buddy who's on his first play through, pacing the game so I'm in step with him) when my left hand dropped to the floor and stayed there. Controller would register in Steam VR as turned on, but not tracking:
Restarting Steam VR and Steam didn't do anything, so I restarted the computer, but then Steam wouldn't load. Gah!

Restarted the computer once again, and everything was back to normal.

For an hour, lol. Then the same thing happened again. At which point I switched to my Oculus headset so I could continue playing.

I think this underlines the point that Index, although a fantastic headset, should never be the sole HMD one owns.

Off to Steam support again - looks like the replacement controller they sent me has some new issues

That is strange - but it has happened before, just found this:

https://www.reddit.com/r/ValveIndex/comments/co395a/left_controller_not_tracking_anymore/

If resetting the controller doesn't help, looks like you may need a replacement. 

Some dude wrote: "Alyx maximized demand, Covid-19 killed supply", I hope that Valve is able to ship parts. I've seen several posts on Reddit where Valve in March said 8 weeks of waiting time for Index kits to ship, but for many these 8 weeks haven't been reduced - thus 8 weeks may have turned into at least 16 weeks...  

Agreed that it's great/important having more than 1 hmd available. 

RuneSR2 said:

TomCgcmfc said:

Well I tried 1.9.2 and it did seem to work a bit better.  However, some of my Vive controller actions like turning on/off the headlight and helmet do not seem to work in Lone Echo.  I tried going back to earlier loads to just before these got calibrated but it did not make any difference.  So, out with Revive again and onto my good old cv1, lol!  Too bad because the graphics with my Pro's oled's was stunning.

It can be hard to hit the imaginary helmet buttons, but if it works with CV1, you should be able to do it using Revive too, at least some has got it to work, although it's an old thread:

https://www.reddit.com/r/Vive/comments/6ok4j6/lone_echo_press_button_on_side_of_visor_stuck_no/

- they say you should look for the button here:




I have not tested that using the Index, but Index usually works extremely close to Touch. 

Ya, I tried all that and I could only get the visor up/down (left side) once in a while and headlight same on the right side.  Plus I've found the yaw control (left trackpad) is now also very inconsistent.  Funny because all these seemed to work well a 2-3 weeks ago.  Lots of SteamVR and Win10 updates in the meantime though.   Anyway, my cv1 continues to play perfectly so back to it I go.  I hope I can get through Lone Echo before an Oculus update screws thing up, lol!  At least I'll still have my Quest wireless with Virtual Desktop as a backup (works surprisingly well btw).

TomCgcmfc said:

RuneSR2 said:

TomCgcmfc said:

Well I tried 1.9.2 and it did seem to work a bit better.  However, some of my Vive controller actions like turning on/off the headlight and helmet do not seem to work in Lone Echo.  I tried going back to earlier loads to just before these got calibrated but it did not make any difference.  So, out with Revive again and onto my good old cv1, lol!  Too bad because the graphics with my Pro's oled's was stunning.

It can be hard to hit the imaginary helmet buttons, but if it works with CV1, you should be able to do it using Revive too, at least some has got it to work, although it's an old thread:

https://www.reddit.com/r/Vive/comments/6ok4j6/lone_echo_press_button_on_side_of_visor_stuck_no/

- they say you should look for the button here:




I have not tested that using the Index, but Index usually works extremely close to Touch. 

Ya, I tried all that and I could only get the visor up/down (left side) once in a while and headlight same on the right side.  Plus I've found the yaw control (left trackpad) is now also very inconsistent.  Funny because all these seemed to work well a 2-3 weeks ago.  Lots of SteamVR and Win10 updates in the meantime though.   Anyway, my cv1 continues to play perfectly so back to it I go.  I hope I can get through Lone Echo before an Oculus update screws thing up, lol!  At least I'll still have my Quest wireless with Virtual Desktop as a backup (works surprisingly well btw).

Maybe I'll test it later with the Index - but I lost all my save games when moving the game from one location to another. I think the save games can still be found, I just haven't bothered because I've completed the game. Not sure if the helmet button is active from the start of the game. 
Still CV1 is "the way it's meant to be played", I guess you're doing fine ;) Revive will be more important when we get those 3080 cards, lol.