TexasGary

Per the changelog this build addresses: Continued navigation update logic improvements Added FACTORY RESET> option in PMDG SETUP> to purge the navdata from within the sim

I just ran DLSS Swapper and noticed there was a new version 310.7.128.0. I tried a couple of flights with it, and the stutter when switching views seems to be a little better. And panning from the cockpit was very smooth. This was with preset M and driver version 610.47.

I just tested the option to start in the cockpit. Works great!! And a quick check of DLSS Swapper shows that my version was reset from 310.7 to 310.6. I assume this is related to the adding DLSS 4.5 support as the default native upscaler. I hopped into a couple of planes, and the text in the cockpit looks very good. So for now I am not going back to 310.7, I am staying with 310.6.

Working here in Texas.

I was finally able to download the SDK via the "Help" dropdown in the Developer Mode menu.

I keep getting error messages whenever I try to download the MSFS 2024 SDK. At the MSFS 2024 intro screen, I enable Developer Mode and then select “Devmode” in the menu. But as soon as I click “SDK Update Available” in the drop down menu I get a “Resource usage exceeds GPU memory” message followed by a "Your graphics device has encountered a problem and the application will exit” message and then the sim crashes to the desktop. I have a 4090 with 24 GB of RAM with the 610.47 driver, and MSFS 2024 runs well with no issues. The only time I see these errors is when I try to download the SDK. I tried downgrading my MSFS 2024 graphic settings, but that didn’t work and I keep getting the errors. Has anyone else ever dealt with this? If you have, how did you fix it? Can the SDK be downloaded outside of MSFS?

I am also loving the Piaggio. I am flying it right now.

Friendly reminder to update your DLSS files after the MSFS update.

I thought Black Square's next plane was going to be a King Air.

Thanks Funky. When I go to 2024 I think I will stick with FS Economy until they fix the bugs.

Thanks bailout and qqwertz. I guess to know for sure I will just have to load up 2024 and see how it goes.

Hey qqwertz, thanks for responding. Appreciate it. But you didn't really answer my questions. I know that some planes cannot be used in career mode. And I know that some 3rd party planes show pax and some don't. Specifically, what I am trying to find out is 1) are you forced to use the default ATC in career mode? and 2) can you show passengers in 2024 planes even if the developer didn't include that option by default? Thanks.

I'm still using 2020, but I am thinking about finally moving over to 2024. Before I did I had a couple of questions: 1. In Career Mode, can you use third party ATC programs (like P2ATC, Beyond ATC, etc.) with it to complete missions? Or is it limited to only using the default ATC? 2. I understand that passengers are visible in Career Mode. But are passengers also visible in Free Flight? I realize some 2024 airplane addons include visible passengers, but does 2024 allow them to be shown in the default planes and 3rd party planes that don't include visible passengers by default? Thanks.

I am still using 2020. In 2024 career mode can you use a third party ATC program like P2ATC or Beyond ATC during missions? Or do you have to use the default ATC?

Just a friendly reminder to update your DLSS file after the update. I forgot, and I couldn't figure out why my speed and altitude tapes were so blurry after the update. Updated my DLSS back to 310.5.3 and now all good.

Looking forward to it.

Search for YouTube videos by Patriot Six. He makes very good, easy to follow videos on MSFS scenery creation and editing.

Just made a flight with 310.5.2. Didn't notice any difference from 310.5.0.

Just suggestions, they work for me and maybe they will work for you. Oh, I forgot to mention that I am using 2020, not 2024.

Turning off Bloom also stops the flashing.

Do you have AMD FidelityFX Sharpening disabled? I read somewhere that setting that to a minimum of 10 fixes the flashing. I had it at 0 and I was having these flashes but after I set it to 10 the flashes went away. As always, YMMV. I also read somewhere that if you set Motion Blur to "Low" that fixes it. I haven't tried that one yet.

Thanks for that precise clarification.

I agree with that. Probably a slight improvement with ghosting from 310.4 to 310.5. And also a slight overall performance improvement.

Ryan, yea that's what I meant (ghosting = numbers blurring when rapidly changing). OK, I owe the community here an apology. When I made my post above about not having any ghosting with DLSS antialiasing set to Quality, I didn't realize that I was actually using DLSS DLAA antialiasing and not DLSS Quality. So I made another flight in the Citation X and I can offer the following more detailed insight: Early in the takeoff run, the numbers are changing so fast in the X that they are blurred using TAA or any of the DLSS modes. While rapidly increasing or decreasing the power levers, the fractional numbers (to the right of the decimal) for N1, N2, and ITT do not blur at all using TAA or DLSS DLAA. There is some very slight blurring with DLSS Quality, and it gets progressively worse with DLSS Performance and Ultra Performance. When descending at 3000 fpm, the altitude "10s" numbers (last two numbers) do not blur at all using TAA or DLSS DLAA. There is some very slight blurring with DLSS Quality, and it gets progressively worse with DLSS Performance and Ultra Performance.

Sorry, I forgot to mention that this was with Preset K.