I don’t think it’s a bug.

All HMDs render higher than their panel resolution to account for lens distortion. 100% render resolution in SteamVR is what gives you native resolution on the headset.

Someone on Reddit said G2 was rendering way too high at 100%, but I don’t think that’s true - it is actually an equivalent increase to what you get on the Quest 2 at 100%.

Running 50% in SteamVR is halving the native resolution. Unfortunately it is kind of necessary for performance. :)

Sure, but not 2x higher. At least from what I was reading/viewing, for the G2 specifically, SteamVR gives the default resolution as double what it should be.

As I said, it’s the same for Quest 2 and no-one is saying that is bugged.

The panel on the G2 is 2160, and 100% is around 3100. It seems in line with other HMDs to me, e.g. Valve Index and Vive Cosmos are both similar ratios.

Remember it has to render two view points. So so the G2 which is 4K… it’s really 4K x2. I know there are some trick they do to save performance in rendering two similar views, so maybe it’s 4K x1.7.
Then add a x 1.3 on top of that to accommodate fro the lens distortion effect.

Then add on top of that that you need stable 72-90 fps or it will fall down to half.

And still it manages to look better than the rift on my decrepit old 1070.

https://www.youtube.com/watch?v=i3NQptr7CEk

Now that I’ve a little more time, here is the evidence that the Reverb G2 SteamVR resolution is not bugged. Or if it is, it is not by as much as some are hoping. :)

The Quest 2 and G2 SteamVR numbers are mine, while the others are sourced from the internet.

Sure, the G2 is a little higher than the others but it seems in the ball park of the more modern HMDs:

HMD Native Panel SteamVR 100% Pixel Count Increase
Reverb G2 2160x2160 3180x3100 2.11x
Oculus Quest 2 1832x1920 2496x2592 1.84x
Valve Index 1440x1600 2016x2240 1.96x
Vive Cosmos 1440x1700 2016x2380 1.96x
Rift S 1280x1440 1648x1776 1.59x

Oculus in general seems lower, and the Rift S was really low!

Well, whether it’s by design or a bug, it’s still a resolution that not many current systems can push the GT2 at at a decent frame rate in detailed games. Fine for simple VR-specific stuff, but likely needs to be cranked down for stuff like simulations and racing games.

@Denny - thanks for the spacey sim suggestions. They’re awesome!

What should I use to measure FPS?

Also, is there an easier way for me to click SteamVR than from the Desktop? Once again I feel like I’m doing something wrong. When I’m in the MS House, I choose desktop, and then I see a cascading set of infinity desktops in front of me and I desperately try to click the tiny Steam logo in my tray to try and click the SteamVR icon.

I’m dumb :)

The windows button on your controllers should bring up a menu. You can get to steam vr from there. I usually just start steam vr from my desktop or from steam before I put on the headset.

So did you buy that $175 kit? Does it impact your fps?


Another weird question for everyone. If you’re both near-slighted and far-sighted, which glasses should one be trying with the VR headset? Glasses for viewing stuff far away? Or reading glasses? I have crappy eyes.

I’m getting confused trying to set up my Quest 2 and Virtual Desktop just right.

What resolution / settings should Virtual Desktop be set at on the headset? What about the settings within the app on the desktop PC? And then what about Steam VR settings? They all overlap somewhat and I feel like I’m spending more time tweaking than just playing, yet while tweaking sometimes changes have huge performance implications and I don’t really understand why.

I don’t have an answer for you, but I feel the same way.

Calling out to anyone with Star Wars Squadrons. Finally gave it a go, and while super cool - I’m having issues. For lack of a better description, the controls feel very “swimmy”. I don’t know if it’s VR, or if it’s my T.Flight Hotas. I adjust sensitivity from 100% to 200% but besides being a bit snappier it still feels like I’m moving through jello and staying on target is nearly impossible.

It’s going to depend on your hardware as always, and your network setup. My PC is wired to a Wifi 6 router.

PC Streamer:

I use defaults apart from ‘automatically adjust bitrate’, which I disabled as I found it set the bitrate too low.

VD Settings, which is for the desktop streaming:

  • Use optimal resolution. Desktop is always streamed at 1080p and this automatically changes it to that resolution.
  • Frame rate: 90. Match the Quest 2 refresh so it doesn’t flicker
  • Environment quality: medium. I don’t really know what this does, I thought it controlled the quality of the background environments you can use but I don’t really see any difference between the settings.
  • Desktop bitrate: 15 Mbps. I think this is default, it saves battery as desktop doesn’t need high bitrate.

VD Streaming settings, which is for game streaming:

  • VR graphics quality: high. Sets the rendering and streaming resolution. This setting impacts performance the most. High uses the native resolution of the headset. I’d prefer to leave this at high and adjust the resolution in SteamVR to claw back performance if needed (though I’m not fully sure on which method is optimal).
  • VR frame rate: 90
  • VR bitrate: 120 Mbps. I set this as high as I can, as it majorly impacts quality of the video compression. Much under 100 and the artefacts start getting ugly. Will depend on your network setup.
  • Sliced encoding: enabled. Similar to how Link optimises compression. Not supported by all GPUs but give it a go.
  • You can enable the Performance Overlay here too, which will show you where your bottlenecks are. If it shows ‘game’ is the bottleneck you’ll need to lower VR Graphics Quality, SteamVR video resolution, and/or in-game graphics options. :)

SteamVR

Basically I set the video resolution at 100% globally, and use the per-game settings here to adjust lower if needed.

