fzike

They're doing an update to the update right now per the installer message

I recommend creating a support ticket via the PMDG operations center. They are quite interested in hearing about WASM crashes with their aircraft and what you were doing at the time of the crash.

I encountered the same problem and set the 4X Frame Gen in the Nvidia App and left the sim setting alone. Just a suggestion f

FWIW : How to - Clear the WASM folder? - FAQs - iniBuilds Forum

Disclaimer, I am no expert on the subject but I recently upgraded from a 3080Ti to a 5080. I did remove the dlssg_to_fsr3_amd_is_better.dll and the version.dll files from my MS2024 Content folder since I now have native DLSS and frame generation. I have my 2024 sim settings Anti-alising = Nvidia DLSS Super Resolution, Resolution = Quality, Frame Generaton = NFIDIA DLSS, Framerate Multiplier = 2X. I cleared my shader caches per Island Sim Pilot's March 19, 2025 video on YouTube (ignore the Profile Inspector portion of the video). Finally, in the Nvidia App I set the DLSS Override-Frame Generation to 4X to take advantage of the 50 series capabilities. It's a trial and error type of exercise to take advantage of your new acquisition. I tried setting framegen to 4X inside the sim and that did not work at all well. Good luck!

I've also just acquired a 5080 and experienced similar freezes when I attempted to set the frame gen multiplier in MS 2024 to anything higher than the default of 2X (HAGS turned on FrameGen enabled, etc.) regardless of whether I turned down the other settings as many have suggested. I was able to get the benefits of DLSS and the 50 series cards by setting the frame gen to 4X in the Nvidia App/Graphics/Program Settings and letting the Nvidia app optimize the flight simulator settings and then manually adjust some values in the sim itself. I'm using the latest 576.40 driver. I find I still have to use Auto_FPS and the demanding third party airports but I'm still tweaking my TLOD and OLOD settings.

Thanks for informing us of the update! Much appreciated! f

I just updated my card with another Nvidia card (3080Ti to 5080) and I would recommend uninstalling the current driver before installing the new card. Delete the shaders and rolling cache and DX12 in diskcleanup. Then do a clean driver install direct from Nvidia.com download rather than Nvidia Experience. I wrongly assumed that just installing the new card would pick up the previously installed driver but that was not the case for me Fred Ziker

Back again today! Just finished a short flight but had six plus disconnect/connects. Based in Texas FWIW Very frustrating! Has Asobo acknowledged their server problems yet? f

Is there a comparable way to trigger time compression off/on in the 777-300 as the right click on CHR in the 777-200? This would be preferred to me versus going to the menu in the FMC. Sorry if this has been covered but I couldn't find the answer in the documentation. thanks fred ziker

There are folks out there far more knowledgeable than me but here's my experience moving PROATC off my desktop onto a laptop ( I haven't moved ASN and don't use FS Commander). First, I'd recommend upgrading the laptop to Windows 10 and get that completed before moving programs over. Go to the Pointsoft website and download the simconnect.msi file onto your laptop in the Documents folder: http://pointsoftware.de/proatcx_e/download.html . You'll need to configure the simconnect file with your desktop IP address. With PATC you're only allowed to have an active program on one computer at a time. So you can either copy all of your PATC files over to the laptop or create a fresh load of the program on your laptop your choice. When you open PATC on the laptop for the first time you'll have to register the product with your key and all that just like you would if you had just purchased it. You'll have to define the paths to all the FSX folders, weather, etc. on your desktop to access them via the network (Once you've registered PATC on your laptop you won't be able to use it on your desktop without re-registering). Things to expect when networking this program: The sound of PATC will come out of your laptop, the popup screen (when you press 1 on your desktop PC) will show up on your FSX screen just like it does now. I find no delay in response when interfacing with PATC in a networked config except the PATC moving map has some understandable delays in picking up the current position. If you desktop IP address changes (they do from time to time even if 'fixed') You'll have to edit the simconnect. msi file in the laptop as well as the simconnect.xml file on your desktop. If this is your first time using a laptop via simconnect there are two files to install on the desktop and the .msi on the laptop. Just search on the forum for that topic. hope this helps fred

The gift that keeps on giving! Many thanks for the tip on the "TODO" folder! That was the final key to enabling me to successfully upgrade from Windows 7 to Windows 10. fred ziker

+1 about being too bad that UT2 has been abandoned by the developer.

I experienced the same rejection and alert from Norton Internet Security. I simply configured Norton to exclude this program from its future scans and auto protect. I've also done this with most of my FSX files from vendors with whom I've had a lot of experience with and FS2Crew is certainly one of those. No worries fred

Thanks for your patience, Paul! Moving the legacy shader in Steve's DX10 Fixer left towards the scenery has definitely improved my runway lighting issue.