Page 1 of 1

Ship repair bug

Posted: Tue Oct 20, 2009 11:34 am
by Walloc
Been looking throught the forum an cant i find any reports of this. So here goes.

It seem the "spot" code wise that ships gets in the damaged status, some times gets mixed up.
So the ID of the ship doesnt match the spot its given in the code.

3 pictures follow and a save game. If pw is needed i assume not, pm me.

Picture 1. All ships are on normal repair urgency. combined capacity is 67,470.

Picture 2 Cassin a DD around 1500 tons is put on High and the capcity rise to 99,770

Picture 3 Cassin down at normal again and BB West Virginia is put on high and the capacity rise to 68,835

So it seems the code gets ships mixed up. It from all i can see defernatly have an effect.
I've had 3 DDs on critical. So when looking at some of the ships the capcity would say above the 100.000 blocking some ships from repairing. While looking at others it be below. While not changings any of the ships prioverty.
Neither of the BBs made any repairs for 60+ turns while the 3 DDs was at critcal. Manually counting up it should have been no more than at 75ish capacity. Showed at 150k+ on some of the ships while not on others.
After i figured it out the BBs have started repairing. So it seems that the port actually think its over capacity and with hold some of the ships from repairing.

Kind regards,

Rasmus

Image

RE: Ship repair bug

Posted: Tue Oct 20, 2009 11:36 am
by Walloc
No text

Image

RE: Ship repair bug

Posted: Tue Oct 20, 2009 11:36 am
by Walloc
No text

Image

RE: Ship repair bug

Posted: Tue Oct 20, 2009 11:38 am
by Walloc
Save

RE: Ship repair bug

Posted: Tue Oct 20, 2009 11:49 am
by Don Bowen

Does look a little under-right. I'll take a look.

RE: Ship repair bug

Posted: Tue Oct 20, 2009 11:57 am
by Walloc
If u want a earlier save with all 3 DDs on critical showing the "full extend" of the issue, let me know. Think u can check SF and IIRC there is problems there too of same kind.

Kind regards,

Rasmus

RE: Ship repair bug

Posted: Tue Oct 20, 2009 12:52 pm
by Don Bowen

No thanks, problem is obvious once one looks at it. Just a timing issue in a calculation loop.

Good catch!