mazex

Well, it seems like a dev override that is not included in the fingerprinted files it will overwite if changed. As it does not exist in the default install set it should be left alone. Not like us beeing forced down into a Soviet bunker with a cold war Su-27 as menu background every time a new update is released With NVPI we have to change 6 attributes every time a new Nvidia driver is released to get back to preset K. I hope this one will stay as it does not exist in the monitored files, and thus stick ...

Thanks for the advice here! So, after creating the "autoexec.cfg" file in C:\Users\<username>\Saved Games\DCS\Config (did not exist before) with this content: DLSS_Preset = 'K' HUD_MFD_after_DLSS = true It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more Note: I am running Nvidia 576.52 (on an RTX 5080) and DCS 2.9.16.10523. Additional info for VR users: I am using Pimax Play 1.39.4 and the 1.0.16 firmware for my Pimax Crystal Light it that matters. I have the Pimax render quality under the "games" section set to high that does a big difference in clarity (but takes quite som FPS). Worth it for me. I am replying to my own post adding this good description stolen from Reddit where someone does a good job of explaining the different presets with letter codes. What I understand is that the latest version of DCS updates the DLSS dll to 310.2.1.0 It does however use preset C as the default setting (that we can override with the autoexec.cfg that is very nice of the devs). So only J and K use the new transformer model (AKA DLSS 4). The default C is the old CNN preset. I can see a very noticable difference in my Pimax Crystal Light using K instead of the default C preset. The displays and the landscape is MUCH sharper. But I loose around 10 fps. It is worth it for me...

Thanks for the advice here! So, after creating the "autoexec.cfg" file in C:\Users\<username>\Saved Games\DCS\Config (did not exist before) with this content: DLSS_Preset = 'K' HUD_MFD_after_DLSS = true It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more

OK - upgraded to the new Nvidia 576.52 and when starting Pimax Play it wanted to update to 1.39.4. Then after that it wanted to upgrade to 1.0.16 from my shaky 1.0.15. It was a scary firmware upgrade process that failed 6 times requiring USB reconnects and reboots to finally work. But now it actually seems stable. Did a 30 minute F16 mission all stable in DCS. Managed a full 20 minute flight in MSFS 2024 and then a great 40 minute DH-2 cold start combat patrol mission from Amiens in IL2 BoX with three Fokker EIIIs downed. The last with 30 rounds left in the last drum. No problems. WW1 in IL2 BoX with all settings maxed out and high res in the Pimax Crystal Light is actually a pretty awesome experience... Just tried it for the first time in ages to verify it was stable... The scary thing is that you actually aim for the pilots, just like IRL. And with the Crystal clarity it almost feels too real

Agreed. After 1.0.15 firmware I get random freezing in both DCS and MSFS 2024. Tried downgrading the Nvidia driver from .40 to .22 but it continues... So I really need 1.0.14 as it was rock solid before... Their drivers page is hopeless with just the latest version.

I do not understand why I did not do this before... I realized that the switches I like most are the T4, T5 and T6 switches - mapping them to different buttons for different shift modes. The "hooded" T1 switch is rather annoying and toy looking in my opinion. It is also a bit awkward to map (see my config guide that explains some of that). So now I realized that I would try to remove it, as it actually is the same type of switch as T4-T6. Just took a narrow awl on the right side of the pin and tapped gently with a hammer. It easily went out. So now I have another "real" up/down switch that I can map with shift modes. Have not decided yet for different settings so have it for AA/AG in the setup now... And it looks better I think with the three mounting points good for tactile feedback in VR, to know where you are Even though I am not that fond of T2 and T3, they are much easier to reach and use now... I did update my configuration guide for the Virpil Throttle with removing the default mappings for the hooded switch and adding shift mappings for the T1 switch as well - available here: https://forum.dcs.world/topic/207442-my-virpil-configuration-software-guide EDIT: When posting this image I realized that the bright yellow "toy" plastic B9 button has nagged me a bit as well, even though that is just cosmetics. I think some later versions had it in black. So pulled gently up and no problem. Got it loose. Cleaned with some alcohol and sprayed with high quality CRC matte black spray paint. I realized it looks almost exactly as the other buttons. Image of the spray session and final result in the end. Took 10 minutes to do and some drying time... Rood Hood gone: Spraying: Final, also shows the mounts left after the hood. Does not disturb me at all actually:

