MSFS2024 Diagnostics Tool – Something I've Been Working On

[EmpireKicking 156]

I've been working on a small utility for Microsoft Flight Simulator 2024 that I thought I'd share with everyone here. It's called MSFS 2024 Diagnostics Tool. The idea behind it is pretty simple, make it easier to gather useful information about your MSFS 2024 installation and system when you're trying to work out what's going wrong.

 

I've been building it myself and have now put it up on Flightsim.to so other MSFS users can give it a try.

 

You can find it here: MSFS2024 Diagnostics Tool - MSFS Add-on - Flightsim.to

 

I'm still working on it, so this isn't necessarily the finished version. I'm interested in seeing what people think and whether there are other diagnostics or useful information that should be included.

 

If you try it, feel free to post your feedback here. If you find a problem, even better, let me know what happened and I'll take a look at it.

 

I'll also use this thread for future updates to the tool, so I'll keep adding to it as development continues.

 

Thanks for checking it out!

[EmpireKicking 156]

Also have done P3d version 😉 So working on both at the same time LOL

V1.8.3 Patch Notes - For P3D

• Fixed P3D version and scenery information not appearing correctly in the Diagnostic Overview.
• Changed storage warnings to use actual free space, with 150 GB and 50 GB thresholds.
• Simplified diagnostic wording with clearer Scan Results and Key Findings.
• Improved diagnostic explanations to distinguish recorded issues from diagnostic leads.
• Removed the unwanted blank line between the Graphics separator and GPU information
• Added yellow CMD-only wait messages during longer DirectX and drive scans. These messages are not written to the diagnostic TXT report.

 

Version 1.2 is out now 😉 Also working in progress Empirekicking

• Added a DirectX "Please wait" message while the check is running (Highlighted in yellow).
• Added broken link detection for Community folders.
• Changed storage warnings to use actual free space, with 150 GB and 50 GB thresholds.
• Removed the unwanted blank line between the Graphics separator and GPU information.
• Improved Windows OS information reporting, including the Windows release version and full OS build number.
• Improved computer model detection and now reports "Not detected" when Windows only provides a generic or unusable model name.

[EmpireKicking 156]

Hello, Update

 

The Diagnostics Tool FAQ page is now up and running: Empirekicking

Both Prepar3D and MSFS 2024 have now been updated.

 

🛠️ V1.8.4 — Prepar3D Patch Notes

• Improved Diagnostic Leads to identify specific areas, including GPU driver incidents, Prepar3D errors, hardware/WHEA incidents, DLL/EXE configuration problems, and inactive add-ons, making it clearer what may have triggered an issue.
• Inactive add-ons now show the inactive item and its configured path.
• Continued investigation into how Visual FX Tool and Traffic Toolbox are detected outside the normal add-on configuration.
• Updated the Final Result section to provide clearer Diagnostic Lead information.
• Added a More Information / Support section with update information and a support link.

✈️ V1.3 — MSFS 2024 Patch Notes

• Added GPU event grouping to reduce repeated Event Log entries.
• Added colour-coded messages during the diagnostic scan.
• Added a More Information / Support section with update information and a support link.
• Thanks to everyone using the tools and providing feedback. More improvements and updates will follow.

Updates can now be downloaded via Empirekicking

[EmpireKicking 156]

I thought I'd share a quick update on the MSFS 2024 Diagnostics Tool, as I've been spending time working on Version 2.

The current version already collects a fair bit of useful information about your PC and MSFS 2024, but I wanted to take things a bit further rather than just make a few small changes and call it an update. One of the main things I'm working on is improving the crash investigation side of the tool. Version 2 is being developed to look at MSFS crash reports, GPU related events and available crash dump files, helping to bring more of that information together in one report. The idea is to make it easier to see what information has been found and whether there are any clues worth looking into when something goes wrong.

I'm also working on making the results easier to understand. At the moment, diagnostic reports are provided as plain text, but Version 2 is moving towards an HTML report that can be opened in a browser. This should make the information easier to read, with clearer sections and explanations of the findings.

 

 

There are also improvements planned for scan status and reporting, so it's clearer when information has been found, when a check couldn't be completed, or when access to a file wasn't available. That distinction matters, as a check that couldn't run shouldn't be mistaken for a check that found nothing.

I've attached a comparison table showing Version 1.4 alongside the features being worked on for Version 2. It gives a better idea of what's already included, what's being improved and what's new.

I'm still working through the development and testing, so "Version 2 isn't ready for release yet", and I don't have a release date to share at this stage. There is still more to check before I'm happy to put it out.

It's worth mentioning that the tool is intended to help gather and present diagnostic information, rather than automatically identify the cause of every crash. The extra information should hopefully make troubleshooting a bit easier, but the findings will still need to be looked at in context.

I'll post another update when there's more to share. In the meantime, the current version remains available, and I'll keep working on getting Version 2 into a state where it's ready for others to try.

Thanks to everyone who's taken an interest in the project!