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.

I'm certainly willing to try moving the General slider to the Left towards the scenery, but I don't understand the instruction. What/Where is the "General slider"? In the DX10 Fixer program there is the possibility to configure the "General Shader" but I don't see a slider per se' to move left towards the scenery and there is no "general" slider in the FSX settings. Sorry to be so dense, but this newbie needs more detailed direction. thanks! f

Just getting starting with DX10 in FSX using Steve's fixer and trying very hard to follow all of the recommendations for settings. Not surprisingly I've encountered some issues with the add on airport Chicago O'Hare from FS Dreamteam which is not currently DX10 compatible. I'm seeing four black objects surrounding each green taxiway light but don't know what to call this problem and some issues with what I think is called a halo effect around the area lighting. I have attached a screenshot of these two issues which may or may not come through but would like to know two things: For my education, what are these two DX10 anomalies called and is there anything I can do to improve the visuals? Overall I'm very happy I've made the switch to DX10 and can certainly live with the minor problems I've encountered but I'm enjoying the challenge of getting DX10 to work in FSX. Fred Z

I don't know what else to try. My freezes are occurring on pretty much every flight after about an hour of flight. Mostly occur at cruise altitude or on approach. Now they're occurring on both the 737NGX and the T7. It doesn't matter whether I after scenery activated via Scenery Config Mgr or not. It doesn't matter if I have Opus activated, TrackIR or ProATC/X or none of them; still get a freeze that never ends except via Ctrl/Alt/Del. The sound keeps going along with ATC chatter if I have it turned on. I've tried deleting the fsx.cfg file to no avail. I don't see that I have a simconnect.ini file anywhere. I found a log associated with the install of FSUIPC 4.92 that said it couldn't find the "ESP" file whatever that is. But all my addons are working well and the visuals are smooth and the T7 is a joy to fly until it freezes. Like others, the tutorial worked fine the first time but now I can't even get it to complete with no weather. I'm so frustrated! I don't want to have to reinstall FSX from scratch but I've run out of things to try. Any other suggestions or comments? Thanks! Fred Ziker

Thanks to all for your interest and inputs! I have made a couple of changes and haven't had a CTD since: I made the changes described in the thread related to UIAutomationCore.dll, and I applied patch 5 to Orbx PNW. I even flew into the "Bermuda triangle" (KSEA) without incident. As many of you speculated, my issue was more of a software incompatibility rather than a CPU limitation (although more horsepower would probably help!). I now suspect the primary culprit of my FSX pause and CTD issues are related to REX 2.0 trying to perform a weather update at or near TOD or approach which in my case caused more than a loss of FPS or stuttering problem. Thanks again fred ziker

Peter, thanks for your input on my issue and the potential of it being related to Orbx scenery files. I have checked and do not have either of the files you mentioned (cvx_300_FTX_NRM_LCpoly_1712_Edmonton_cutblocks.BGL, cvx_300_FTX_NRM_LCpoly_1613_Jasper_cutblocks.BGL). I currently have PNW and CRM from Orbx. I found a thread related to replacing a UIAutomationCore.dll file in the FSX core and have tried this. I tried the flight again and FSX went into an involuntary pause just before TOD but I was able to press P and continue through landing and shutdown (no CTD). I'll keep playing with this as I suspect everyone is right in that it is not the CPU. fred ziker

Thanks to all for your replies! I've learned a lot already! I didn't know about Ivy and I didn't know what a CTDS was but now I do! Also didn't know about the compatibility issue with FS2 Crew and Orbx but that isn't the cause of my CTD. I was doing a Gulf Coast US shuttle from KIAH to KMSY. I know this sounds bizarre but it most often occurs just before TD on no particular route; sometimes FSX just goes into pause mode and I can continue the flight, then sometimes CTDS. I'm not sure if I can determine whether it's a software incompatibility or my CPU is just out of gas but I think I'll disable one software at a time and fly the route and try to sleuth it out that way. In the meantime, I've started shopping custom PC builders and exploring perhaps building one on my own thanks to you all. f

I'm a novice at all of this but enjoy it thoroughly especially with the new PMDG NGX. I'm not experiencing obvious frame rate issues but I am having FSX freeze up during flight and Windows forcing the program to close down. I have a relatively old CPU (Intel Core 2 2.4 Ghz with 6GB DDR, NVidea 8800GTS, Windows7 64 bit). I'm trying to run the NGX with REX, UT2, FS2 Crew, Radar Contact, Accu-Feel and some Orbx and Extreme scenery. So my questions are: I assume the FSX freeze ups are due to high CPU usage rather than any software compatibility issues? If I need to upgrade my CPU, what would be your recommendations regarding configuration? I'd rather not go the gaming PC route due to the expense, but I DO want to enjoy the best flight simulator experience that I can with a "conventional" CPU that will also be used for email, MS Office and the usual mundane tasks at home. I don't see myself getting into overclocking but would certainly go the i7 route just in case. Any input on the subject would be appreciated! Thanks in advance for you advice!!

Same message about unable to connect but am also receiving another error message that says my activation code is invalid. . Presume my activation code is my license number? (24 character)

I'm having difficulty installing the recommended FPS Limiter. Keep getting the error msg that the hookhelper.dll file is missing from my computer. I've tried to copy that file to my computer but the program still can't find it. The FPS Limiter program readme txt didn't answer the question. Any suggestions?

Thanks very much Soundman! That was exactly what was wrong; somehow I uncheck the Play pilot wavs under the general tabSorry to have taken up y'alls' time but I appeciate the responses.