Any info yet for Lone Echo 2?

[ElricOfMelnibone]

I know it just came out, but was wondering if anyone had tried it yet.

[vvvnew]

I tried using the latest version of revive and also the one before that. Using a reverb G2, 5600X and RTX 3080. Pretty much unplayable. I get huge fps drops and judders every few seconds.

The most recent version is dated July 2020, so i think a new version is needed for LE 2 to run well.

[ElricOfMelnibone]

Damn... Good to know though--thanks for the info. I'm on an OG Vive, AMD 2600X and 1080Ti, so I don't hold out much hope of being able to run this.

[vvvnew]

I think its more of a software issue than hardware. The game isnt that CPU intensive, mostly GPU bound. People have run it with the Quest 2 with low/mid end GPUs.

[thomasfrobieter]

I tried using the latest version of revive and also the one before that. Using a reverb G2, 5600X and RTX 3080. Pretty much unplayable. I get huge fps drops and judders every few seconds.

But you where able to play. I can't confirm anything in the accessibility screen on first startup.. the trigger button doesn't work.

[tomasvala]

In Oculus world (at least Lone Echo 1 and 2 which I tried) for some reason menu actions are not confirmed by trigger button but by opening and closing fist. Quite inconvenient. Also boosters are controlled by clicking joystick button which is awkward as it is known to cause damage to Index knuckle controller. Wish there was a way to remap these actions to trigger buttons. UPDATE: as it turns out there is a possibility to create custom binding profile in SteamVR.

