Qcumber

Thanks. I've had a look at reviews and the Charlie is very heavy. About 1kg heavier than the TPR. It is also quite big (45cm x 45cm) and has carpet grips so good for keeping in place without a frame. As it's from Amazon I might try the Charlie and if it's not for me get the TPR instead.

Does anyone have any experience with Honeycomb Charlie rudder pedals? I can get them from Amazon for £250. I can also get Thrustmaster TPR for £430. Unfortunately I don't have easy access to Virpil or Winwing so these are not options for me. I know what I want to get but is the extra £180 worth it?

I've tried it and unfortunately it's not for me. I am sending it back. I am not saying it's bad headset and it will be a good upgrade for many users. However, I think the Quest Pro is a better option IF you can get one for a decent price. I paid £300 for my mine. I was lucky to get such a good deal for a mint headset that had hardly been used. There are still some bargains.

I ran another test using your settings. The QP resolution is lower at these settings but still looks better than the PSVR2. The cockpit is sharper than I managed but is still a bit fuzzy compared to the QP. It is similar to what I saw with the Pico 4. I tried a few runs over Syria, and the oversaturation is less noticeable compared to a green map like Normandy. BTW thanks for these settings. I like them. I have tried lots over the years but did not have much success with the edges. 0.33x0.33 with 0.33 edges works a treat. QVFR config smoothen_focus_view_edges=0.33 sharpen_focus_view=0.33 turbo_mode=0 horizontal_focus_section=0.33 vertical_focus_section=0.33 peripheral_multiplier=0.33 focus_multiplier=1 debug_eye_gaze=0 debug_focus_view=0 Here is an excerpt of the log for the PSVR2 set at 150 in Steam VR 2025-09-14 16:20:06 +0100: Found option 'smoothen_focus_view_edges=0.33' 2025-09-14 16:20:06 +0100: Found option 'sharpen_focus_view=0.33' 2025-09-14 16:20:06 +0100: Found option 'turbo_mode=0' 2025-09-14 16:20:06 +0100: Found option 'horizontal_focus_section=0.33' 2025-09-14 16:20:06 +0100: Found option 'vertical_focus_section=0.33' 2025-09-14 16:20:06 +0100: Found option 'peripheral_multiplier=0.33' 2025-09-14 16:20:06 +0100: Found option 'focus_multiplier=1' 2025-09-14 16:20:06 +0100: Found option 'debug_eye_gaze=0' 2025-09-14 16:20:06 +0100: Found option 'debug_focus_view=0' 2025-09-14 16:20:06 +0100: Eye tracking is supported 2025-09-14 16:20:06 +0100: Recommended peripheral resolution: 1938x1978 (0.330x density) 2025-09-14 16:20:06 +0100: Recommended focus resolution: 1938x1978 (1.000x density) 2025-09-14 16:20:06 +0100: Stereo pixel count was: 70370048 (5872x5992) 2025-09-14 16:20:06 +0100: Quad views pixel count is: 15333456 2025-09-14 16:20:06 +0100: Savings: -78.2% 2025-09-14 16:20:16 +0100: Session is using quad views 2025-09-14 16:20:16 +0100: Edge smoothing: 0.33 2025-09-14 16:20:16 +0100: Sharpening: 0.33 2025-09-14 16:20:16 +0100: Turbo: Disabled Here is an excerpt of the log for the QP set to 150 in VD. 2025-09-14 16:44:56 +0100: Found option 'smoothen_focus_view_edges=0.33' 2025-09-14 16:44:56 +0100: Found option 'sharpen_focus_view=0.7' 2025-09-14 16:44:56 +0100: Found option 'turbo_mode=0' 2025-09-14 16:44:56 +0100: Found option 'horizontal_focus_section=0.33' 2025-09-14 16:44:56 +0100: Found option 'vertical_focus_section=0.33' 2025-09-14 16:44:56 +0100: Found option 'peripheral_multiplier=0.33' 2025-09-14 16:44:56 +0100: Found option 'focus_multiplier=1' 2025-09-14 16:44:56 +0100: Found option 'debug_eye_gaze=0' 2025-09-14 16:44:56 +0100: Found option 'debug_focus_view=0' 2025-09-14 16:44:56 +0100: Eye tracking is supported 2025-09-14 16:44:56 +0100: Recommended peripheral resolution: 1520x1592 (0.330x density) 2025-09-14 16:44:56 +0100: Recommended focus resolution: 1520x1592 (1.000x density) 2025-09-14 16:44:56 +0100: Stereo pixel count was: 44457984 (4608x4824) 2025-09-14 16:44:56 +0100: Quad views pixel count is: 9679360 2025-09-14 16:44:56 +0100: Savings: -78.2% 2025-09-14 16:45:04 +0100: Session is using quad views 2025-09-14 16:45:04 +0100: Edge smoothing: 0.33 2025-09-14 16:45:04 +0100: Sharpening: 0.33 2025-09-14 16:45:04 +0100: Turbo: Disabled

