-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lone Echo Not Responding to WMR Controller Inputs in Remixed or Revive Injector #1158
Comments
This issue seems to be open since and discussed since ticket #962 ? |
Confirming Remixed controllers on Lone Echo no longer working. Looking into it. |
@Dragoboss I can confirm that running it through Revive on the SteamVR dashboard is the exact same result as running it through the manual injector |
I experience exactly the same issue as JoePinapples I have a Lenovo WMR headset, would love a fix for this |
Also, as mentioned if Lone Echo is launched via Revive dashboard directly it runs but button responses are not registered so you are unable to start the game. If I launch the Lone Echo VR (the free multiplayer game) from Revive it launches and button presses DO work and when it the game it is buttery smooth . Launching this same Lone Echo VR multiplayer game via SteamVR stutters as you turn your head, the same as the full game. So this is quite annoying that the menu and start screen work in the multiplayer aspect, seems like it would be a relatively easy fix to work out whats different :-( |
I have the same problem with Vive:
|
I've been with this problem for a few weeks, I tried to see if it was the subject of the revive and tried to update to the most current version (1.6.3) but without solving it. With several guys who have the same problem, they give the steamvr version as a solution, they say that doing a downgrade to version 1.3.3 works correctly ... After trying to do the downgrade, as steam always updates, I can not keep that version, so after the announcement of a user that the Lone Echo worked perfectly with SteamVR 1.2.10 and Revive 1.4.2, I decided to try the different versions of Revive and ... indeed, I have tested all versions after 1.4.2 and none of them work. So you know, if you want to play your Oculus games with SteamVR 1.2.10, you will have to make a downgrade of its version 1.4.2 revive until further notice. |
I'm having this exact same issue with an Odyessy Plus. It's a shame, since I got the unit primarily for Lone Echo :). Robo Recall does not work either ("connect controllers" screen). Both games work flawlessly with the Rift. |
After yesterday's remixed support update the buttons get registered again and the game works again for me! |
That’s weird! I tried last night. I did a fresh install of revive 1.6.3 and I had no joy. Using remixed, the game loaded up into the Lone Echo main menu, my controllers were being tracked & I was no longer getting the hardware error message but my button presses were not registering. Could not select any of the options in the main menu.
I will try again tonight.
My I ask what your specs are, what headset and what software versions you are using?
Thank you.
From: m0nk210 [mailto:notifications@github.com]
Sent: Tuesday/ 5 February/ 2019 09:19
To: LibreVR/Revive <Revive@noreply.github.com>
Cc: JoePinapples <rightsduff@hotmail.com>; Author <author@noreply.github.com>
Subject: Re: [LibreVR/Revive] Lone Echo Not Responding to WMR Controller Inputs in Remixed or Revive Injector (#1158)
After yesterday's remixed support update the buttons get registered again and the game works again for me!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#1158 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ar8qGzA5LY_--EYmWe0xrUET-gNcYCybks5vKUx8gaJpZM4ZoHE6>.
|
Okay after your message yesterday I tried again last night, the button press not registering issue still persists in Remixed and in Revive through the Steam VR compositor and through manual injection. |
Same as m0nk210. |
I had this issue of no buttons working with injecting Lone Echo on the Vive. Recently updated to 1.6.3 and the issue still persists. Why is this happening? |
Tonight, Lone Echo is working on my PC with my Lenovo Explorer. I don't know why, but if it could help someone, I did this:
And I can click on buttons. |
@yd76 Unfortunately i cannot get it to work using your method. Perhaps I am doing something wrong. Can you describe in greater detail exactly the steps you took? I am still have the same problem. Also when you kill the revive tray icon and "launch the revive dashboard" do you mean the remixed overlay? Once you quit the revive tray icon revive no longer shows up in the steam dash board. So I am a bit confused about this step. When launching through remixed now I no longer get the hardware error message and the controllers are tracking and the button presses are prompting the corresponding animations on the robotic hands. However, it appears that the game thinks that my HMD is not on correctly. The icon that indicates the HMD status in the start menu is in a paused state and depicts the oculus headset raised up resting on the models forehead rather than in the playing position. Perhaps this is what is preventing the buttons from registering. The game thinks that that the HMD is not down in the playing position on the head and that input is going to the desktop? |
I dont know why but it's work for me ! thanks you very much ! Perhaps revive don't initialize correctly with steamvr and need a restart ?!? |
@JoePinapples
I hope it could help you until this issue is fixed. |
@yd76 |
Solved my problem. OMG. Thank you! |
Hey JoePinapples, https://www.youtube.com/watch?v=MYYm9R7TXaQ
P.S.: My System- and Hardware-Specs are listed in the video-description. Regards |
Remixed has been replaced by ReviveXR: https://github.com/LibreVR/Revive/releases/tag/1.7.0 |
This fixed my no button click with odyssey+ |
Revive/Remixed Report Template
Description of the issue
Lone Echo will load from the revive dashboard with remixed and it will also load from the revive injector within the Steam VR compositor. 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.
There is a slight difference arising between using the 2 different revive methods which I will outline below:
Issues Experienced Launching Through Remixed
When launching the game in remixed i.e. via the Revive Overlay, (without using SteamVR)
trigger animations on the in-game holographic robot hands
showing as green, i.e. connected however the touch controllers are displayed as red, i.e. not connected.
Issues Experienced Launching Through Revive & Injector
Technical Information
Tell us your specs and versions
Versions and features
This issue is about:
What is the last working version before this issue first came up?
n/a I just bough Lone Echo and tried it for the first time
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?
The controller inputs simply will not register in the menu. My hunch is that Revive is not telling the game that the controllers are connected correctly. This may be a Samsung Odyssey Plus issue in that the controllers no longer require a separate bluetooth dongle in the computer to make a connection, like the previous Samsung Odyssey did, but that they are now paired with the headset itself. Just a thought!
I just want to add a big thank you I love the software and it has helped me play Oculus games such as Robo Recall, Edge of Nowhere, Air Car and First Contact without any issues whatsoever.
I am really appreciative of any support you may offer to get Lone Echo up and running.
Discord ID
JoPineapples#3512
Error messages/codes:
Message Received when using remixed method:
Thank you for reporting your issues/feedback/suggestions about Revive! We really appreciate your support!
The text was updated successfully, but these errors were encountered: