Open Dekor47 opened 6 years ago
Can you try switching to the openvr-inputemulator-temporary branch of SteamVR?
ok wow that seemed to work thanks SO MUCH for the fast response i can now finish my work. Medium started. thanks for all that you've done actually.
That branch uses an old build of SteamVR, the issue you're describing was in the beta and I hope they didn't just push it to the stable now.
Fixed my problem as well. Thank you!
Windows Mixed Reality (Odyssey) user here. The openvr-inputemulator-temporary branch of SteamVR fails to even recognize my headset, so that's no solution for me.
@cartoonmonkey You'll need to wait until Valve fixes the issue or until I complete native WMR support in Revive.
Are you saying we need to install openvr inputemulator? I tried that and am also trying to start in non beta as well as fresh install of steam and revive with no luck.
No.... I said you needed to switch to a different branch, it's right there in the list next to the beta.
Is that for the beta that ended jan 22? I don't see that option in steamvr
edit: finally found where to change the branch. Have to opt into beta through steam changing steamvr properties.
Can someone test the beta branch of SteamVR? It should be fixed there also.
Wish I'd seen this earlier - Windows is downloading a new insider build now (after several hours of troubleshooting why I'm 3 builds behind), and it's late, so I probably won't be able to test it until I get off work tomorrow, but I'm all about helping test it for you. Might be able to check it before the PC reboots to finish the install.
And I'd like to re-iterate the sentiment of Dekor47 - Thank you very much for all you do.
Unfortunately, the SteamVR Beta branch is a no-go. The openvr-inputemulator temporary branch works though, at least... temporarily, haha.
Steam broke it again :(.
No version is working (beta, imputemulator, GDC2018, standard)... Arggh, that complicated world where things were working a day and no more the next day... and hopefully again the next next day but so far no Medium for me today.
Somehow related : does someone knows how to 'backup' a given (working) SteamVR version ? That could be a 'lifeguard' when you have to rely on a software.
@Expicot You need to disable the Steam Overlay: https://www.patreon.com/posts/how-to-fix-part-17220186
Thanks for the hint but it was disabled. Previously it was working only on SteamVR beta, but since the latest update (version with the automatic SS setting)... it just crash at start.
Next version of Revive will disable the code in Oculus Medium that makes it so sensitive to OpenGL errors. Should be out today or tomorrow.
Great ! Thanks a lot.
Thank you so much. I am demoing VR sculpting, using Medium, on the 28th and was seriously sweating it.
On Sun, Mar 18, 2018, 11:30 AM Expicot notifications@github.com wrote:
Great ! Thanks a lot.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LibreVR/Revive/issues/922#issuecomment-374008368, or mute the thread https://github.com/notifications/unsubscribe-auth/AIJNrk3KKZPK71bi5ZaiJoR5Vk6Jot8xks5tfn2mgaJpZM4SEjNH .
Just to confirm I tried the openvr-inputemulator-temporary branch and making sure I didn't have steam overlay on but it is not working for me either. I will check back in a couple days and see if there have been any updates. Windows 10/32 Gb/Nvidia 1080. Thanks.
I see there was a "commit" to fix the issue for medium (hooray!!) but I am a github noob and have no clue how to get that installed if it is not included in the existing installer. What is the trick to get that commit installed?
@redcovert I don't have a nightly build system so you'll have to wait until it is rolled out in the next release.
@Armada651 - Do you have an idea as to when the next release will be?
@3dbumper Right now: https://github.com/LibreVR/Revive/releases/tag/1.2.2
@Armada651 Thank you very much. I really appreciate it.
I apologize if this is the wrong place to ask this, but are there any tricks to getting the most performance out of Medium? My GPU (1080) never got over 58% usage during my last session, and I'm getting some frame rate issues/stutter. Weird, now I maxed out at 91. Still some stutter/blur when moving, but in the end, so happy to have Medium back.
@Armada651 Hi, I just updated to the latest release form your link and Medium is no working at all along with Quill that was working fine before the update. Any idea on what could be wrong? Thank you!
Sorry, just realize I had to update the oculus app as well.. All working fine now. Thank you so much for you work!
Github Noob here - I wasn't sure how to install the 1.2.2 zip file you referenced above but thought maybe I needed to download the program NSIS from sourceforge and use that to process the .nsi script in the installer folder (in your 1.2.2 zip file) but when I load that script into it... I immediately get this error:
Changing directory to: "E:\git test\Revive-1.2.2\Installer"
Processing script file: "E:\git test\Revive-1.2.2\Installer\Revive.nsi" (ACP) !define: "BASE_DIR"="..\Release" !include: "C:\Program Files (x86)\NSIS\Include\MUI2.nsh" (ACP) !include: "C:\Program Files (x86)\NSIS\Contrib\Modern UI 2\MUI2.nsh" (ACP) NSIS Modern User Interface version 2.1 - Copyright 2002-2018 Joost Verburg (C:\Program Files (x86)\NSIS\Contrib\Modern UI 2\MUI2.nsh:14) !include: closed: "C:\Program Files (x86)\NSIS\Contrib\Modern UI 2\MUI2.nsh" !include: closed: "C:\Program Files (x86)\NSIS\Include\MUI2.nsh" Name: "Revive" OutFile: "ReviveInstaller.exe" InstallDir: "$PROGRAMFILES64\Revive" InstallRegKey: "HKCU\Software\Revive\" Var: "StartMenuFolder" !define: "MUI_ABORTWARNING"="" !insertmacro: MUI_PAGE_LICENSE !insertmacro: end of MUI_PAGE_LICENSE !insertmacro: MUI_PAGE_DIRECTORY !insertmacro: end of MUI_PAGE_DIRECTORY !define: "MUI_STARTMENUPAGE_REGISTRY_ROOT"="HKCU" !define: "MUI_STARTMENUPAGE_REGISTRY_KEY"="Software\Revive" !define: "MUI_STARTMENUPAGE_REGISTRY_VALUENAME"="Start Menu Folder" !insertmacro: MUI_PAGE_STARTMENU !insertmacro: end of MUI_PAGE_STARTMENU !insertmacro: MUI_PAGE_INSTFILES !insertmacro: end of MUI_PAGE_INSTFILES !insertmacro: MUI_UNPAGE_CONFIRM !insertmacro: end of MUI_UNPAGE_CONFIRM !insertmacro: MUI_UNPAGE_INSTFILES !insertmacro: end of MUI_UNPAGE_INSTFILES !insertmacro: MUI_LANGUAGE !insertmacro: end of MUI_LANGUAGE Section: "Revive" ->(SecRevive) IfSilent ?install: DetailPrint: "Terminating dashboard overlay..." File: "nsExec.dll"->"$PLUGINSDIR\nsExec.dll" [compress] 3121/6656 bytes Plugin command: ExecToLog "taskkill" /F /IM ReviveOverlay.exe Sleep: 2000 ms SectionIn: [RO] IfFileExists: "$INSTDIR\ReviveOverlay.exe" ? +3 : 0 IfFileExists: "$INSTDIR*.*" ? 0 : +2 StrCpy $INSTDIR "$INSTDIR\Revive" () () SetOutPath: "$INSTDIR" File: "LICENSE" [compress] 626/1064 bytes File: "..\Release\app.vrmanifest" -> no files found. Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] | /oname=outfile one_file_only) Error in script "E:\git test\Revive-1.2.2\Installer\Revive.nsi" on line 78 -- aborting creation process |
---|
After an hour of googling/trying things I still have had no luck.
Latest official release is 1.2.1 right ? Is it possible that performance is lower with Medium ? I have a lot of reprojection that I don't remember having saw in previous builds (GTX 1080Ti).
@redcovert You're downloading the source code, you need to download the executable file called "ReviveInstaller.exe".
It's happening again with Oculus Medium version 2.1 I had the same problem before with Medium version 2.0 and I solved it installing SteamVR Beta. But now it's not working again, even with SteamVR Beta installed.
HI,
So currently im having a hard time running Occulus medium, every time at launch i get an instant "fatal error" MSG with a blank screen on my desktop. It looks to be just a snap shot of the main medium menu. While in VR I cant see the usual application loading screen but i can hear the loading music. also my controllers seem to phase thru selections, and become unresponsive. Usually pressing the home button on and off does the trick, but im not sure if these 2 issues are related in anyway but its weird since i wasent experiencing any of this yesterday and from what i can see nothing has updated except steam vr.
Just before making this post i had updated revive and got a new msg saying "Unable to initialize the Oculus Rift"
i have seen similar issues before but since steamvr just updated im wondering if this could be the issues.
ive reinstalled revive twice. once to a previous version and 2nd time i just reinstalled the newest version. ive reinstalled medium ive disabled steamvr beta ive updated my drivers to 390.77
im on a Nvidia geforce GTX 970