...new problem (actually seems to be a bug this time - reproducible and everything).
Got hit by a thruster plume right after winning a race, and as my ship was going up in flames, the game crashed. Given that it was kind of a terrible way to lose a ship, I was tempted to alt+f4 but the game locked up before my ship exploded... then just closed on me with no warning.
On relaunching the game and trying to repeat the dive and race again, the "Bring it on!" answer when asked if I'm challenging the ship was flagged (incorrectly) as a "hang up" option, but continued the conversation properly. When I tried to rematch, the line was (again) tagged as a "hang up" option, but this time, actually behaves like one. Which prevents me from rematching.
Viewing post in 1.63.6 - Poltergeist Protocol comments
Reproduction steps for the crash:
-Playing on a relatively new i7/RTX4070 system, capable of handling an uncapped framerate of 220fps when there isn't an insane amount going on and rarely dropping below 200 even during most high-complexity interactions.
-Flying a Kitsune in compact mode (it's possible in other ships or with the cargo bay expanded, but harder to trigger on purpose).
-Get a thruster or plasma thrower from anotehr ship lined up perfectly to blast its plume into the glowing strip on the side of the ship where it extends, as close to perpendicular as possible.
-Give the other ship a reason to burn with that specific thruster and melt the inside of your ship.
This will *usually* result in instant 6000K+ temperature *and* instant 100% overheat applied to the ship's computer. If so, the game will *sometimes* lag out to the point of taking 3 to 5 seconds to load the next frame, and basically stalling time to try and work out just how screwed you are.
If the game survives long enough to see the ship explode, it probably won't crash, but sometimes it doesn't make it that long and just closes on you, no warning, no error, just gone.