I have a lot of experience with VR headsets.over the last 6 years. Rift S, Pico 4, Quest Pro. My PC is a new build. Only 3 months old. I keep mods to a minimum. I based my calculations on the base panel resolution of 2000x2000 and wanted to make sure that I was comparing like for like. With the extra x1.5 from QVFR the equivalent resolution of the foveated region is 4800. That should be more than enough. I did try going higher to about 6000 but there was no further improvement. In this case both the PSVR2 and the QP had the same (within a few percent) resolution. Ideally I would have compared the QP with Steam VR but I couldn't get QVFR to run properly. I did try at 120Hz. The reason I chose 90Hz for this test is because it is the highest the QP will go. Maybe I have a bad example of the PSVR2. But to me the colours looked very bright and over-saturated and the chromatic aberrations were bad in the outer edges. Have you used a Quest Pro? I'll run another few runs and save the logs. Then I will do the same using your settings.

I haven't had chance to do the testing I wanted to. The main reason to use XRFrameTools was to measure game performance. I miss-typed in my previous message. I meant frametimes. I played with the two headsets comparing them at the same resolution and same settings in QVFR. As like-for-like as possible. PSVR2: Steam resolution set to 160% for about 3200x3200 pixels. Refresh rate 90Hz. QP: Virtual Desktop set to Godlike (3027x3216) pixels. Refresh rate 90Hz. I tried to use Steam link for this but had issues running QVFR. QVFR for both PSVR2 and QP: foveated region 0.25x0.25 at x1.5, periphery at x0.5. DCS settings were the same for both. I can post them but they don't really matter as I am not including any performance numbers. The PSVR2, even in the sweet spot, is not as sharp as the QP. Not by a long way. Cockpit resolution with the QP is near perfect. With the PSVR2 it always looks slightly blurred. I can read most things in the cockpit without leaning in too much but it never gets as sharp as the QP. Landscapes and distant objects look soft, even mushy in some cases. I have tried AA-off, MSAA, DLAA and DLSS (quality and performance; latest version; preset J and K) and varying degrees of sharpening but it just makes the landscape look very artificial. I just cannot get an image that compares with the QP. The colours on the PSVR2 are very oversaturated. To the extent that there is some colour bleed between objects. There is also a lot of chromatic aberration which can make some objects in the peripheral vision look quite garish. I know I could use Open XR toolkit or Reshade to reduce the saturation but this would not help with the fringing. It is also another XR layer and I prefer to keep these to a minimum. There are other more minor issues that I am not keen on such as the overall build quality, the face gasket (a magnetic one would have been much better), the lack of integrated lens protectors for glasses, the design of the controllers and the Steam VR interface. I realise that the display port connection should give a better experience but for me the Quest Pro has much better image quality. I wish they had released the QP with a Display Port. I think I will send it back and save for a Pimax Dream Air SE.

I am going to take another look today. I'll try to summarise my set up and findings here with more structure. If I get chance I will measure the game latencies using Fred Emmott's XRFrameTools comparing the QP with the PSVR2. Then there will be a more objective comparison if anyone else is considering switching from the QP to the PSVR2.

Good point

