imperialMedium's rigidBody crashes the main menu without error when ship is inserted in menuBackgroundShipConfig.json

Inizia riproducendo il crash al commit 52b23c412b6f84753d855f51e81a785753a98a52 con core/assets/configs/menuBackgroundShipConfig.json e i file JSON delle navi imperialSmall e imperialMedium. Confronta i relativi dati di collisione di rigidBody ed esegui il gioco su Windows. Il lavoro è completato quando le navi dello sfondo del menu vengono caricate senza che il gioco si blocchi o si chiuda silenziosamente, incluse imperialMedium e le navi che condividono la sua mesh di collisione.

What you were trying to do

Add the imperialMedium ship from the core module into the game's menu background, e.g.

DestinationSol\modules\core\assets\configs\menuBackgroundShipConfig.json or DestinationSol\modules\custommodule\overrides\core\configs\menuBackgroundShipConfig.json

{ "Menu Ships": [ "core:imperialMedium", "core:imperialSmall" ] }

What actually happened

Depending on which ship(s) it loads first and if there are other ship entries in menuBackgroundShipConfig.json, it may not crash immediately, but when it attempts to load in the imperialMedium ship, or a ship that shares the same collision mesh, the game freezes momentarily before closing, without an error message.

How to reproduce

Step 1: Replace the contents of core\assets\configs\menuBackgroundShipConfig.json with the following contents:

{ "Menu Ships": [ "core:imperialSmall" ] }

(imperialSmall is exclusively an example)

Step 2: Replace the corresponding rigidBody field in core\assets\ships\imperialSmall\imperialSmall.json with the following data, taken from the imperialMedium's rigidBody:
"rigidBody": { "origin": { "x": 0.5303030014038086, "y": 0.3068181574344635 }, "polygons": [ [ { "x": 0.20500002801418304, "y": 0.1312500387430191 }, { "x": 0.5600000619888306, "y": 0.1287500411272049 }, { "x": 0.892500102519989, "y": 0.4037500023841858 }, { "x": 0.33000001311302185, "y": 0.9237499833106995 }, { "x": 0.20250003039836884, "y": 0.918749988079071 } ] ], "circles": [ { "cx": 0.7400000691413879, "cy": 0.4412499964237213, "r": 0.18447551131248474 } ], "shapes": [ { "type": "CIRCLE", "vertices": [ { "x": 0.7400000691413879, "y": 0.4412499964237213 }, { "x": 0.9049999713897705, "y": 0.35875001549720764 } ] }, { "type": "POLYGON", "vertices": [ { "x": 0.20500002801418304, "y": 0.1312500387430191 }, { "x": 0.5600000619888306, "y": 0.1287500411272049 }, { "x": 0.892500102519989, "y": 0.4037500023841858 }, { "x": 0.33000001311302185, "y": 0.9237499833106995 }, { "x": 0.20250003039836884, "y": 0.918749988079071 } ] } ] },

Step 3: Run the game

Game version

Commit 52b23c412b6f84753d855f51e81a785753a98a52

Log details

No log was produced.

Operating System

Windows

Additional Info

I have not tested other collision meshes, so there is the possibility more ships within the core module may be affected by this bug.