All Activity

The included Flight Guide is superb, I'm reading it now, while I wait for RL free time to flight test Thanks you so much.

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?

hello. post your dcs.log. if it looks to be a different problem, then i would suggest starting another topic.

OK another day of Testing!!! Watch Prickleys video here: I followed this right through. Working for me, specs below. Rocksteady 72FPS at last.... Aircraft - F16- Apache - F15 - Spitfire- Gazelle Maps Kola - Caucasus - Normandy - Persian Gulf

I've purchased and repurchased many DCS modules, but the mig29A fulcrum prepurchase is taking quite a long time to clear. I purchase through PayPal. Hs this been an issue for this module?

250914A (September, 14th 2025) - Support for UH-60L 2.0 mod added. Support for prior version of the mod deprecated https://www.digitalcombatsimulator.com/en/files/3344152/

Any update on the fix? Becouse the Airboss is non existing (it is useless) for VR users.

That sounds interesting. How many time needs this process?

Quick question: I tried DLSS Swapper today and changing the DLSS runtime for DCS was suspiciously easy. Is there a way to verify it is actually working and using the correct runtime?

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.

Very interesting thread because I have the very same problem since a few DCS updates!

Republic of korea army (JGSDF) remove (JGSDF)

Wait!? ALREADY? How is that possible? Not even TWO WEEKS? Congratulation! I'll test it Today.

Unfortunately, I have no idea. But I’m envious. I measure DCS download times in days, not minutes.

We could do with some Turbulents, water balloons, flour bombs and gates to fly/limbo under too . eta: The smell of fried onions. Mustn’t forget that.

In the last picture overlooking the Merlin we see someone has his head in the cockpit, eyes down. I’m taking that to be Sq Ldr Scoobiedoobs, BriantheBrain, Loki or someone on the team and that they’re busy tinkering and humming happily away to themselves while they work. Holding on to ‘no news is good news’ is sketchy but it’s what I’m going with for now. Trust everyone and everything’s all good. Best regards .

Just installed this app. Aircraft are showing, but not seeing any ground units ?

Anyone can confirm whether it still works in the current version?

Hi all, to my knowledge the only airshow objects mod for DCS was the GrinnelliDesigns Air Show Scenery ( https://www.digitalcombatsimulator.com/en/files/3302379/ ) It appears this mod no longer works in DCS. Is there any talented mod makers out there that would be keen on creating something similar? Or perhaps there's an alternative mod I hadn't heard of before? Certainly can't find anything on the DCS user files

Понятно спасибо!

Thanks, this is fantastic!!!

When there are multiple carriers, they all have the same name (Essex class carrier) on the comms menu, ordered by distance to the player. So, contacting the intended carrier in the group for reporting inbound is a bit problematic. This may be relevant to the problem you're describing.

Yeah, it looks like that's a (weird) error code inside of DCS. Was misleading, that's why I looked at Onedrive first.

В этом на 1:50 показывают.