View Issue Details

IDProjectCategoryView StatusLast Update
0001720FSSCPmultiplayerpublic2008-11-11 00:58
ReporterFUBAR-BDHR Assigned Totaylor  
PrioritynormalSeveritytrivialReproducibilitysometimes
Status resolvedResolutionfixed 
Product Version3.6.9 
Fixed in Version3.6.10 
Summary0001720: Sometimes client reports host ship as 0 hull when the host is still alive with 1 hull left
DescriptionThat pretty much sums it up.
Additional InformationTBP 3.6.9 build but I'm pretty sure this one has been around since retail.
TagsNo tags attached.

Activities

2008-07-04 02:32

 

screen0256.jpg (76,675 bytes)   
screen0256.jpg (76,675 bytes)   

2008-10-21 04:01

 

screen0017.jpg (52,308 bytes)   
screen0017.jpg (52,308 bytes)   

2008-10-21 04:02

 

screen0018.jpg (57,660 bytes)   
screen0018.jpg (57,660 bytes)   

2008-10-21 04:02

 

screen0019.jpg (58,082 bytes)   
screen0019.jpg (58,082 bytes)   

FUBAR-BDHR

2008-10-21 04:03

developer   ~0010077

Attached 3 new screenshots. This time hosting on a standalone. The ships have even fully recovered their shields even though reporting 0 hull.

taylor

2008-10-21 05:56

administrator   ~0010078

I think that this is because it can technically have < 1% hull, but the math in there needs it to be at least 1% when going over the wire. It just gets round down to 0 from loss of precision basically. Fixing it doesn't look difficult, I just want to make sure that nothing is going to get broken in the process. :)

FUBAR-BDHR

2008-10-21 20:09

developer   ~0010083

It hit me sometime last night while not sleeping that there are possibly 2 different bugs here. The original report was for clients seeing the host ship as 0 when it wasn't. Only seen in TvT and Dogfight. Yesterday was the first time I've ever seen this happen with an AI ship in a Coop mission. They still could be the same problem. It could be the ones from yesterday only happen on a standalone though.

taylor

2008-10-21 20:22

administrator   ~0010084

There are actually two different places that the information gets sent over the network, so it is easily possible that some situations will do it one way and other situations will use another. It is done in two very different ways too, which makes it a bit annoying.

I should have at least one fixed but I haven't figured out exactly how best to deal with the other one just yet.

2008-10-23 05:29

 

screen0133.jpg (69,961 bytes)   
screen0133.jpg (69,961 bytes)   

FUBAR-BDHR

2008-10-23 05:30

developer   ~0010103

Uploaded another screenshot. First time I've ever seen this with a cap ship.

taylor

2008-11-11 00:58

administrator   ~0010169

Fixered.

Issue History

Date Modified Username Field Change
2008-07-04 02:32 FUBAR-BDHR New Issue
2008-07-04 02:32 FUBAR-BDHR File Added: screen0256.jpg
2008-10-21 04:01 FUBAR-BDHR File Added: screen0017.jpg
2008-10-21 04:02 FUBAR-BDHR File Added: screen0018.jpg
2008-10-21 04:02 FUBAR-BDHR File Added: screen0019.jpg
2008-10-21 04:03 FUBAR-BDHR Note Added: 0010077
2008-10-21 05:56 taylor Note Added: 0010078
2008-10-21 20:09 FUBAR-BDHR Note Added: 0010083
2008-10-21 20:22 taylor Note Added: 0010084
2008-10-21 20:23 taylor Status new => assigned
2008-10-21 20:23 taylor Assigned To => taylor
2008-10-23 05:29 FUBAR-BDHR File Added: screen0133.jpg
2008-10-23 05:30 FUBAR-BDHR Note Added: 0010103
2008-11-11 00:58 taylor Status assigned => resolved
2008-11-11 00:58 taylor Fixed in Version => 3.6.10
2008-11-11 00:58 taylor Resolution open => fixed
2008-11-11 00:58 taylor Note Added: 0010169