TexasGary

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.

Just completed a flight with Nvidia 591.74 , DLSS 310.5, DX 12, Frame Gen, and DLSS antialiasing set to Quality. I have a 4090, and in the FlightFX Citation X I had great performance. The Primus 2000 screens were all clear and sharp, and I didn't notice any ghosting at all.

I just ran DLSS Swapper and noticed there is a new version 310.5. Nvidia also just released a new driver 591.74. Anyone tried these yet? About to start a flight with the new driver and DLSS version and will report back.

I really miss the PMDG J41. At FSExpo last year in Providence I asked RSR if there was any chance they would ever bring back the J41. He said that it wasn't a zero percent chance, but the chance of it being resurrected is pretty low.

At FSExpo this year I asked RSR if there was any chance they would ever bring back the J41. He said that it wasn't a zero percent chance, but the chance of it being resurrected is pretty low.

Went to make a flight in 2020 and I noticed that the aircraft registration number was not showing on the tail or the panel. I turned Online Functionality off then back on and the registration numbers are now showing again.

Thanks Dave. I am still using Version 2, are you are going to update both Versions 2 and 3?

For the last 2 days every time I highlight an airport and hit the Wx button it just says "Not Available." I also tried using the "Sim Weather" option instead of the "NOAA Real Weather" option, but it still just says "Not Available." This happens on both Versions 2 and 3. Has NOAA changed some of their processes again? Whenever I access https://aviationweather.gov/adds/dataserver_current/current/metars.cache.xml it says the service is unavailable.

FlightFX didn't preview their Citation X before it was released. And it has turned out to be a fantastic aircraft.

I just did a flight in 2020 with 310.4.0 using DLSS/DLAA and the 577.00 driver. The image quality appeared to be a little better, but I didn't really notice too much of a difference from 310.3.0. My overall impression is it appears to be a pretty good DLSS update.