I can confirm Lone Echo 2 kinda works with Revive (but I personally needed to install this fork build https://github.com/ServError/Revive/releases/tag/2.1.1.134 instead of latest official stable to make game even launch). Disclaimer: I played just a few minutes as I don't want spoilers before completing Lone Echo 1.

Valve Index, Ryzen 2700X, RX 6800XT

[vvvnew]

I have no issues with G2 controls which makes sense because the button mappings are similar to the rift controllers. Only issue i have is horrible performance. The only way to play with 90fps is set everything to low and 70% steamVR SS, which is what iam currently running. This being said, the game is awesome.

[vvvnew]

I tried using the latest version of revive and also the one before that. Using a reverb G2, 5600X and RTX 3080. Pretty much unplayable. I get huge fps drops and judders every few seconds.

But you where able to play. I can't confirm anything in the accessibility screen on first startup.. the trigger button doesn't work.

I believe people have it working with the index by button mashing and finding a button that works. You can look it up on index forums.

[mateuszw1995]

I also tried this game witch Reverb G2 and the performance is poor. I have RTX 3080 and I7-8700K. On medium settings GPU load is 100%, FPS around 30-60 FPS but the worst thing is judders almost all the time. It is very strange, because Lone Echo 1 works well on max settings and FPS was stable, and new episode doesn't look much better than first one. I figured out that changing shadows to high or enabling antialiasing causes catastrophic failure - game turns to slideshow :) Changing render scaling or using dynamic resolution in game settings has no effect.

[vvvnew]

I also tried this game witch Reverb G2 and the performance is poor. I have RTX 3080 and I7-8700K. On medium settings GPU load is 100%, FPS around 30-60 FPS but the worst thing is judders almost all the time. It is very strange, because Lone Echo 1 works well on max settings and FPS was stable, and new episode doesn't look much better than first one. I figured out that changing shadows to high or enabling antialiasing causes catastrophic failure - game turns to slideshow :) Changing render scaling or using dynamic resolution in game settings has no effect.

Agreed. The first one with the G2 (at 100% steamVR resolution) was fantastic and possibly the best VR experience ive had to date. Iam playing LE 2 at 70% steamvr SS and all settings to low. Looks very poor in comparison and runs like crap compared to the first one. (i get 90 fps but a lot of judders/stutters) Such a shame though; FB decided to shut down PCVR on the rift and so you cant really talk to devs regarding this. This site also seems to be pretty much dead at this point, since the admin now has a full time job and is no longer working on revive. (the last version is July 2020, been more than a year now)

I wouldnt mind paying money to buy revive and run oculus games with good performance.

[tomasvala]

That's strange. In my very short test the performance didn't seem particularly bad/unplayable. And that was with 300% SteamVR resolution on Index, my default for BeatSaber and Echo 1. Will eventually try again.

[vvvnew]

That's strange. In my very short test the performance didn't seem particularly bad/unplayable. And that was with 300% SteamVR resolution on Index, my default for BeatSaber and Echo 1. Will eventually try again.

Could be an issue specific to WMR maybe? I know guys with 3090/reverb G2 who run the game at 30-45 fps.

[CrossVR]

When comparing performance numbers please mention which version you are using. For WMR users it'd be interesting to compare the performance on OpenXR with the beta version against SteamVR. I provided a more permanent download location for the beta version and bumped its version number so you don't need to download it from weird forks anymore:

https://github.com/LibreVR/Revive/releases/tag/3.0.0

[vvvnew]

When comparing performance numbers please mention which version you are using. For WMR users it'd be interesting to compare the performance on OpenXR with the beta version against SteamVR. I provided a more permanent download location for the beta version and bumped its version number so you don't need to download it from weird forks anymore:

https://github.com/LibreVR/Revive/releases/tag/3.0.0

Hi, Iam using The latest version of revive (2.1.1) that only works with steamvr and use the reverb G2 (which also has WMR running in the background). I can see a version 3.0.0 beta version now, will give this a go. Any idea how this OpenXR one is supposed to be run? With steam vr, i open steam vr, then revive and open the game from revive dashboard.

Thanks for the help!

[CrossVR]

You can skip opening SteamVR, just open WMR and if it's not set as the default OpenXR runtime it'll give you a button at the top to "Fix It":

Then just launch the Revive dashboard on the desktop and start Lone Echo 2 from there. Unfortunately there's no in-VR dashboard for WMR so you'll have to use the desktop each time.

[vvvnew]

You can skip opening SteamVR, just open WMR and if it's not set as the default OpenXR runtime it'll give you a button at the top to "Fix It":

Then just launch the Revive dashboard on the desktop and start Lone Echo 2 from there. Unfortunately there's no in-VR dashboard for WMR so you'll have to use the desktop each time.

Great, will try it out today and post results with 3.0.0/OpenXR in comparison to 2.1.1/SteamVR.

[vvvnew]

You can skip opening SteamVR, just open WMR and if it's not set as the default OpenXR runtime it'll give you a button at the top to "Fix It":

Then just launch the Revive dashboard on the desktop and start Lone Echo 2 from there. Unfortunately there's no in-VR dashboard for WMR so you'll have to use the desktop each time.

So tried out the OpenXR beta version of revive. The game crashes immeditely after i launch, giving an 'unknown error'. I checked with a few other people and all of them had the same crash with this version of revive.

The steamvr one launches but performance is abysmal.

[vvvnew]

@CrossVR I think both the openXR version of revive and steamVR versions have issues with lone echo 2.

[CrossVR]

Yes, it looks like an issue specific to the DX12 implementation in ReviveXR, but the SteamVR version works fine on the Valve Index. The problem you're encountering with the SteamVR version is an issue in the implementation of the WMR driver for SteamVR.

[vvvnew]

Yes, it looks like an issue specific to the DX12 implementation in ReviveXR, but the SteamVR version works fine on the Valve Index. The problem you're encountering with the SteamVR version is an issue in the implementation of the WMR driver for SteamVR.

Its also game specific because lone echo runs fine with revive/steamVR but lone echo 2 doesnt. Any chance you can fix the ReviveXR version?

[CrossVR]

I'd like to, but I doubt I will have the time available. I'd be happy to give a few pointers to any developers wanting to pick this up.

[vvvnew]

I'd like to, but I doubt I will have the time available. I'd be happy to give a few pointers to any developers wanting to pick this up.

Damn that sucks. I wouldnt mind (and many others i know) paying for something like this; this is one of those games that i was looking forward to. But i understand you have a full time job at Epic. Maybe there will be someone who can take this up in the future and get it fixed.

[ElricOfMelnibone]

Just wanted to say I got LE2 working for me. I kept getting an error though whenever I tried to start it. Ensuring that the Revive executable is running as an Admin stopped the errors for me and finally allowed the game to work. I'm running on medium-ish settings, and so far everything looks pretty good. The only other strange thing I've noticed is that in the game Settings menu, there's a red "x" instead of a checkmark for my GPU, even though I have a 1080Ti and the game req's state a 1080 minimum, so not sure what's up with that, but it doesn't seem to be affecting anything so far.

[mapotter99]

@CrossVR I’m using an Index with SteamVR.

On Revive 2.1.1.0, the menu item selection (using Index controllers) is SUPER finicky, and requires multiple trigger presses to select items. I still can’t adjust the graphics settings. If I start playing the game, it crashes to the Home Screen within 5-10 minutes.

I tried Revive 3.0.0 beta, and the game won’t start with an “unknown error”.

[ElricOfMelnibone]

@CrossVR I’m using an Index with SteamVR.

On Revive 2.1.1.0, the menu item selection (using Index controllers) is SUPER finicky, and requires multiple trigger presses to select items. I still can’t adjust the graphics settings. If I start playing the game, it crashes to the Home Screen within 5-10 minutes.

I tried Revive 3.0.0 beta, and the game won’t start with an “unknown error”.

Ditto with the menus being really finicky. For the vertical scrollbar, I have to pixel-hunt the bar to get the right spot in order to move it. For horizontal menu arrows, it takes multiple clicks to get them to activate. I did manage to change graphics items after a bit of work. I turned TAA off and set textures to high with no AA at all, and that works well for me. I also lucked out in that my game hasn't crashed yet. I keep Steam resolution at 100%, same as in-game. And that's all with the latest Revive version as linked in this thread.

[mapotter99]

@CrossVR I’m using an Index with SteamVR. On Revive 2.1.1.0, the menu item selection (using Index controllers) is SUPER finicky, and requires multiple trigger presses to select items. I still can’t adjust the graphics settings. If I start playing the game, it crashes to the Home Screen within 5-10 minutes. I tried Revive 3.0.0 beta, and the game won’t start with an “unknown error”.

Ditto with the menus being really finicky. For the vertical scrollbar, I have to pixel-hunt the bar to get the right spot in order to move it. For horizontal menu arrows, it takes multiple clicks to get them to activate. I did manage to change graphics items after a bit of work. I turned TAA off and set textures to high with no AA at all, and that works well for me. I also lucked out in that my game hasn't crashed yet. I keep Steam resolution at 100%, same as in-game. And that's all with the latest Revive version as linked in this thread.

I found a Reddit that said to release the grip when navigating the menu. That solved ALL my menu problems! I haven’t had any issue with the menus since doing that.

I’ve even been able to play for up to 20-30 minutes without crashes if I consciously try to avoid holding the grip. Not 100% positive the grip is related to the crashes, though.

@CrossVR I almost wonder if the grip is bugging out the game somehow.

[CrossVR]

@mapotter99 It's a known issue in all Echo games. It's not just Revive, the grip button on the Oculus Touch will do the same thing.

[mapotter99]

@mapotter99 It's a known issue in all Echo games. It's not just Revive, the grip button on the Oculus Touch will do the same thing.

Could it be causing my crashing, also, or is that something different?

[webarchitect609]

I want to share how I did manage to get LE2 working well for me:

0) My environment:

