PSA: Reverb G2 small sweet spots, observations and solutions

Thank you for the additional details and articles, I never thought about our eye CA either but now it might explain me better why I do perceive red and blue bars drawn on a black background as if they were at difference depth. Now this LCA aspect could be an explanation I see red/blue fringes in the G2 when wearing it above/below the center line/sweet spot, and why I see the image blurrier when I look in the center. However I’d suspect I would have a similar effect with any headset, but I don’t with the Valve Index. Actually the Index allows a wider range of positions without any difference regarding CA and sharpness which is great (they use dual elements lenses). My G2 is not which would indicate it has a defect.

So if I get it correctly, in your G2 you can see clear text closer to the 2nd image (in “what I see +1 correction glasses”) than in the 1st image, and it appears like in the “Partial Solution” screenshot (white on black), and not like in the “Changing the point of view” screenshot (white on black with red/blue fringes). Did I understand it right?

Would you mind if this is correct, trying to lower or raise ever so slightly the G2 and see whether you can notice red/blue fringes appearing in this case?

Otherwise, if you do see red/blue fringes already, would you mind trying lowering or raising the G2 up to the point both disappear when looking at anything white over background in the middle (like text preferably), and when it occurs, is the text then becoming less sharp for you?

Hi Captain,

If I tilt the heasdset to a rather extreme angle, I perceive the blue fringes you described. It’s slight but definitely present. If I wear it normally, it’s all white, as described by JALxml.

Another thing though, not sure if this is related, but the screen of GPS in the cessna172 classic does appear to me in 3D, magenta lines and blue line do not appear to be on the same plan, if that make sense.

1 Like

I would say the text in the floating Windows Mixed-Reality settings window in the post here: PSA: Reverb G2 small sweet spots, observations and solutions - #79 by JALxml is much closer to the clarity of what I see than either of the two images that you’re asking me to compare in your post here: PSA: Reverb G2 small sweet spots, observations and solutions - #108 by CptLucky8. The text in both images included in your post is very, very blurry compared to what I see and the top rightmost image of the YouTube video preview PSA: Reverb G2 small sweet spots, observations and solutions - #109 by JALxml is closest to what I see when using MSFS.

I don’t notice any striking discolorations but later today (1/25/21), I’ll try moving my G2 headset around and see if I can induce any chromatic aberration and let you know.

I will return my G2 and get a Quest2. For me the sweet spot is just too small, to be acceptable. Secondly, the GPU power needed for the native resolution will be the the rtx40XX ot rtx50XX series. Until then, they will have an G2 with a better sweet spot on the market I guess.

I confirm this observation of GPS in “steam gauges” C172 and Reverb G2.

@JALxml @AIRBORNE4795 @stekusteku

I should have clarified the point you’re raising about the white text in my screenshots appearing fuzzy and this is just due to the way I took the photo and unfortunately distracting from the points I wanted to highlight. For this reason I’ll try differently using a screenshot of the DCS altimeter seen in the through-the-lens video.

This is what I see in the G2:

1. Blurry + No CA

When I align the eyes in the sweet spot:

NB: It is blurry because I can’t focus on the display distance and only if I force my eye to see closer it is becoming sharper, but there is no or minimal CA visible.

2. Sharp + No CA

When I use +1 correction glasses:

NB: It is just what I need to add in order to be able to focus on the gauge without effort on the eyes, whereas I normally need +2.5 reading glasses.

3. Sharp + CA

When I look from slightly above or below the sweet spot (needed for point 4.):

NB: It is sharp but with chromatic aberrations. These CA are due to not being aligned to the lens center and looking to the gauge in a slanted way (see my attempt to picture the “slanted” way above), that is I’m for example looking at the gauge with my eye above the center of the lens, with the gauge center below the lens center. However in looking this way the gauge is sharp and I suspect it is because with the eye at this position against the lens, I’m seeing the image at a difference focal length.

4. Sharp + No CA

When I look from slightly above or below the sweet spot with distortion correction using the registry keys:

NB: The registry keys are distorting the red and blue channels separately in order to make them join together with the green channel, eliminating the fringes and producing white lines again. These are undocumented Dwm registry keys (REG_DWORD):


I set ColorDistortion to 1 (enable) and I change Blue value to 0.995 (ColorDistortionB: 995) and Red value to 1.005 (ColorDistortionB: 1005) for my G2 in order to transform image 3 with the fringes to 4 without.

NB: Any change is immediately effective when the presence sensor activates. In other words: remove headset, edit registry values, put the headset back, see the results!

1 Like

Now we need someone to make a personal eye test app that can adjust these hidden registry values on a custom basis.


Look, so far I’m a fan of the G2, and while I’m aware that some people don’t like the sweet spot, this being my very first VR headset, I didn’t (and don’t) know what to expect, or what’s acceptable and what’s not. I probably am going to get one of those face mask mods to get it a bit closer to my face, but I don’t even know where to go to get one.

But all that is irrelevant to the point I wanted to make…

And that is please do NOT buy an Oculus device!! Get anything besides that. The controls and restrictions that FB is putting on them are completely unacceptable, and we as consumers cannot reward that behavior by purchasing their products. I’ve even seen unconfirmed rumors that Germany literally made it illegal for them to sell them there because of these issues. That is something I would ordinarily be opposed to, but because of the unique circumstances with Oculus, FB, and them trying (and so far succeeding) in cornering the VR market completely, I’m making an exception to my normal objections to government doing such a thing.

So as much as I want to see the G2 succeed, sell it, send it back, do whatever it is you feel is appropriate, but replace it with anything but an Oculus.

Thank you for letting me rant, this is a topic that has me peeved off, and has become kind of a pet project for me. Not that little old me is going to win going up against FB, but if I can save even a small handful of people from making that mistake, I’ll feel better.


@CptLucky8, what does NB: mean?

Nota Bene (it is latin):

This is trial and error and you usually change the values in an opposite fashion: raise blue/ lower red (or vice-versa @KevyKevTPA this one is Latin too :wink: )

The neat thing about these registry keys is that you can see the change immediately: every time the headset sensor is detecting presence, it reloads the registry values, so that you can quickly remove HMD, change values, put back HMD and compare.

I’ve posted the above to compare and document each one experience against the 3 possible outcomes in the end: sharp, sharp but with fringes, blurry.

Let’s try to compile some feedback.

Do most of you with a G2:

  • Usually need reading glasses?
  • See sharp like the 2nd picture (no fringes)?
  • Or like the 3rd picture (with fringes)?

[updated with the question about reading glasses]

PS: Thank you for any one participating and I hope this will in the end reveal it is not a widespread problem but just mine because in this case, I’d be more than happy sending it for RMA and not thinking I’ve a useless piece of VR equipment, especially since with the latest SteamVR beta I can run the Index comfortably at TAA100 SS124/128 (EFIS/GA) and at this level I can read small green EFIS lettering without any issue in the Index.

Closer to pic #2 for me

1 Like

Yep, same for me. Picture #2 would be the visual clarity with my G2.

I’m still rummaging around on comparative tests (have to keep wife happy doing real world things!). I notice there is a thread on chromatic aberration in MSFS and the difference in 2D vs. VR settings: Here's how you turn off post processing effects! (Chromatic aberration for example)

When I look in the VR section of my UsrCfg.opt file, here’s what I find:

Enabled 1
EyeAdaptation 1
ColorGrading 1
Sharpen 1
Fringe 0
LensDistortion 0
Dirt 0
LensFlare 0
FilmGrain 0
Vignette 0
LensBlurMultiplier 1.000000
FringeMultiplier 1.000000

The OP post in the thread that I cite says that setting FRINGE to 0 removes the “artistic” chromatic aberration effect, at least in hangar scenes. What are your VR UserCfg.opt settings, @CptLucky8 ? Mine is 0.

I did my own color “calibration” image. hah.

Opening that image on paint and then using desktop view at the cliffhouse I can easily change the registry values and see how they behave in the headset. When using the default values for all color channels I get a massive blue offset from the red and green channel, but yellow channel is more or less aligned. Tip: Close one eye, move close, look at the center dot. Then move your view left and right repeatedly. You shoud see a blue halo separating from the line as the view changes from left to right.

That speaks of a huge color misaligment bug in the headset. Makes me wonder what else is fubared.

The good thing is these issues can be fixed on software updates.

1 Like

Also, @CptLucky8, I don’t seem to have any of the Color Distortion registry keys you cite. I have also blithely disregarded your advice and am running Nvidia driver 461.09 with GeForce Experience(!), if that might make any difference.

@JALxml The UserCfg.opt settings are just for artistic rendering in 2D.

