El Viejo wrote:I just got killed whilst docking manually, under heavy Viper fire.
I was actually in the slot when the ship blew (thought I’d made it… damn).
‘Press Space’ didn’t work… I was left spinning endlessly in the slot, so I had to crash the game.
I got this error in the Latest.log:
Code: Select all
[general.error.inconsistentState]: ***** ERROR: status is STATUS_DEAD, not STATUS_DOCKED, but dockedStation is not nil; treating as docked. This is an internal error, please report it.
I can reproduce this pretty easy: while docked I wrote
player.ship.explode() in debug console with r 3281, which resulted the player ship to explode while being docked..
I recalled that I couldn't press space because I tend to test odd things like that. An odd side effect was if you then pressed f1 to launch while press space commander after player.ship.explode(), you launched and exploded again. I did'nt report it though as it seemed unlikely that a player would die while being docked, unless explicitly scripted to die and in that case it would be the scripters responsibility
I updated to 3320 and retrying the above..
what happens now is the following
the players ship gets its energy zapped to -499999872
how he is stil alive..
meaning that once the player presses launch
his ship explodes again...
so the error is still there, i presume had this been the viper , the same thing would happen..
the hard error though is gone from the log file, since the player dies while not being docked..
Edit but that is not all
The players ship also overheats, and dies, even when energy has been restored by debugconsole
Cheers Frame...