• CPU: Intel i7-8700 @ 3.2 GHz;
• GPU: NVIDIA GeForce RTX 2080 SUPER;
• HMD: Valve Index with controllers;
• RAM: 16GB;
• OS: Windows 10;
• Revive: 2.1.1;

1) "Driver" problem. I've noticed the red cross near the "Driver" word in the graphics settings. So I updated to version 496.76. Now there's "✅" at the "Driver".

2) ⚠️ IMPORTANT: Don't change graphics settings while playing. This will cause immediate glitches, even if you switch to the "lowest" preset. Just set the desired graphics settings, but then you must restart the game completely.

3) So far everything works very well at "Low" and "Medium" presets, although "Medium" still causes the red cross at "GPU". At "High" it glitches slightly, but every time you turn the head, even if "Lighting" and "Shadows" set to "Low".

4) Minor problems:

• loading/resuming saved game is very slow(1 minute 10 seconds);
• sometimes one of the controllers remains vibrating without any reason(grabbing and releasing something fixes it; and I had the same issue with LE 1).

P.S.: I'm currently at the point, where Olivia starts wearing suit. So I believe that's enogh to be sure it works well. And I also use the room with huge holographic tree as a place with maximum graphics pressure.

[vvvnew]

I want to share how I did manage to get LE2 working well for me:

0. My environment:

• CPU: Intel i7-8700 @ 3.2 GHz;
• GPU: NVIDIA GeForce RTX 2080 SUPER;
• HMD: Valve Index with controllers;
• RAM: 16GB;
• OS: Windows 10;
• Revive: 2.1.1;

1. "Driver" problem. I've noticed the red cross near the "Driver" word in the graphics settings. So I updated to version 496.76. Now there's "✅" at the "Driver".
2. ⚠️ IMPORTANT: Don't change graphics settings while playing. This will cause immediate glitches, even if you switch to the "lowest" preset. Just set the desired graphics settings, but then you must restart the game completely.
3. So far everything works very well at "Low" and "Medium" presets, although "Medium" still causes the red cross at "GPU". At "High" it glitches slightly, but every time you turn the head, even if "Lighting" and "Shadows" set to "Low".
4. Minor problems:

