[Genhis] [1.1.45] Crash when visiting locomotive page in prototype explorer

[Xorimuth]

To reproduce:

- Open prototype explorer
- Search for "Locomotive"
- Click on "entity"
- Open the Locomotive page

OR

- Hover over locomotive
- Press prototype GUI button

This causes a crash which isn't reported in the log, but instead opens a macOS crash window with some other info (copied into macos-crash-report.txt attached). Happens on both 12.0.1 and 12.1 beta 1.

[Rseding91]

Thanks for the report. I tried to reproduce the crash but it seems to work fine for me. Can you try verifying the steam files and see if it finds anything wrong?

If you restart your computer does it still happen?

[Xorimuth]

Thanks for the report. I tried to reproduce the crash but it seems to work fine for me. Can you try verifying the steam files and see if it finds anything wrong?

If you restart your computer does it still happen?

Verifying steam files and restarting still doesn't help. I tried with my non-steam installation (1.1.39) and the same crash happened, so I expect it is a problem on my computer still. Note that it doesn't crash for the other prototype pages I tried (cargo wagon, straight rail).

I feel like I remember reading about someone having similar problems with the prototype explorer crashing several months ago... I don't remember if it was resolved. (Edit: viewtopic.php?f=11&t=98736).

[Therenas]

Can confirm, crashes for me too, macos log attached.

[oof2win2]

Here is my stack trace. Air 2020, Intel.

[Genhis]

Thanks, your crash reports were very helpful. The issue should be fixed for the next release.

[Xorimuth]

Thanks, your crash reports were very helpful. The issue should be fixed for the next release.

Nice! Was it not a macOS bug then? From the discussions on discord it seemed like it was.

[Genhis]

The issue was affecting all systems but only Mac OS crashed: "create-trivial-smoke" trigger objects were accidentally static-casted into "create-entity" when shown in the prototype explorer. I, personally, don't have Mac but was able to find the issue from your logs.