Lone Echo menu buttons unresponsive with Revive 1.7.0 on Odyssey old and + (but Echo VR works and performance gain is great compared to 1.6.4) #1230
Comments
CommercialCRAP
changed the title
|
Just confirming I have this same issue, both in SteamVR version and not. I have the Odyssey +. If I use Vive tracking instead everything works great. |
CommercialCRAP
changed the title
|
I am once again reporting in! I have two PC's. Just tried the other PC for the heck of it, and everything is working perfectly for every game I've tried, including Lone Echo. The only difference between the two is one is Windows 10 pro build 1803 (working) and the other is Windows 10 home build 1903 (not working). I am also using steamVR beta on the not working one, and current release on the working one... which is the version you're using so that shouldn't be the culprit there. Afraid to say I have no idea how to further diagnose but am ready to try different things if instructed! |
|
Thank you! Also the windows mixed reality portal versions? |
|
Note to myself, from investigating this youtube video: As far as I understand Lone Echo used to work fine and smooth with the old Odyssey back in 2019 march 30th with revive 1.6.4 In the comments of the video it was later reported by the author of the video that either the new steamVR or Lone Echo version broke revive and thus became slow/jitter-ish. |
Sure thing! How do I check the portal version? Working revive PC -- user benchmark gives its current config other than portal version: https://www.userbenchmark.com/UserRun/16476787 Non-working revive PC -- user benchmark gives its current config other than portal version and it's using nvidia driver version 430.64 now: https://www.userbenchmark.com/UserRun/16808361 eta You can use old SteamVR (this version is even older than 1.3.20) and any revive version previous to 1.7 and it should work smoothly. However I am having the same input issues with WMR tracking on that as well. See this reddit thread |
|
In windows start menu, right click on the mixed reality portal icon, then select more>app setting thanks for the old steamvr! |
No problem! Let me know if that fixes anything for you! I'm wondering if this is a 1903 issue. When I first installed it (it's a completely fresh install on a new HD), if the O+ was plugged in it wouldn't shut down all the way. I re-checked 'allow the computer to turn off this device to save power' and it started shutting down again. Now it won't again and that box is still checked... Anyway, the versions are: working revive PC: 10.0.17134.1 non-working revive: 2000.19011.1132.0 |
|
Since the portal versions are different, it could possibly be limited to the portal version. I don't know if you have any way to manually downgrade just the portal app in the 1903 revive non-working PC to the same version as the 1803 revive working PC and see if this solves the issue. I would happily try that on mine if I found a way to do so. Also I was wondering if your Lone Echo version is the same on both ? Mine is 3.17. |
|
I believe the portal version has to do with the windows build version and can't be rolled back to one that went with a previous build unfortunately! Both PCs have the same version of Lone Echo, which is also 3.17 |
|
The mixed reality portal app is updated through the microsoft app store > dowloads and updates > get updates. So there might be some way to roll back even though it might also have some dependencies with the windows build version. Also in the microsoft app store, I can search for mixed reality portal, and I see that is it installed. So it seems to be managed in there. There might be some comparable download and update mechanism as for steamVR through the steam store. Just a wild guess, I don't really know. |
|
I have 1809 installed now and am waiting for the Oculus software to download! The portal version it automatically installed was different than the one automatically installed for 1903 or 1803 so I think the versions may be tied to the windows build. After verifying if it works I'll see if I can get an update from the store. |
|
I am now able to play Lone Echo with WMR after the 1809 downgrade! Last thing I need to try is setting Vive tracking back up then seeing if everything still works with WMR... Then can safely say if it's 1903 causing the issue! Edit: and have Vive tracking set back up and I'm now able to smoothly switch between WMR and Valve lighthouse tracking and have revive still work! Looks like 1809 is the trick! |
|
Well done detective! What's the version of the portal on your 1809? |
|
I just downgraded to 1809 but same problem. Portal version: It's the still the same version as on my 1903! So it's most probably due to this new portal version. |
|
I have tried to uninstall the MR portal and reinstall it but I always get the same version. So Apparently I am stuck regardless of 1809 or 1903. How did you downgrade to 1809, clean fresh install? On my laptop I went to settings > update and security > recovery > restore previous build.
I haven't found any repository for old builds or option to downgrade the app version. Would you please be so kind to upload your MR portals app folders from both PC so I could try to override my portal manually? I read that: QUOTE Additionally, here is a script or manual guide to gain access to the windowsapps folder. Prerequisite to copying the WM portal folder: |
|
I had to install a fresh version of 1809, cause it had been a fresh version of 1903 -- ended up calling Microsoft and they remotely put an 1809 iso on a USB drive for me. Hopefully the portal version didn't update with today's Windows update: I'll check and see about giving you my file once home! |
|
Hey just checking in to say MS support updated my portal to current while trying to troubleshoot my WMR power issues... So it's the same as yours now. That said revive still works with that version, so that's not the issue it seems! I would try with a completely fresh install which of course means re-downloading everything and all of that :/ |
|
Ok that's great news! Thank you. |
|
Oculus stopped working for no apparent reason and would not reinstall so I took the opportunity to do a fresh 1809 install. However I still have the same initial issue for me with 1.7.0 and up to date steam. I am now trying to install your batch for switching versions. Do you use the same windows build? I downloaded 17763.1.180914-1434.rs5_release_clientconsumer_ret_x64fre_en-us_a21ecd9defb6c71439dc7bbf6bc3684be8fd9aea.esd from this guide:
|
|
I have used your batch to switch to the old SteamVR contained in the same folder as the batch, along with Revive 1.5.0 and openVR advanced settings 2.6 (I didn't install that before reading your READ ME txt file, I don't know what it is for by the way). And it works with Lone Echo! Thank you so much! I am finally able to play smoothly. Did you say that this switching to old SteamVR and Revive 1.5.0 would also work on win10 1903? This is my WMR version by the way: |
|
Great! I don't understand why 1.7 isn't working for you but at least you can play now! I was originally using it with 1903 so it should work for you, but all bets are off since switching to 1809 didn't work for 1.7. Oh another word of warning: 1903 has a bug that makes Odyssey, plus, and reverb blurry unless you super sample a lot. Advanced settings is for if you're using controllers other than the ones for WMR. It's using the same code base as steamVR so needs to match the openVR version of steamVR, so has to also be swapped to an older version when you swap to old steamVR. It's not necessary if you're not using Vive or Valve controllers but doesn't hurt anything either :) Anyway glad it's working for you now! It's not my batch file btw: I just first suggested swapping to old steamVR to the OP and when it worked they shared the batch file! |
|
Well thank you and batch OP very much. And thank you so much for LibreVR/Revive to make this possible! I am definitely a huge fan of Lone Echo, I think for me it is the best VR game I played so far, along with Doom VFR. But lone echo is way more immersive. I am an instant huge fan of zero G VR gameplay, which feels so immersive and no motion sickness at all. I finished Downspiral before but it is nowhere as beautiful as Lone Echo. Echo VR is super fun and so beautiful also with its somewhat "TRON 2" looking environment, but I am very lame with team sports and grabbing and throwing a projectile. I am thinking about buying Echo Combat as I am better with shooting guns. I don't know why facebook chose to make oculus exclusives, I am not so sure it really helps them to make more profit compared to just making these games "oculus store exclusive" but with built in support for all VR hardware. And it definitely sucks to segment early VR adopters, it's slowing down mainstream adoption in my opinion. Same with the Oculus Quest : why on earth didn't they make a built in wireless PC VR streaming client/server, as supported by third party free open source projects?!? And why would they even remove these projects from the official oculus quest app library!?! So thank you so much to all people who are bridging all platforms! |
|
i know its been a couple of days but i had a similar issue. I'm on the orginial vive with 1.0 base stations and index controllers and im almost positive the issue is with revive becasue i was on an old verison version 1.3.0.3 of revive and when i inject lone echo everything works fine expept that the index controller inputs werent mapped properly because the version of revive didn't have the controllers mapped, and when i updated to 1.6.4 it broke, making it so that no inputs where recongnized in the game, however since i still had the files in the recycling bin i rverted back to version 1.3.0.3 and when i checked for updates it gave me 1.6.3.0 and after i updated to that version everyting worked perfectly. |
|
I was having similar issues with Index + Index Controllers in Echo VR. Couldn't select anything in Menu. But after a while I found out that touching (not squeezing) the grip (not the trigger) activated menu buttons. I don't know why this is, according to the Steam Controllers Settings nothing is bound to touch grip. After I had played for half an hour I went back to the menu (keep pressing the touch pad) and now the Trigger also worked for selecting menu items!?! Very weird. I'm thinking about buying Lone Echo, but not sure yet. Controls need to be reliable... |
|
@JoopNL This has nothing to do with the reliability of the controls, the issue is that pressing the grip trigger to any degree on the Oculus Touch also activates buttons in the menu. This will also prevent pressing other buttons until the grip is released. There is no clear solution for this other than rebinding the hand trigger to the force sensor, but this could require you to continually squeeze the controller to hold something. |
Lone Echo menu buttons unresponsive with Revive 1.7.0 on Odyssey old and + (but Echo VR works and performance gain is great compared to 1.6.4)
Description of the issue
Lone Echo will load from the revive injector. However once loaded into the main menu of the game the WMR controller inputs are not registering and I cannot move passed the main menu into the game. (and as reported in #1229 ReviveXR doesn't work. Anyways Remixed didn't work in 1.6.4 either, so revive is the only option so far)
The game will load into the main menu
I can see that the wmr hand controllers are being tracked and moving correctly.
Pressing buttons such as the grab and the trigger buttons on the controllers will prompt grab and trigger animations on the in-game holographic robot hands
The icons for the first tower camera is showing as red i.e. not connected and the oculus rift and the 2 touch controllers on the bottom right in the Lone Echo main menu are showing as green, i.e. connected.
I can see the point of focus dot in the Lone Echo VR main menu and it corresponds to the movement of my wmr hand controller, however when pointing it at any of the options within the menu it is not highlighting the targeted option. The single player option is constantly highlighted and does not budge from there regardless of where I point to with the controller.
Pointing at the highlighted single player option and pressing trigger has no effect
Alt tabbing out and back in had no effect
Pressing the windows button to go back to the cliff house and then going back into lone echo has no effect.
Whilst still in the main menu, If I remove my headset I can observe on my laptop the following Hardware error message: "You have a pending hardware issue that is preventing you from entering VR. Please check that your sensor(s) is/are connected". (the error message is displayed fullscreen with white writing on a totally black background, the message does not give me any options to select, such as okay or close).
(surprisingly there is no issue with Echo VR, even though it is also displayed to have first tower sensor off, and same black screen "hardware problem", echoVR is now smooth as silk whereas it was slow/jitter-ish in 1.6.4, as Lone Echo)
Issue is somewhat similar to that was reported for the new Odyssey Plus in 1.6.4 with Remixed and with revive and where a workaround through injector was found and described in the discussion. But there are also some difference (namely the camera is showing off here and all the rest green, whereas in the issue 1158 all was green except the 2 touch controllers) I tried many possible ways, through the injector and also from within Steam VR revive dashboard but no luck. I report here the same procedure that was previously working but is now broken:
#1158
WILD GUESS: It would be interesting to know if it works with the new Odyssey Plus, if so maybe the a fix for the plus broke the functionality for the old Odyssey as reported here.
Edit : user spoonyspork experiences similar problem with the odyssy + (see reply)
It also seems somehow similar to:
#1196
Technical Information
Tell us your specs and versions
See configuration and versions in screenshot attached.
Versions and features
This issue is about:
Revive 1.7.0 Injector
SteamVR version (unless Remixed): 1.4.18
Revive installation version: 1.7.0
What is the last working version before this issue first came up?
What apps/games are you trying to run?
How to reproduce your issue?
This is some of the most essential information: what steps did you do to get to this issue. Which steps do we take to get to the same result?
Error messages/codes
(surprisingly there is no issue with Echo VR, even though it is also displayed to have first tower sensor off, and same black screen "hardware problem", echoVR is now smooth as silk whereas it was slow/jitter-ish in 1.6.4, as Lone Echo)
The text was updated successfully, but these errors were encountered: