Quad View square visible at night

1 tag is requred - add it in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
The SU2 Beta “Foveated Rendering” VR graphic settings improves FPS by ~15%, but the higher rendered ‘middle squares’ of the Quad Views Rendering are visible during night flights what breaks the immersion.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time … at night flights.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Enable Foveated Rendering in the VR graphics settings.
  2. Start a flight at dark/night with a Cessna 182 Basic from LAS.
  3. You can see the middle square being sharper but also a bit darker, as if it has a different transparency than the area around the square. The left and right side of the square are easiest to spot.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are currently plugged in, as well as your VR headset? Please name all of them as there could be a potential conflict.
Pimac Crystal (OG)

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?
RTX4090

[PC Only] What other relevant PC specs can you share?
i9, 64Gb

MEDIA

Please add a screenshot or video of the issue occurring.
See the attached picture. Between the two added blue arrows you can see the difference between the middle block (left side) and surroundings (right side).
Edited: I’'ve attached another picture which clearly shows the darker square (at a since a SU1 Beta overexposed Manhattan heli-pad).

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Yeah. Having the same problem.

Quad view square is also visible when flying in clouds. It’s hard to get a screenshot of it, but it looks like a flickery dusty box floating in the center of the screen.

1 Like

I am also getting the FFR dark square but I am also finding ZERO FPS benefit with FFR on or off. I am using Pimax OG. If anyone can advise what I should be doing to make it work I would appreciate it. Thanks

I checked two boxes: in MSFS '“fovearated Rendering” in VR Graphic settings and “Pimax OpenXR Quadviews” in the Pimax Play (Games tab). That gives me the FPS increase.

Thanks for this. Are you using the Pimax openxr codec or are you using pimaxXR?
Also, what are you using to see your fps?
Do you use oxrtk? If so what are your settings on there on the first menu screen such as eye tracking, fixed foveated, turbo mode etc

Using the Quest 2 and I’m have the same issue. I do see a significant FPS bump (5-8fps) using foveated rendering. I’ve noticed city lights also become blurry/hazy when they’re within the square.

Pimax OpenXR. I’m also using Openxr Toolkit, but only for the FPS overlay. No foveated, turbo etc.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:
• S

Same here..

I have a Quest 2 and 3, neither of which exhibit this behavior. I run wired with the link cable / meta link connection. DLSS 4 (via DLSS swapper) . All drivers / software at latest builds. I can tell foveated rendering is ON if I look hard enough at the edges (really can see the lower res there). I cap my FPS at 40, and notice a ~10% drop in GPU usage, which is nice! Not here to brag about me not having this dark square issue, just hope my information helps with the DEV’s getting it figured out.

plyanthony321 Try using DLAA mode at night with a lit airport ramp and look around then report back please with both headsets thanks.

Software using? (OpenXR Toolkit)

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes, I have the same issue
Provide extra information to complete the original description of the issue:
• Some lights (at least, added earlier by me), switched off, when I get closer to them.

If relevant, provide additional screenshots/video:

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

the outside square also seems to have different LOD for lights, see video below.

If relevant, provide additional screenshots/video:

I have that square at all times… it’s very visible while in IMC in the daytime or anytime the background is a similar color.

I don’t even have FR on in the sim (though I do have it setup within the HP reverb )

The team was unable to reproduce seeing visual artifacts in 1.4.10.0 on an RTX 3060 with a Quest 3 when flying at night. Changing the DLSS settings had an effect on the performance of the game in VR, but did cause any visual artifacts.

Please let us know if you are still experiencing this issue, and if so, can provide more details. Thanks!

In 1.4.11.0 it’s still there (with a Pimax Crystal), but too small to capture in a screenshot I noticed. However, during daytime it’s a little more visible (see attached picture). Settings DLSS / Auto, Sharpening 150, no reprojection, dynamic settings ON. Nevertheless … I’m happy with the better clarity and performance in this latest build!

Here is another thread with the same problem and better pictures where you can see the problem. The conditions are a bit of a pain to reproduce, but I think there are enough pointers.