• loading/resuming saved game is very slow(1 minute 10 seconds);
• sometimes one of the controllers remains vibrating without any reason(grabbing and releasing something fixes it; and I had the same issue with LE 1).

P.S.: I'm currently at the point, where Olivia starts wearing suit. So I believe that's enogh to be sure it works well. And I also use the room with huge holographic tree as a place with maximum graphics pressure.

Thats still not optimal; but i get even worse performance with the G2 even on low/medium settings. I dont think this issue is going to be fixed anytime soon as facebook has abandoned any sort of support for this game and things are pretty much dead on this site as well.

[kleenerStern]

Hey, thought I'd repost my Reddit comment here too, since I finally got it to work flawlessly without any glitches or lags.

Specs: CPU: AMD Ryzen 5 3600; GPU: NVIDIA GeForce RTX 3080 TI; HMD: Valve Index with controllers; RAM: 32GB; OS: Windows 10; Revive: 3.0;

Things I did in order:

1. I uninstalled revive and oculus app.
2. Installed Oculus app.
3. Opened Oculus app, clicked on the blue banner telling me to set up my headset, -> continue -> skip setup -> skip setup.
4. Installed Revive 3.0
5. closed everything.
6. Right clicked on Oculus Shortcut -> properties -> compatability -> tick run as administrator.
7. Same thing for Revive Dashboard Shortcut and Steam Shortcut (of course you could run those things as admin manually everytime)
8. Started Oculus App (as admin)
9. Started Steam (as admin)
10. Started SteamVR (and the controllers and trackers)
11. If revive doesn't open automatically, start revive dashboard (as admin)
12. In the taskbar all the way on the right side, clicked the little up arrow that reveals the hidden taskbar symbols (like the one for disconnecting usb devices), right clicked the revive symbol that shows up -> click use OpenVR runtime.
13. In Revive Dashboard, clicked on the Lone Echo 2 Image
14. Success :)

[vvvnew]

Hey, thought I'd repost my Reddit comment here too, since I finally got it to work flawlessly without any glitches or lags.

Specs: CPU: AMD Ryzen 5 3600; GPU: NVIDIA GeForce RTX 3080 TI; HMD: Valve Index with controllers; RAM: 32GB; OS: Windows 10; Revive: 3.0;

Things I did in order:

1. I uninstalled revive and oculus app.
2. Installed Oculus app.
3. Opened Oculus app, clicked on the blue banner telling me to set up my headset, -> continue -> skip setup -> skip setup.
4. Installed Revive 3.0
5. closed everything.
6. Right clicked on Oculus Shortcut -> properties -> compatability -> tick run as administrator.
7. Same thing for Revive Dashboard Shortcut and Steam Shortcut (of course you could run those things as admin manually everytime)
8. Started Oculus App (as admin)
9. Started Steam (as admin)
10. Started SteamVR (and the controllers and trackers)
11. If revive doesn't open automatically, start revive dashboard (as admin)
12. In the taskbar all the way on the right side, clicked the little up arrow that reveals the hidden taskbar symbols (like the one for disconnecting usb devices), right clicked the revive symbol that shows up -> click use OpenVR runtime.
13. In Revive Dashboard, clicked on the Lone Echo 2 Image
14. Success :)

I believe it does work well with the index but not WMR headsets like the reverb G2. For me its not even loading into the game these days, just gets stuck on the menu.

[kleenerStern]

Oh sorry, kind of got a bit too excited because I finally got it to run after not even seeing the intro screen and wanted to share. Though I must say I’ve had two different errors and then on some try after that it always also crashed in the title screen, so maybe setting admin privileges everywhere and enabling OpenVR runtime does help even when not on index.

But ofc I have no real Idea about WMR headsets and I’m glad I finally got it to work at all after a long time of not getting any results.

[vvvnew]

Oh sorry, kind of got a bit too excited because I finally got it to run after not even seeing the intro screen and wanted to share. Though I must say I’ve had two different errors and then on some try after that it always also crashed in the title screen, so maybe setting admin privileges everywhere and enabling OpenVR runtime does help even when not on index.

But ofc I have no real Idea about WMR headsets and I’m glad I finally got it to work at all after a long time of not getting any results.

Actually tried reinstalling revive (2.1.1, not the beta version) and got it to run after i opened both oculus and revive with admin privileges. Btw my default settings are low, what graphics settings do you use? I use a 3080 btw and running on a Reverb G2