I have been testing Steam Link with my QP and am quite impressed. It's much better than when I last tried it a couple of years ago. However, I am having an issue. If I enable QVFR it works fine on the hanger screen but when I try to load a mission it just gets stuck. No crash but long loading times. I have waited up to about 5 minutes but no mission loads. That is the absolute limit of my patience. I've attached the QVFR log. This is the last part where the errors show. Does anyone have any ideas what this issue is? 2025-09-13 16:42:09 +0100: xrLocateViews: XrResult failure [XR_ERROR_TIME_INVALID] Origin: XRNeckSafer_xrLocateSpace(m_ViewSpace, viewLocateInfo->space, viewLocateInfo->displayTime, &location) Source: E:\VS2017\Projekte\XRNeckSafer\XR_APILAYER_NOVENDOR_XRNeckSafer\dllmain.cpp:639 2025-09-13 16:42:09 +0100: xrLocateViews failed with XR_ERROR_RUNTIME_FAILURE 2025-09-13 16:42:09 +0100: xrLocateSpace failed with XR_ERROR_TIME_INVALID 2025-09-13 16:42:09 +0100: xrLocateSpace failed with XR_ERROR_TIME_INVALID Quad-Views-Foveated 13-9-25.log

After using the PSVR2 most of today I am not convinced enough to replace my QP. In my opinion the QP is at least equal or superior in all elements except for the display port link. In testing though I cannot see any obvious compression artifacts with VD or Meta Link and the PSVR2 showed the black borders at lower FPS which I don't see with Meta link. I think my initial thoughts regarding better "softness" and "less jaggy edges" are related to Steam VR rather than the PSVR2. I tried Steam link a while ago and was not impressed. Playing around today I managed to get some impressive results.

Up and running now. XR eye tracking had not installed properly and I needed to reorder the XR layers. Now it's all working fine. Just tweaking settings. My impressions at this stage are very positive. The sweet spot is small but easy to find and keep. Eye tracking is better than the QP. With the QP there is a lot of shadow flickering when transitioning between the foveated region and the low res. This is hardly noticeable with the PSVR2. Sharpness is not quite as good as the QP but the softness means there are very few "jaggy" edges so it does not need any anti-aliasing. I'll feed back in more detail later. I want to try the QP using Steam link and do a performance/quality comparison.

Yes. All of the above. I have followed all the instructions. I'll go through everything again today.

OK. I have the PSVR2 now. My first impressions are that it is not very well made compared to the Quest Pro, Rift S and Pico 4. It feels quite cheap and flimsy. That is not a deal breaker so far. It is actually quite comfortable to wear and has some intuitive adjustments. And it is lightweight. In terms of performance I cannot yet comment. I have spent about an hour and a half trying to get DCS to run in VR. Steam VR is running but it DCS just opens in flat screen mode. I have removed the Meta app. I will post some log files tomorrow. I have had enough for tonight. Time now for brandy!

I haven't compared with Intel but the 9800x3d is a monster. I played with overclocking when I first got it and got some very good results then realised I did not need to when paired with an rtx5080. I might need to when I get a 6090 though

Sorry I missed your reply. If you want a response then ping me by using @Qcumber @Swallow

I'm looking forward to trying this out now. It looks like the halo mount will allow you to remove the face gasket like with the QP. @RealDCSpilot have you tried this?

I switch between using VD and meta link frequently. The main issue I have with VD is that I see the edge of a black border when I moved my head quickly. VD is less glitchy. In terms of quality they are both very similar if you compare like for like. Both are choppy if FPS drops below refresh. Mainly noticeable low to the ground. I will see how I get on with the PSVR2. It sounds pretty good.

So if you set to 120 Hz and DCS runs at 70-90 FPS the image remains smooth? This does not happen with QP and Meta link. If I run below refresh it is very choppy.

The lowest refresh rate of the PSVR2 is 90Hz so capping the frame rate to 72fps will cause stutters. You might be better running at 120Hz and aim for 60fps with re-projection up to 120.

That's pretty much what I see with the QP.

Me too. Sounds promising if you prefer it to the QP. I'll post my thoughts over the weekend.

What are you comparing it to?

I've ordered a PSVR2 from Amazon to see how it looks. It's arriving tomorrow.

Yes. DLAA will also cause blurring of aircraft. Are you using quest link with a cable? Do you have any supersampling enabled of are you running at native resolution?

How does the DLSS ghosting/blurring look with these settings?