I updated my guide with a new chapter if you want to remove the red hood on T1 and use it as a regular up/down switch. Really recommend that. A side note. I tried upgrading my Throttle V2 (pre CM) to the 2024-12-26 firmware on my V2 throttle (VPC_Software_Setup_V20241226). Doing that made shift modes stop working. Got that confirmed by Virpil that where very helpful. So after downgrading to 2024-08-14 everything works good (VPC_Software_Setup_V20240814). So if you are on one of the older throttles, avoid the december 2024 version. Link (also update the original post): https://drive.google.com/file/d/1v7Kd3dQHkl6FHm6OCs2o4UauW4DZD-Ks/view?usp=sharing

I just removed the red hood over the T1 switch for my Throttle V2, making it a normal switch like T4, T5 and T6 that I like a lot more. So I updated the original post with an updated template for version 2 and one without the hood that I use myself now.

I am pretty sure that glider pilots would avoid flying while WW3 was rolling? Having said that, I agree that it was a problem in peace time. I have a fond memory from the the late 80-ies where me being 19 flying a glider got a radio message from a slightly older fellow glider pilot I recognized the voice of, checking if it was me flying in straight line over point x. When I responded, an AJ-37 Viggen passed under me, going vertical with full afterburner after he passed... I realized that my friend that also flew gliders was at work that day, in the Viggen This was in the Top Gun era, would not have happened today...

As this is not a sight seeing simulator like MSFS is for many, I think that it is maybe problematic that they have spent time on doing some landmarks and parts of towns like Berlin "too good". This is a military flight simulator of modern conflicts and civilian high-rise apartment buildings, parks with civilians etc. are not supposed to be targets like they where in WWII. Like everyone else does, I naturally did a quick mission starting where I live (even though it will only be included in Phase 3). This is the town where I live now (Lund in southern Sweden). I thought it would just be flat green land now so rather happy that they have done something with low res satellite images. The fact that there is a forest over the low res satellite image of Lund probably shows that they will spend time on "building" that town for Phase 3. They will never beat MSFS where I can see my trees, solar panels correctly placed on my roof etc. I would actually rather have my town as a correctly sized generic Swedish town, and time spent on getting F10 Ängelholm done OK-ish as that was the only AJS-37 base in southern Sweden. And that is just outside the limit for Phase 3. So for that example, less time on the large towns in southern Sweden that will be included in Phase 3 (Malmö, Lund, Helsingborg) and expand to get the only 2 air force bases in Skåne during the cold war included (F5 and F10). Last image is over F10 marked in green. So the only fighter base in Skåne is there with low res satellite at least. The orange line is the phase 3 limit.

Please leave it at CW1 that never happened...

There will be no actual military airfields from the cold war in Sweden and Denmark even in phase 3. Maybe we could get some grass airfield? Viggen is not that sensitive to rough strips, the F-16s in Denmark might have more problems on grass though. Or inklude Skrydstrup (DK) and F10 Ängelholm (SE) by expanding the map a few kilometers... This post was juvenile and off topic. I agree But I agree that it would be nice with some grass strips in Germany. We have the props where we can ignore the post 1940:ies stuff outside the air bases. And interesting that the actually used them for Mig-21s!

I have not noticed the DCS/Ugra product ads in the Syria map but it sounds like a truly awful idea, spending so much good effort on getting the right atmosphere... But I mostly fly jets at higher altitude. I was locked away for 3 hours in Checkpoint Charlie as an 18 year old, drinking my visa away in the spring of 1989 on a school trip to Berlin... It really would kill the immersion seeing an Ugra ad instead of raw grey concrete there, as I plan to revisit it with a rocket armed chopper or an M48 tank in combined arms, to pay back for the lost 3 hours of my life

Wow, this is really looking too good unless there is s big update coming to Combined Arms. And those Aist hoverceafts on that beach look awesome... Did a rather successful scenario in CMO (Baltic Storm) where a bunch of them try to land on the Bornholm supported by Mi-24s, and the Skåne East coast in Sweden... Sadly not included in Phase 3. But almost. Nudge nudge

OK - rather useless but I compiled the different grades from the Supercarrier manual into one PDF to printout for the ones that like it... Or rather for myself, but why not share. https://drive.google.com/file/d/1PWqLAWhGIFJKy0Ydm6-WnpkvzBRt0A6N/view?usp=sharing