Sounds like you’re coping with a low frameeate hidden by motion reprojection. So try tweaking down.

Yes I did, and no, not at all. The thing does it’s own processing onboard an just puts out a mouse signal to the PC.

This is good advice but I’d recommend trying many bitrates below 120 Mbps too, as low as say 70 or 80, just to get a feel for it. Even when 120 works fine, I sometimes get a noticeable latency improvement by setting it to 75 and find that preferable in a game.

Good point! There is a definite latency hit for the higher encoding levels, so it’s about finding the balance that works for you.

I see around 10ms latency difference between the lowest and the highest bitrate settings.

So I’ve had the G2 for over a week at this point.

Let’s start with the tracking.

It seems fine? All I heard before receiving mine was that the tracking was just atrocious. I rarely have a problem with it. I’m sure the Index’s system has better tracking, but from my experience it has always been the least of my concern. Granted I haven’t tried any of those super fast sword combat style games.

The real problem is the software. Windows, GPU Driver, Windows Mixed Reality, Steam, Origin, Game, SteamVR, Headset. This is the Gauntlet of Hell every byte of VR data for, say, Star Wars Squadrons has to run before actually reaching your eyes. It is an absolute house of cards that collapses about as often as not.

Be prepared to put your headset on to try to launch the game from WMR, only to find that you can’t add Origin titles for some reason, so you take off your headset to launch it from Windows, then put it back on, only to remember that the game doesn’t start in VR, so take the headset off to try to get the game toggled into VR in the options menu, put your headset back on, wonder why controls aren’t registering, take headset back off to find the game minimized for some reason, hit Windows + Y to accept keyboard commands on the desktop, and then alt-tab it back into focus, put your headset back on, and hope it actually works without your headset displaying a solid black or blue screen for no reason whatsoever which means restarting everything and trying again from scratch.

And if it does work, make sure you crank the graphics settings all the way up to whatever the lowest possible options are, and hope your reprojection rate isn’t still 45% even though you have an i9-9900K / 2080 Ti (overclocked). [Spoiler Alert: It might be!]

Or how about the in-game camera? Several cockpit games I tried appeared to default to the room boundary center, so the game menus, or even the in game camera, was centered 6 feet away from my computer chair. Back to Google. I still haven’t figured out how to fix the IL-2 camera, which has me sitting on the floor of the airplane instead of in the chair. None of the re-center buttons fix it. You can go back to non-VR mode and move the default view, but that only made things worse in VR mode. Back to Google.

And this is to say nothing for the initial set-up, which was a bit of a pain in the ass that led to the requisite moment of quiet reflection in which I wondered to myself if my headset was actually dead on arrival (which, judging by forums, is actually Step 2 in the Reverb G2 set-up manual that’s also not included).

The hardware itself is fine, I guess. Having never used another VR system I have nothing to compare it to. The FOV and “sweet spot” both feel small, and do legitimately seem to be better without the OEM face plate, so I’m sure a thinner face plate would be an improvement, which is sad considering how much these things cost.

When everything is working properly (read: when you’re playing Half-Life Alyx), it’s a really great experience. It would be better if it were wireless, but I bought a tether system that ought to help keep the cord out of the way, so we’ll see how that goes.

It’s great technology. The hardware could use another revision. The software is awful. The fact that I’m running into issues in 2021 that, when Googled, come up in forum threads dating back nearly half a decade tells me everything I need to know about what I have in store for me with this platform.

Performance for the most part is poor, and to be honest with you I literally can’t tell if it’s supposed to be or not. I’ve read reviews for the 2080 Ti that had VR benchmarks where people were running these games maxed out and averaging 120 FPS with no reprojection, whereas I’ll get 40 FPS with low or medium settings with 45% reprojection. Is there something wrong there? Is there a setting buried somewhere in the house of cards that I have messed up? Is there a single obscure Windows process that’s throwing a monkey wrench into the works and decimating performance? Maybe! Have fun spending the rest of your night searching web forums and trying to figure that out.

I’ve been gaming on PC since 1989 and building my own systems for over 20 years, so to say I’m used to PC gaming jank would be a bit of an understatement. I specifically avoided getting into VR until now because I wanted to wait until the technology matured enough to not be a total shit show. After a week with the G2, it feels like I should have waited another five years. I will stay with it and try to get everything working smoothly, but it would be cruel to recommend this to someone who wasn’t ridiculously patient and an expert on diagnosing PC gaming issues.

There’ve been a couple of requests for a step by step guide to enable Virtual Desktop with the Steam SideQuest patch on the Quest. This is the closest I’ve seen.

Holy cow. You just wrote every single detail that’s been in my mind for the past week, as I too have tried to make this work well. When we played simple games it works like a charm. But now that I’m trying games with real meat it’s been a struggle. I too wonder if there’s a setting or something going on that is holding back performance. For instance, Star Wars Squadrons looks like mush (outside of the cockpit) and performance is still poor. Having to turn graphic settings down so far seems to defeat the purpose of VR if it makes details look so bad. I have a few questions…

  • Do you need to run at 90 fps to have stuff feel snappy? Or can you set the refresh rate lower so you can run in more detail. Like 70 or 80 Hz?

  • Is vsync supposed to be on?

  • Should I be playing games in full-screen or windows borderless mode? (does it matter?)

  • Those of you with Star Wars Squadrons… can you take a screenshot of your graphic settings?

  • Same for IL-2 and MS Flight Sim? Then I will know if I have a driver issue if I can’t get it to work right.