View Issue Details

IDProjectCategoryView StatusLast Update
0002751FSSCPmultiplayerpublic2014-06-30 03:08
ReporterFUBAR-BDHR Assigned ToWanderer  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Product Version3.6.15 
Summary0002751: A ship rotated too far. Offending vessel is %s, please investigate.
DescriptionFound this on the mediavp standalone. The ship was Scorpio 2 in mission Fighteer-m01.fs2 The data isn't making much sense on this either.

Scorpio 2 is a hostile Mara.

In the object it's showing that it has a hull of 170 and all 4 shield quads are at 155. In ships it shows that it has a max hull of 200 and shields of 620. So it looks like it took hull only damage but damage taken in ship shows 0.

Also we have the ship exceeding max speed with afterburner energy still at 300. This would only make sense if the ship did take a hit probably from a shockwave.

At least 2 ships blew up right before the assert. 1 was Alpha 2 (most likely a player that was registered destroyed a few frames before that) the other (and last) ship destroyed immediately after was a support ship (yea possibly another support ship bug).

Now the best scenario I can come up with here is that Scorpio 2 was hit by a shock wave from the support ship going boom. That would make sense except that Scorpio 2 is showing that it never fired any weapons either primary or secondary so how was it in range of the friendly ships? Hit during warpin is also out as Scorpio 1 was destroyed earlier so the wing had already arrived.
TagsNo tags attached.

Activities

FUBAR-BDHR

2012-12-13 01:34

developer  

2751.rar (131,517 bytes)

Sushi_CW

2012-12-13 01:49

developer   ~0014432

Unassigned myself since at this point I'm pretty much retired.

Wanderer

2013-11-05 09:18

developer   ~0015382

I'm not quite sure if there is anything to be done about this issue - apart from perhaps turning the assertion into warning. Especially as it only triggers on debug builds. If i understood the code correctly the too rapid rotation essentially triggered old :V: made debug function intended to trap the culprit.

Main issue for this event surfacing seems to have been the flframetime - or delta_time - which according to the log was just a bit above 0.20f - meaning just 4 to 5 frames per second.

Goober5000

2014-06-30 03:08

administrator   ~0015947

Agree with Wanderer. This can be closed.

Issue History

Date Modified Username Field Change
2012-12-13 01:31 FUBAR-BDHR New Issue
2012-12-13 01:31 FUBAR-BDHR Status new => assigned
2012-12-13 01:31 FUBAR-BDHR Assigned To => Sushi_CW
2012-12-13 01:34 FUBAR-BDHR File Added: 2751.rar
2012-12-13 01:49 Sushi_CW Assigned To Sushi_CW =>
2012-12-13 01:49 Sushi_CW Note Added: 0014432
2012-12-13 03:07 niffiwan Status assigned => new
2013-11-05 09:18 Wanderer Note Added: 0015382
2013-12-03 09:46 Echelon9 Category AI => multiplayer
2014-06-30 03:08 Goober5000 Note Added: 0015947
2014-06-30 03:08 Goober5000 Assigned To => Wanderer
2014-06-30 03:08 Goober5000 Status new => closed
2014-06-30 03:08 Goober5000 Resolution open => no change required