RealDCSpilot

Just to make sure, it's the opposite effect. A bigger FOV lets objects appear smaller in the same image space (same frame size for both FOV settings). The farther away the more impact it has. A bit more information about the scene i rendered: The greenish-yellowish box on the left is 1,8 meters high and positioned very close to the camera, the tall column in the center is much more far away and 22 meters high and the sphere is 18 meters high. It maybe a bit hard to see in the miniature top/down shot. In the camera view you can clearly see that the 1,8 meter object is only slightly affected, while the big objects in the distance are much more affected (besides distortion effect that affects the perceived position which is negligible for now). I also have a direct theory why DCS slightly misses the correct dimensions in VR. DCS is the only VR application i know that manipulates FOV of it's VR camera rig in realtime. The VR Zoom function does exactly that. If you press the button, a linear interpolation is started that reduces FOV for both eyes in a timeframe of about a second from the start value (let's call it A) to a much more narrow FOV of value B. If you let go of the button it interpolates back to value A within a second. My theory is that value A is simply a bit off by one to two degrees.

Well, i can prove the effect of FOV affecting perceived world size. Changing FOV has the opposite effect of IPD or "camera distance". IPD changes the perceived size of objects close to you drastically and has almost no effect of objects far away. FOV does basically the opposite, close objects aren't affected much, but the more the object is away from you the bigger the effect will be. So my theory is that the FOV in DCS's VR camera rig is off by a couple of degrees.

It's sad to see that Polychop is up for bad news again. As if 7 years with no helicopter flight model for the Gazelle wasn't enough.

@Gizmokev Hey man, just asked myself... How do you think about this today? A lot of things happened, after 7 years we finally got a helicopter flight model, now the CEO fired all the staff who basically saved his company and tried to mitigate his bad decisions. Also the Kiowa got released, but the CEO (also graphics artist) did an amateur job on all textures. Now Polychop is not able to support both modules anymore...

@Zligor Consider switching to Win11 when reinstalling Windows. It has the much better CPU scheduling and ReBar implementeation. HAGS should run without problems not like on Win10 where it is hit and miss. I can't say anything about smearing, not really something that is noticeable on my device. Mine is from the first batch when it got released. Is production quality that random with the PSVR2??

With only 68% super sampling every headset will look blurry for sure. It's a drastically low resolution. First of all, in SteamVR you can't change super sampling during runtime, it'll do nothing. You have to restart DCS (or any other VR app) every time you change this in Video Settings. Also make sure that Throttling Behaviour is set to fixed and the HMD is running in 120 Hz mode. Then check your system if any of the former Quest 2 tweaks are still in place / running in background... get rid of them. OTT and whatever. Also make sure SteamVR is the main OpenXR handler. For Quad Views settings check my earlier posts for a base to start on (there are two posts, take the newer one). Also check Quad Views log file, and DCS's logfile, they will post the settings and resolutions that are applied for the final images per eye. Make sure you have the latest PSVR2toolkit installed (with SteamVR integrated eye tracking). Also check if you have the latest DLSS dll running and try "Performance" setting with Preset K.

Good to know! I'm on SteamVR beta all the time.

Reading the specs of Pimax's DreamAir series caught my attention. It basically kills the BSB2E on all aspects. I'm waiting for someone releasing a small lightweight, high quality and high fov headset for years now and what started with BSB and Shiftall MeganeX seems to move in the right direction.

Yeah, this is something i noticed too. The way to small looking full moon brought me to this. This isn't coming from IPD, this is a result of a tad to wide fov rendering per eye on ED's VR camera rig in game. Would really like to see some fact-checking on this or really like to get this setting exposed in VR settings.

Version 1.3 of PSVR2toolkit got released. It now uses internal SteamVR eye tracking. It's recommended to deactivate/uninstall the OpenXR eye trackers app. https://github.com/BnuuySolutions/PSVR2Toolkit/releases/tag/v0.1.3

Yeah, good point. And the PSVR2 brings so much to the table now, best PCVR/Playstation entry class headset because of pricing and even some benefits on top that you can't get even beyond spending 1K.

That's my old config, check a few posts later. Something is very strange on your end. You have set 150% now and the SS resolution is 5872x5992 ??? That is crazy high, before that 160% was ~3200x3200... (???) You may have bricked your VR render pipeline somewhere in your system sometime ago. Something is messing with your settings. I'm into VR for 11 years now, always looking to get the best out of it. The PSVR2 is one of the most color correct headsets i've seen. Also very powerful with brightness and contrast (it can do HDR so no wondering here). And it's a relieve to see OLEDs in action again after years with LCD headsets. Sure QLED in the QP is not that bad when it comes to similarities in image quality, but these PSVR2 OLEDs absolutely shine in VR.

Certain things look wrong on your end. I have no idea why you have trouble finding the right settings. These values are way to low for a good resolution for PSVR2. No wonder it doesn't look sharp. On my system Steam resolution on 150% means 4164x4244 pixels per eye. And set 120Hz if you want the panels performing fast. This should be your basic setting, you even have better hardware than me. From there DLSS performance mode in preset K and DFR with Quad Views does the rest. I posted my latest QuadViews setting file a couple of pages ago. Something is strangely wrong on your end. Maybe something set globally and even affecting your QP performance. Here is what QuadViews does to rendered pixel amount, reducing a whopping amount of 35.344.032 pixels to only 8.474.352 pixels that are actually needed to deliver a crisp image in the eye tracked focus view box at 1822x1856 pixels. 2025-09-14 07:17:08 +0200: Found option 'smoothen_focus_view_edges=0.2' 2025-09-14 07:17:08 +0200: Found option 'sharpen_focus_view=0.69' 2025-09-14 07:17:08 +0200: Found option 'turbo_mode=0' 2025-09-14 07:17:08 +0200: Found option 'horizontal_fixed_section=0.25' 2025-09-14 07:17:08 +0200: Found option 'vertical_fixed_section=0.25' 2025-09-14 07:17:08 +0200: Found option 'peripheral_multiplier=0.22' 2025-09-14 07:17:08 +0200: Found option 'focus_multiplier=1.25' 2025-09-14 07:17:08 +0200: Found option 'debug_eye_gaze=0' 2025-09-14 07:17:08 +0200: Found option 'debug_focus_view=0' 2025-09-14 07:17:08 +0200: Found option 'vertical_fixed_offset=0' 2025-09-14 07:17:08 +0200: Found option 'turbo_mode=0' 2025-09-14 07:17:08 +0200: Eye tracking is supported 2025-09-14 07:17:08 +0200: Recommended peripheral resolution: 916x934 (0.220x density) 2025-09-14 07:17:08 +0200: Recommended focus resolution: 1822x1856 (1.250x density) 2025-09-14 07:17:08 +0200: Stereo pixel count was: 35344032 (4164x4244) 2025-09-14 07:17:08 +0200: Quad views pixel count is: 8474352 2025-09-14 07:17:08 +0200: Savings: -76.0% 2025-09-14 07:17:17 +0200: Session is using quad views 2025-09-14 07:17:17 +0200: Edge smoothing: 0.20 2025-09-14 07:17:17 +0200: Sharpening: 0.69 2025-09-14 07:17:17 +0200: Turbo: Disabled These resolutions go through DLSS end deliver these values from the DCS.log: 2025-09-14 09:16:10.395 INFO DX11BACKEND (16904): Use DLSS preset 'K' 2025-09-14 09:16:10.436 INFO DX11BACKEND (16904): DLSS successfully initialized, 460x468 -> 916x936 2025-09-14 09:16:10.436 INFO DX11BACKEND (16904): Use DLSS preset 'K' 2025-09-14 09:16:10.473 INFO DX11BACKEND (16904): DLSS successfully initialized, 460x468 -> 916x936 2025-09-14 09:16:10.473 INFO DX11BACKEND (16904): Use DLSS preset 'K' 2025-09-14 09:16:10.511 INFO DX11BACKEND (16904): DLSS successfully initialized, 912x928 -> 1824x1856 2025-09-14 09:16:10.511 INFO DX11BACKEND (16904): Use DLSS preset 'K' 2025-09-14 09:16:10.548 INFO DX11BACKEND (16904): DLSS successfully initialized, 912x928 -> 1824x1856 The result is the absolute best performance and antialiased image quality i've ever seen in all those years in DCS. I also don't get what you mean with "oversaturation" and color bleeding, it's definitely not the case. Something is really messed up on your end. Maybe too much fiddling with system values over the years? Actually the huge color bandwidth of the OLED panels are able to show even more colors now compared to what i have seen with compressed video over VD back in the days. In the Mi-24P you have the Petrovich VR overlay menu which shows in 3 colors in fine lines in what firing state he is. Now i see white, orange and green, before that in VD even with 10-bit HEVC video encoding i could only distinguish between white and green. Orange was totally lost due to compression. There is one thing you should check, SteamVR does SuperSampling settings two times. Make sure your global setting is 150% and when DCS is running check again if the "per app" video setting is 100%. Maybe you have a hidden downscale there. Otherwise i'm out of ideas, but man something is really wrong on your side.

How does XRFrametools record your latency data? I only see frametime for GPU and CPU, but this isn't latency. Latency is the time how long the already finished rendered frame takes to reach your display panel. The stuff that is shown in VD's frame info display. XRFrametools would need to have an app running on your HMD to measure that data.

@Qcumber Yes, wired directly to the GPU hammers down latency by a lot. This is an important element. Streaming alters the way your mind and body perceive the flight model of each DCS module. If you want to see compression, just fly very low over the huge forest areas in the Caucasus map (south of Senaki maybe...). What i don't get is what you mean with black borders at lower FPS? You should actually reach a much better visual result and fps with your 5080 compared to my 4090. Can you post some logs, Quad View etc.? This is also not quite clear for me. You didn't set DLSS or something? DLSS is an AntiAliasing method(!) Without it, i can definitely see aliasing on the edges of all geometry objects.