On 1/30/2022 at 10:39 PM, 109Sqn said:

he Ugly: At time, the flight is freezing

 

Which is acwell known issue in FS2020, plus crashes. They are working on it. So might not be your hardware.

Test other games not just the sim

On 1/30/2022 at 9:49 PM, 109Sqn said:

Replicated the above Flight Plan and completed the flight with no errors. but my next flight from Prestwick to Glasgow froze and CTDed during taxi after landing.

And there is is at the end: "Display driver amdkmdap stopped responding and has successfully recovered." There's a discussion at AMD Community I will have to read through to see if it's of any help.

 

 

Ugh .. you have a 5700xt ... I dont know what it is with these cards but the 5700xt's have a rep to cause CTD's in MSFS. One potential solution is to go to the radeon software and adjust the power slider to the max in the custom overclocking slider (If it is available)

On 2/1/2022 at 8:41 AM, martin-w said:

 

Which is acwell known issue in FS2020, plus crashes. They are working on it. So might not be your hardware.

Test other games not just the sim

As posted previously, I have tried other games, most notably Forza Horizon and Motorsport, without issues.

5 hours ago, Maxis said:

Ugh .. you have a 5700xt ... I dont know what it is with these cards but the 5700xt's have a rep to cause CTD's in MSFS. One potential solution is to go to the radeon software and adjust the power slider to the max in the custom overclocking slider (If it is available)

And this is what's so frustrating about MSFS - when I first looked at upgrading to the 5700XT, I got people here saying it was a good choice (and for the money, it was). I'm not blaming anyone for what they said though, because nobody knows in advance how a new program like MSFS is going to behave with any given piece of hardware.

A new wrinkle: As mentioned previously, I'm struggling to install the current AMD Adreniline driver as the installer says I am missing a Visual C++ file (vc_runtimeMinimum_x64.msi). Try as I might, I have been unable to fix that by downloading VC++ installers from Microsoft. I've tried individual releases and the full package installer - no joy. 

However, I decided to try installing the Adrenaline drivers on the clean Win10 install I experimented with on an empty drive and all went to plan. I'm seriously thinking that I've nothing to lose (other than my time) in firstly a) upgrading my original OS to Win 11* to see if the Visual C++ files get installed during or after that process, or b) just wiping Win10 from the original drive altogether and starting from scratch. (I don't really want to use the second OS install long-term as it's on an unnecessarily large drive and I always like to keep the OS drive as clean as possible).

There's no guarantee that it would fix any of my problems, but surely one or other of the Windows 'fixes' above would give me a shot of at least getting the GPU driver updated and maybe address some or all of the other issues. And if I get the GPU driver updated, I have the option of trying the OC slider to the right.

 

(* Bearing in mind that as I have an Alder Lake CPU, I really should try Win11 sooner or later anyway).

18 hours ago, 109Sqn said:

I'm seriously thinking that I've nothing to lose (other than my time) in firstly a) upgrading my original OS to Win 11* to see if the Visual C++ files get installed during or after that process

Well, tried that - easy upgrade, no problems. but when I went to install the Radeon Adrenilin driver I was back to the missing vc_runtimeMinimum_x64.msi file. I even tried pointing to the one on my Win10 clean install drive but it wouldn't accept that. And I had  run Windows Update until there were none available. So, upgrading to Win11 from Win10 doesn't add any missing Visual C++ files by the look of things.🙄

So I'm currently planning on making sure I have all my installation files saved in one place before uninstalling every program (including MSFS), wiping the original Win10 drive (which I'd upgraded to Win11) and doing a clean Win11 install before hopefully finding I can actually install the latest Adrenilin driver and then putting all the programs back, starting with MSFS to make sure that runs properly before anything else is re-added. And I'll probably just run the 3200MHz RAM unless the 3600 miraculously runs stably.

If all that fails, I might try cloning the clean Win10 install onto the original Win10 drive.

 

The original XMP and microstutter issue seems like a distant memory (pardon the pun).🙄

A little update:

