Thumbnail Capture Tool Crashes to Desktop in MSFS 2024 (Blocker for Marketplace Submission)

Version: SU/16 - 1.39.9

Frequency: Consistently

Severity: Blocker

Context: *bfg-aca-scout - In both MSFS 2020 and MSFS 2024, the built-in thumbnail capture tool does not function as expected in my environment. The issue is especially severe in MSFS 2024, where attempting to load the capture tool results in an instant crash to desktop (CTD) every single time.

This is a blocker for publishing my new American Champion Scout aircraft to the Marketplace, as I am unable to generate required thumbnail images directly in-sim using the official capture tool.*

Bug description: Also I have reverted back to 6 months ago graphics driver when it was last known working for my ATEA release(I only had a few liveries) This time I have 25 liveries and 3 variants which means 75 captures needed total. I 've tried in 2020 DX12 and 11. Tried settings on low and high and everything in between with no luck in either simulator. A month ago I was lucky enough to get 1 variant almost complete, but then it started crashing again. So now I only have a few of the remaining two variants complete.

Repro steps:

  1. Launch MSFS 2024 (also tested in MSFS 2020 (Hangar)for comparison).
  2. Load any aircraft (including the new Scout) at any location.
  3. Open the Developer ModeAircraft EditorThumbnail Capture Tool.
  4. In MSFS 2024: the simulator instantly CTDs upon the capture tool loading.
  5. In MSFS 2020: tool launches but still does not function as expected for current aircraft builds. In fact it holds an odd camera edit angle once activated. Also doesn’t produce the image as previously saved

Attachments: This is the only zoom/rotation/movement it will allow a picture to be taken in 2020 and its unacceptable. It won’t allow me to edit the camera view.

In 2024 ported this is what I want them all to look like or something similar

Hello @B4Gunner

Have a look at this existing bug report: MSFS2024 SU3 Beta crashing when thumbnails are created - [MSFS 2024] Bug Reports / SDK: Tools/Samples/Documentation - MSFS DevSupport

Make sure you don’t have AMD Frame generation enabled if you have an Nvidia GPU.

If this is not the cause in your case, please follow section 2 and 3 from these guidelines and provide us with a dump file we can analyze.

Regards,
Sylvain

@FlyingRaccoon, Thank You for the timely response

Doing it in SU3 Beta fixed the issue, but now I can see where the issue was. In current build SU2 this log did not show up and then it would just CTD. Hopefully this helps someone else. In the future maybe make it so that if the plane is above/below ground just a tad bit on spawn(static_pitch/static_cg_height) and it needs dropped/lifted could very well be causing the issue currently. This has worked with all 9 variants and 25 liveries each. Thank You.

Nick

  • Hangar Studios 713

One of many final screenshots

Hello @B4Gunner Are you certain this is what caused the crash?

I cannot replicate it in SU2, when setting up my plane so that these errors show up.
I’ll mark this topic as obsolete and we’ll reopen it if it keeps happening.

Regards,
Sylvain

@FlyingRaccoon I’m almost certain this is what was causing the issue, but I only received this error to work in SU3 Beta. SU2 it would just crash immediately and no error log. I mean I could run it in SU2 and get the error log for you if you want with the REI. But I’m just happy SU3 Beta has somewhat fixed it, but still showing the error I displayed above.

Nick

1 Like

Yes, if you can provide me with an RAI archive, I can confirm the cause of the CTD and make sure this has been deliberately fixed in SU3.

Regards,
Sylvain

@B4Gunner You are right. :wink:

There was an issue when accessing the SimObject name in an unprotected way, that could trigger a crash when printing that log message.
This was fixed in Sim Update 3.

Regards,
Sylvain

1 Like

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.