Pertam/Alien Crash zones

It's been a while since I last raised this issue, and since returning to the game for the latest patch I've noticed my previous reproduction no longer reliably triggers the crash as it once did. The crashes on Pertam/Alien planets still happen as frequently as before, but appear to be in slightly different places now.

While creating another scenario to reproduce the issue, I noticed a few unusual traits that cause or prevent the crash. Hopefully this additional information might help the development team resolve these issues, letting PS5 users finally enjoy Pertam and the Alien planets.

I've found a new location which demonstrates the crash. I might have also stumbled onto the precise voxel that may be the underlying cause of these types of crashes on PS5. I'd located an area that causes the crash when travelled through, but noticed that the crash only occurs when travelling in a certain direction. Once, I was able to enter the zone (from an angle that typically crashes the game) without crashing, where I found what appears to be a voxel that hadn't loaded properly. I made a save at this point, with the player character hovering above the erroneous voxel.

This save is available here: https://mod.io/g/spaceengineers/m/pertam-crash-repro#description

The image for the save on mod.io shows the missing voxel, but when you load the save, it's usually back in place correctly. I spent a few hours playing about with this crash zone, and only entered this state with visibly missing voxel (without crashing) once. This unusual voxel appears to be in the middle of the area which causes the game to crash.

To recreate this crash, load the save and travel to the "QA Launchpad" coordinates around 400m away. From there, turn around and fly back to the "Hole in world?" coordinates.This will cause the game to crash, and can be reliably triggered from this approach, which we'll call the crash vector. Approaching the "Hole in world?" coordinates from other directions doesn't appear to cause the crash. Approaching at different speeds appears to affect how close you can get to the marker before the crash happens.

The crash appears is tied the the location and direction of the camera tied to the player character.

When playing first person and flying along the crash vector, the crash is unavoidable. If you switch to third person, with the camera as zoomed out as possible, you're able to travel along the crash vector without crashing. Presumably, once you're travelling at enough speed, the game will crash even if fully zoomed out. Additionally, if you fly along the crash vector using the spectator camera, leaving the player character at least 400m away, the game doesn't crash at all.

If you travel the crash vector, but facing backwards - the game doesn't crash. Likewise, if you travel the reverse of the crash vector while facing backwards, the game will crash very quickly. When you repeat these tests using the spectator camera, the game doesn't crash at all.

If I were to guess, I'd suggest that that the presence of the player character triggers something to load (or reload), which may be failing to complete before it's required by the camera, resulting in a hard freeze, and eventual crash. I bet the crash logs for this are very complicated and graphics heavy, so hopefully this investigation provides the information you need to finally fix this issue.