Clean install of Win11 (with keyboard/mouse receiver the only USB device -other than the Win11 media stick - plugged in) completed. Essential drivers installed. GPU driver updated from default to Windows own driver for the 5700XT (I want to see how things go without trying the Adrenalin driver first). After discovering sometimes you need to rename (or delete where possible) existing folders with the same name before you can tell Windows to move or change things like save locations, I selected my G drive as my desired location for MSFS (and Forza etc) and I'm currently 1h (and 12%) into reinstalling the sim. My account was recognised so I'm hopeful nothing has been lost - I'm certainly getting the full Deluxe package, all 114GB. Here's hoping my settings (particularly control profiles and logbook etc) have been restored from the cloud.🤞

Once installed, the next step will be to run with an empty Community folder, gradually increasing settings to see if things remain stable. I'm prepared to take my time on this stage. I decided to attach all my controllers (one at a time) and install their drivers after the initial Xbox download and before launching MSFS so that they are all in place when MSFS is ready to fly so to speak.

Other than that, Win11 is running vanilla with only Advanced Uninstaller Pro installed as it's my preferred installation manager. Everything else can go on bit by bit if MSFS behaves.

 

Watch this space...🕰️

2Hr, 25%...

And that's the basic installation just finished after 8 hours.😴

Now for all the World Updates...

Edited February 7, 20224 yr by 109Sqn

24.61GB of WU and other previously installed add-ons (including the Ju-52) still downloading. Just over 20% complete after 50min. Took a quick test flight in the C172 around Mount Panorama, Bathurst, Australia and all was well except for No rudder control (but there is a driver update pending so that's probably the reason) and the odd fact that FPS was fine until I loaded Game Bar to check the frame rates when it became a stuttering display.😵 But I am hoping that's just down to the PC not being fully settled, with a restart being needed for some updates which were downloading during the MSFS install.

 

More when everything is updated in a few hours...

State of play:

Things are smoother so far, overall. I'm leaving XMP alone at the moment and still experimenting with the 3200MHz RAM for the time being. I have had one TD unfortunately:

Quote

22:45:04 Event 4101, Display

Display driver amdwddmg stopped responding and has successfully recovered.

---------------------

22:45:05 Event 1000, Application Error

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b250aa
Faulting process ID: 0x2d4c
Faulting application start time: 0x01d81c725d28a14a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: cfbd7d6c-f806-4f53-b02b-63fca07b8a30
Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

-----------------------

So there is still a driver issue by the looks of things. This is with Windows' driver for the 5700XT, rather than either the most basic default driver or  installing Adrenalin (i.e. I selected "update Driver" in Device Manager and allowed Windows to search for its own driver for that GPU). I'm inclined to test further to see if I continue to get CTDs before installing Adrenalin for the first time on this Win11 installation. I'm still running Vanilla MSFS (empty Community folder). At least I now have MSFS where I want it - on an NVMe drive rather than HDD where Game Pass had originally put it back at the beginning.

There is still this issue though:

On 2/7/2022 at 7:27 AM, 109Sqn said:

FPS was fine until I loaded Game Bar to check the frame rates when it became a stuttering display

No idea what's causing that.

 

Anyway, I left the sim running overnight, flying the Asobo Porter across Australia (AI pilot, unlimited fuel) and it completed the (16 hour) flight without issue, apart from the usual AI Pilot behaviour of a) flying beside the flightpath rather than on it and b) lining up perfectly with the runway before circling a few seconds before touchdown and ditching in the sea!🙄

Edited February 8, 20224 yr by 109Sqn

Just completed what was one of the best-behaved flights I can remember!😊 But it did leave me a little confused.    😕

I flew from NY La Guardia to Toronto Pearson Int in the 747. For the first time in many months, a plane actually followed the flight route on AP, albeit slightly to the left of the runway on final approach, leading me to cancel AP earlier than planned. I haven't flown the 747, or any tubeliner, in months so I forgot to set Auto Throttle and Flight Director till I was over Lake Ontario, but no matter!😁

