destroyers burning bug?

klh · 06-30-20, 07:24 AM

I attacked a large convoy in August 1940. Before I attacked, three of the destroyers were on fire, but it did not seem to affect their abilities. After my first attack, I did an end run and attacked again many hours later. The same three destroyers were still burning, but they participate in the counter-attack as if nothing is wrong.

I think I remember this was a bug back when SH3 first came out, but I can't find any posts about it. Does anyone know what caused this?

Pisces · 06-30-20, 07:58 AM

Burning ships happens every now and then. Maybe they dove too deep into a wave at some point and deckstructures got damaged. Or they ran into each other when getting settled after spawning. Nothing to worry about. Real ships get damaged ever so often too you know. No torpedoes required for that.

Grumpy Pete · 06-30-20, 09:14 AM

I have no way of proving this but I think the burning ships in convoy may have something to do with the time compression setting when the convoy is first detected. I've recently backed off my time compression when I know I will be making detection in about an hour and since doing that, I haven't seen burning ships. (I back off to X64).

My reasoning is that some of the ships spawn basically on top of each other and then while moving to their assigned positions in the convoy they have collisions (or something). Again, my reasoning is more anecdotal than facts based...

CapZap1970 · 06-30-20, 10:23 AM

Quote:

Originally Posted by Grumpy Pete

I have no way of proving this but I think the burning ships in convoy may have something to do with the time compression setting when the convoy is first detected. I've recently backed off my time compression when I know I will be making detection in about an hour and since doing that, I haven't seen burning ships. (I back off to X64).

My reasoning is that some of the ships spawn basically on top of each other and then while moving to their assigned positions in the convoy they have collisions (or something). Again, my reasoning is more anecdotal than facts based...

Maybe that's the same reason why after too long periods of running with high time compression rates you return to ports and some ships are burning or out of place... 2 patrols ago I returned to Kiel and all the ships in the schleuses were out of place, one of them was even blocking the schluese to get in the Kanal...

Anvar1061 · 06-30-20, 11:01 AM

Quote:

Originally Posted by CapZap1970

Maybe that's the same reason why after too long periods of running with high time compression rates you return to ports and some ships are burning or out of place... 2 patrols ago I returned to Kiel and all the ships in the schleuses were out of place, one of them was even blocking the schluese to get in the Kanal...

You sailed for too long, and at that time there was a tsunami and the ships broke anchor.

klh · 06-30-20, 11:55 AM

Thanks. That refreshes my memory. I will just ignore them.

Pisces · 06-30-20, 12:32 PM

Didn't think of time compression, but yeah. High levels could make ships jump around and dive to deep or leap too far into other ships 'personal spaces'. Better give them some time to react on what is going on.

CapZap1970 · 06-30-20, 10:48 PM

Quote:

Originally Posted by Pisces

Didn't think of time compression, but yeah. High levels could make ships jump around and dive to deep or leap too far into other ships 'personal spaces'. Better give them some time to react on what is going on.

Yeah... from the time I found Kiel a mess like 27 days after sailing to a patrol, no more TC above 128...

CapZap

CapZap1970 · 06-30-20, 10:50 PM

Quote:

Originally Posted by Anvar1061

You sailed for too long, and at that time there was a tsunami and the ships broke anchor.

It was a biiig Tsunami....

06-30-20, 07:24 AM	#1
klh Der Alte Join Date: Jan 2002 Location: Indiana, USA Posts: 227 Downloads: 200 Uploads: 0	destroyers burning bug? I attacked a large convoy in August 1940. Before I attacked, three of the destroyers were on fire, but it did not seem to affect their abilities. After my first attack, I did an end run and attacked again many hours later. The same three destroyers were still burning, but they participate in the counter-attack as if nothing is wrong. I think I remember this was a bug back when SH3 first came out, but I can't find any posts about it. Does anyone know what caused this?

06-30-20, 07:58 AM	#2
Pisces Silent Hunter Join Date: Dec 2004 Location: AN9771 Posts: 4,904 Downloads: 304 Uploads: 0	Burning ships happens every now and then. Maybe they dove too deep into a wave at some point and deckstructures got damaged. Or they ran into each other when getting settled after spawning. Nothing to worry about. Real ships get damaged ever so often too you know. No torpedoes required for that. __________________ My site downloads: https://ricojansen.nl/downloads

06-30-20, 12:32 PM	#7
Pisces Silent Hunter Join Date: Dec 2004 Location: AN9771 Posts: 4,904 Downloads: 304 Uploads: 0	Didn't think of time compression, but yeah. High levels could make ships jump around and dive to deep or leap too far into other ships 'personal spaces'. Better give them some time to react on what is going on. __________________ My site downloads: https://ricojansen.nl/downloads

06-30-20, 09:14 AM	#3
Grumpy Pete Shore leave Join Date: Jun 2020 Posts: 70 Downloads: 8 Uploads: 0	I have no way of proving this but I think the burning ships in convoy may have something to do with the time compression setting when the convoy is first detected. I've recently backed off my time compression when I know I will be making detection in about an hour and since doing that, I haven't seen burning ships. (I back off to X64). My reasoning is that some of the ships spawn basically on top of each other and then while moving to their assigned positions in the convoy they have collisions (or something). Again, my reasoning is more anecdotal than facts based...

06-30-20, 11:55 AM	#6
klh Der Alte Join Date: Jan 2002 Location: Indiana, USA Posts: 227 Downloads: 200 Uploads: 0	Thanks. That refreshes my memory. I will just ignore them.