Gogolathome

I am planning my route in LNM then export it as .gpx file and load it into Windy. This is great as I fly in different regions wit Onair and have to use historical weather sometimes.

I have best results with gsync compatible monitor (3440x1440) @100hz and in game limiter set @40 fps and DLAA antialiasing with preset F (any other preset gives worse ghosting). TAA is bit more sharper but with more shimmering which I don't like. My videocard is 4090 an CPU is 13900KS.

I have read about SU3 that files are downloadable again. Will this offer the same extraction of info from the Sim like in 2020 version, so without simconnect?

It works better with native MSF2024 aircraft G1000. With the MSFS2024 DA62 I didn't have this problem. Did you use a non-native aircraft? Problems arise also with user waypoints that are not recognized on non-native G1000 in my experience. I think we have to wait...

First set departure and arrival and then from EFB load your flight plan and send it to avionics. That works for me.

I asked Google Gemini: Why do so many users have problems with the new nvidia driver and dlss4? It appears there are indeed quite a few users experiencing issues with the new Nvidia driver and DLSS 4, particularly within the Microsoft Flight Simulator community. Here's a breakdown of the potential reasons, drawing from the information available: 1. Inconsistent Implementation and Compatibility Issues: MSFS 2020 vs. MSFS 2024: One of the most prominent issues seems to be the difference in how DLSS 4 is implemented in the older MSFS 2020 compared to the newer MSFS 2024. Some users report smooth experiences in 2020, while many encounter problems in 2024, with options being greyed out or unavailable. Nvidia App Inconsistencies: There are reports of the Nvidia app showing games as "unsupported" for DLSS features, even when those games are officially listed as supporting them. This suggests potential bugs or inconsistencies in the app's detection and handling of DLSS 4. 2. Complexity and User Confusion: Manual Overrides and Workarounds: The current situation seems to require users to resort to manual methods like using DLSS Swapper or Nvidia Profile Inspector to enable and configure DLSS 4 features. This level of technical know-how is not expected by the average user and can lead to confusion and frustration. Lack of Clear Guidance: There seems to be a lack of clear and concise instructions from Nvidia and Asobo (the developers of MSFS) on how to properly utilize DLSS 4 in the simulators. This makes it difficult for users to troubleshoot issues or understand the intended workflow. 3. Potential Bugs and Driver Issues: Early Release Challenges: It's not uncommon for new drivers and technologies to have teething issues, especially in complex scenarios like flight simulators. There might be bugs in the driver itself or in the interaction between the driver, DLSS 4, and the games. Optimization for Different Hardware: DLSS 4, with its new Multi Frame Generation feature, might be optimized primarily for the latest RTX 50-series cards. Users with older GPUs might experience varying levels of performance or encounter issues due to compatibility differences. 4. Communication Gaps: Lack of Clarity from Nvidia and Asobo: The two companies need to provide clearer communication about compatibility, known issues, and recommended solutions. This would help manage user expectations and reduce frustration. Overall: The issues seem to stem from a combination of factors, including complex technology, potential bugs, inconsistent implementation, and a lack of clear communication. It's crucial for Nvidia and Asobo to address these issues promptly to ensure a smoother experience for users and to fully realize the potential of DLSS 4 in flight simulation. If you're experiencing problems: Stay updated: Keep your drivers, Nvidia app, and games updated to the latest versions. Check official forums: Look for information and solutions on the official Nvidia and MSFS forums. Engage with the community: Share your experiences and learn from others on platforms like Reddit or AVSIM. Be patient: Hopefully, these issues will be resolved with future updates and patches.

Thank you @Ianrivaldosmith, your opening post has very clear instructions! Everything is working fine on my system.

I will add a little more to the confusion. I am using a 4090 with native (real) gsync monitors and DLSS+DLAA with driver 566.36 and new DLSS4 dll's. I have the best quality and super smooth still with preset F and not with J. The last preset is giving me a blurrier G1000.

Did you install the specialized MSFS 2024 version of the G1000 bridge?

I remember from the past that I had problems with FSUIPC in combination with other software (could be AAO). So I avoid using FSUIPC related connections to MSFS.

After 24H2 update I once had a flight with audio stuttering. It was gone the next flight. One thing I noticed that my CPU(13900KS) was at 75%. I think it has to do with CPU throttling, but that is just a thought.

You can change that to not change the settings😉. You will be that person!

As the title says version 4.50b32 for MSFS2020 and MSFS2024 crashes when I switch to offline mode and try to load a template, not when I load a configuration. Thank you in advance for solving this😉. Jos

Both statements are true, however first I thought that the plugin wasn't working with the new version but I had to change the webAPI port to make it working😉

I decided to install the game a few hours ago and keep the 2020 version. I was flying around 15 minutes later!