All Activity

I'm afraid that the campaign won't work in multiplayer, nor will any of the paid campaigns I believe. The issue IIRC is that the trigger commands do not work across clients, unfortunately there is no way around it.

Don't remember did I post R-60 motor rework earlier, same as with R-27ER I was wandering with number of points in star configuration, first with 8 then with 6 but seems it could be awkward number 7 after all. There are lot of photos of this cross cut rocket model on the internet but for this purpose all taken from some stupid angles This is best I found and after some retouchings and after many doubts and questioning, I thing 7 should be. If someone has some better photo from personal archive it would be appreciated. In any case 7-point star will give what is in description of this motor, a bit stronger initial thrust -> This is thrust case for +50, +20 and -50degC at sea level and this is 5km situation which is with nearly perfect match to documents ->

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.

Hello, I really love this campaign and I recommend this campaign to all my friends. However when I try to play with my friend who have bought campaign, I met a problem: I first edit the player F-16cm to a 3 ship group. During the game, only the server host player can hear and see the message from the vacuum/sentinel/..., the client can only hear the ai wingman. I can not figure out why, because these are all sent by the "send message" in the trigger action. Can you possibly give me some idea on how can I fix this? Really appreciate it!

Cheers Silver, I do have 64gb ram cheers. I’m resigned to the fact that DCS is just always gonna crash a few times on me every session. I’ve been mostly flying MP and I’m not alone, most just accept it’s gonna crash. It’s a shame something so good when up and running is so unstable. I rarely have any trouble with any other software on my system, not that much else gets a look in anyway now. cheers for the helpful pointers . - oh and the OH-6, while there may be some issues, is one of the most well put together modules in DCS, albeit a Mod. Tobi & Eightball deserve all the tea & medals for giving us a massive bundle of goodies along with a chopper that’s one of the most fun things to fly on the platform. It has caused issues in the past so if things start to go wonky I disable my mods, as we should, but I’d never be rid of it. What would I do with all these Hawaiian shirts & loafers ?

Long stripes look better to me. Rus skins first maybe.

I'm kinda assuming the MP servers will remove the FC3 version when this arrives

vSFG-7 is a semi-milsim squadron focused on community, education, and having a good time with our favorite aircraft. We run missions and dedicated training sessions to include pilots from all levels of experience. Whether you're a seasoned 1000+ hour master of your chosen airframe, straight out of the tutorial missions, or just want a tight-knit community to hang out and fly with, we have a little bit for everybody. We offer private 1 on 1 training sessions with exclusive, in-depth training material, complete with a tracker to make sure you learn everything there is to know about your chosen aircraft. As well as squadron-wide operations to put your knowledge to the test in high stakes, large scale missions. vSFG-7 runs dedicated, high performance privately owned servers to offer the best possible experience and performance for squadron-wide operations and training. Currently there are 3 squadrons open for application: F/A-18C - VFA-154 "Black Knights" - Tuesdays and Thursdays @ 2000 EST F/A-18C - VMFA-225 "Vikings" - Tuesdays and Thursdays @ 2100 EST F-16C - 421st Fighter Squadron "Black Widows" - Tuesdays and Thursdays @ 2000 EST We have Wing Wide Missions once a month Join Now! https://discord.gg/3WFBm93QQG

I don't have combined arms. I'm just talking from a mission editor perspective.

I think this happened after a certain update. My system is an R7 7700 CPU, 64GB DDR5, and an NVMe 2TB M.2 SSD. This seems to be caused by ED's repeated pursuit of high-quality maps in updates. How can I fix this?

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? 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.

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 FORGOT TO include PP sharpen to 0.8!!!!! Try Pimax Play Launch worked well Also QVC repaired then launched with PP in background, then Launch DCS direct. I am still however Setting the DCS priority to HIGH in tack manager, regards.

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.