My route took me circling over NYC to max out the stress on the GPU. Frame rates were 34-45fps throughout the flight (FPS capped at 30 in-sim), only dipping to 28-30 in external view if I looked directly down over Manhattan Island, and briefly 18-20 as I taxied in Toronto. No stuttering whatsoever. Live time & weather, it was dusk (around 16:00) when I departed and around 17:30 when I landed in snow-covered Toronto. Real-time online traffic, with generic models off and variety on ultra. I'm still using overall High settings for now before going back to trying mostly Ultra as I had before the hardware changes.

Finally for this progress update, I tried Game Bar Performance display again to monitor FPS, and this time it had no notable affect on frame rates. Go figure!🙄

Still plenty testing to do, but things are so far better than they had been.👍

(Cue the next CTD...😬 )

Glad you are finally sorting it out. I have the sim installed now, and yes, its not exactly stable. Randomly shuts down and smoothly returns me to the desktop. 😁

I wouldn't exactly call it well optimised. 🙄

I take it you aren't using XMP. But have you tried the other Asus memory presets in the Bios, the Asus version of XMP in a way? If your Tuf board has it.

 

2 hours ago, martin-w said:

I take it you aren't using XMP. But have you tried the other Asus memory presets in the Bios, the Asus version of XMP in a way? If your Tuf board has it.

Nope, still using the default setting in the BIOS but I'll give XMP a shot if I feel that CTDs are going to be much rarer in future when not using it first of all.

I haven't discovered non-XMP presets, but there are so many menus and sub-menus that I may just have missed them. I've never been one to over or underclock and I think my previous PC build before this one was the first to even have XMP as an option.

I share your frustration - if it weren't for FPS/stuttering and CTDs, I could live with most of MSFS's issues. Since I seem to have fixed the stuttering and possibly the FPS issues, I'm hoping it's a case of two down, one to go. Only that one CTD since installing a fresh Win11 and re-installing the sim, so 🤞 I'm making progress. I will re-seat the GPU before I boot up the next time, just to rule out any problem there.

2 hours ago, 109Sqn said:

I've never been one to over or underclock and I think my previous PC build before this one was the first to even have XMP as an option.

 

XMP has been around for a long time. The only issue by not enabling XMP, apart from the loss in performance, is that you will have spent money for faster ram without getting your money's worth if you just run at the JEDEC frequency.

I agree with your strategy to test for a while before opting for XMP.

Come to think of it, I don't think you do have AEMP (Asus Enhanced Memory Profile) because your board is DDR4. I recall AEMP is DDR5 boards. 

 

 

 

Edited February 9, 20224 yr by martin-w

Been a while since I posted an update. I've been testing on and off since the last one, still with the 3200MHz RAM at default speed and the new vanilla install of MSFS "Ultra Deluxe Super-Duper".

Two problems currently:

1) Anything with an overlay on top of the sim results in stutters and lower FPS - that's Game Bar or any monitoring software such as NZXT CAM.

2) Even without the above, I am getting complete PC shutdowns after running the sim for 20 minutes or more (frustratingly often when I'm a minute or two from touchdown🥵), with the PC feeling pretty hot immediately after. And yet I see nothing in the crash logs which suggest overheating. Likewise, although I can't really be looking at the temp monitors whilst flying (especially because of 1 above), I don't see anything particularly extreme temp-wise.

Not long after I originally installed MSFS, I set the rear fan - the only monitored one other than CPU & GPU - to run at full speed when the sim is running, so short of adding extractors in the top of the case, I'm pulling as much hot air out of the case as I can. It's natural to suspect the PSU, so I've been trying to fore a shutdown when the sim isn't running... 

I've been running OCCT and WhoCrashed but none of the tests (run for the maximum 1 hour that the free version allows) has resulted in any problems (let alone a shutdown), and the latter hasn't found a single crash log after any of the tests. I've only run each test once so far.

I'm going to run a flight with WhoCrashed running, to see if it finds something I'm overlooking, assuming the PC manages to record the problem before the power goes off. The screen does go black for a second or two before the shutdown, so fingers crossed that's time for a log to be created.