@JALxml You have to manually create them, they’re undocumented otherwise (thus not present)

@Altsak Thank you for this, it tells me I’m not mad yet! This blue shifted copy is what I can see and I’ve reported very early indeed: Use a G3000/1000 aircraft, look at any purple text, there is a visible blue copy of the same text overlapping which can go up to 1/2 letter size depending on distance to center.

The blue copy might not be anti-CA, but uncorrectable light leakage instead:

When you see bright text on a black background, you’re going to see several “ghost” images of that text due to light leaking across color channels on the panels. You’ll see the same thing on a Quest 2. This particular light leakage isn’t correctable since the neighboring pixels are black or near black, so there’s no light to use to compensate for the leakage.

PS: I got this one from Alex Vlachos via a WMR contact so I believe he knows about this!

The thread that I cite claims that there are TWO separate settings sections, one for 2D, one for VR, and when I look in my UserCfg.opt file, I do see two separate PostProcess sections and the one I quoted in my post above is under the VR setting. And the settings values are different for 2D vs. VR Why call it “VR” if it only applies to 2D? When in MSFS, I also seemed to find different settings for Settings, General, Graphics, depending on whether I was wearing my G2 or not (the pressure sensor in the G2 would trigger the switch between the two, so I actually set my graphics settings in MSFS while wearing my headset, which is hard to do since I can’t see any reference settings in a browser windows (maybe now that I’ve switched to windowed MSFS I can figure out how to do that).

On the undocumented, I thought you might mean hidden registry keys so I ran psexec.exe from Windows SysInternals, i.e. " psexec.exe -s -i regedit.exe" at an admin command prompt but didn’t see any hidden registry keys under the ExtendedComposition key, just to report that adventure. Same keys, same DWORD values. Since I’m not having a problem with my headset/my eyes, I don’t think I want to add the undocumented keys but I’ll try tilting the headset as you previously suggested to see if I can induce chromatic aberration (it’s a bit of an operation to set up MSFS in VR for me, uncoil the cable, move chairs, turn on USB hub switches, etc.).

I believe it is appearing in the VR section only because they didn’t fundamentally changed the load/save settings code. They’ve just provided 2 slots (2D + VR) and this saves both slots settings. It is only there but it is not used when in VR. As for the registry they are undocumented. You won’t find them in your search engine either (well now you’ll start to get some since the cat is out) :wink:

As for shifting the eye position, it is on one hand producing the blue/red fringes I’ve illustrated, but more importantly to me, it turns the white blurry text and eye focus effort to make it clearer, into sharp text surround by color fringe with no effort to see clearly (well a little bit of effort, enough to start feeling some fatigue after 1h). This is the position I’ve to put the headset in order to make it clearer, hence, the need to also compensate the fringes with the undocumented registry keys.

1 Like

Here’s a simple test for chromatic aberration. I see none in normal viewing position unless I displace my G2 from my normal wearing position. The test image is a Windows 3D Builder BLACK cube with a WHITE lightning bolt on its front face and since this site doesn’t take .3MF uploads, I’ve linked to the file on my OneDrive account. In my normal G2 viewing position, I only see a clean white/black edge, say, along the border of the bolt. If I tilt the bottom of my headset out and up from my face, I see a yellow red birefringence along a border. If I tilt the top of the headset out and down from my face, I see a blue birefringence instead. But otherwise in anywhere near a normal viewing position, I see an EXCELLENT image.!ApngLox0gfb7j4dDVsbXBOQXF9BaQA?e=KnilQ0

OK. The link will open in either Edge or Chrome and show you the 3D cube. You can download it.

In the Sky Loft view in VR, click the Windows button on your WMR controller, when the Windows interface pops up, click All Apps on the right side, then 3D Viewer app, then from the 3D Viewer menu at the top, pick FROM FILE, and open the Cube with White Lightning. Shoot the front edge and pull the cube in 3D as close to your “eyes” as you want to view the object. When right in front of my face, I have NO CHROMATIC ABERRATION with an HP Reverb G2. I will further explore my settings but as mentioned above, I’m running the Nvidia driver 461.09.

So, in answer to @CptLucky8 , yes, if I want I can induce chromatic aberration in my G2 but normally I have as close to zero as I can tell. The CA I get by tilting my headset off a proper face mount as above is obnoxiously obvious.