Burning targets get fixed after loading?!

[Temujin]

I encountered a tanker escorted by a warship.
I let the warship pass and banged the tanker.

While on surface, trying to blast the flaming tanker, the warship made a U-turn and came towards me.

I dived , and banged the warship with a tail torpedo - nice blast.

In the meantime, the flaming tanker got cheeky, developed speed and got far from me..

Well, I thought. I'll reload the hole situation from a saved 'burning target' game and try again.

Oh no, It seems that the tanker loaded 'without a scratch', sailing away.
What happen? Is it another (huge) bug after the last (1.2) patch?

Is there a way around it?

F * * K !! :down:

Temujin (pissed off)

[KaptajnNP]

That's just bad for you:down:.
Another of those fugging bugs that can make the game a horrible experience.

I have tried to take out 3 ships with 3 torps, saved and left the game. Later I would take them out with the deckgun, but when I loaded the ships just flew away at flank speed...:nope:

[Jimbuna]

This happens because when you reload the game, the ships in the vicinity are rendered again, the game does not keep tabs on damage levels, on save the ship is simply alive and well or destroyed...the same criteria is used on loading a save.

[John Channing]

One of the things I noticed pre 1.02 was when I had the "Health Bar" on (ok, stop laughing... I just forgot to turn it of on my first patrol) that the "health" of the ship would still reflect damage after the save, but visually it would be fine.

In other words if I had pumped 99 shells into a ship and then saved, it would look fine on the re-load, but still be one shell away from sinking.

Not sure if this is the case post 1.02.

JCC

[Ducimus]

This happens because when you reload the game, the ships in the vicinity are rendered again, the game does not keep tabs on damage levels, on save the ship is simply alive and well or destroyed...the same criteria is used on loading a save.

This.

For the folks who don't know, this is the same behavior accross SH3, SH4, and SH5. When an object is rendered (again), the game loads the criteria for that object. Damage levels are temporary information that are only tracked on a single instance of whatever object is being rendered. This saves system resources considering how many ships/planes the game is tracking.

Long story short, if you damage a target and want it sunk, you must see it to the bottom before you quit that play session, or before that target gets 30KM distance away from you.

[Webster]

This happens because when you reload the game, the ships in the vicinity are rendered again, the game does not keep tabs on damage levels, on save the ship is simply alive and well or destroyed...the same criteria is used on loading a save.

i would add that another cute feature this has is a DD that was low on DC will respawn with a full load so if you are saving in order to evade him later can simply result in reloading that pesky DD that was running out of ammo

[longam]

If they could create a bubble around your ship, say 5 miles, and save that health information that would take some of the load off. Seems plausible anyway.

[McHibbins]

It is an unwritten rule since SH3 : never save with ships or land nearby !

[Jimbuna]

If they could create a bubble around your ship, say 5 miles, and save that health information that would take some of the load off. Seems plausible anyway.

I agree but it has never been the case thus far....probably down to hardcoding one must presume.

[urfisch]

i still get these weather bugs on loading...anyone else does?

[commandosolo2009]

you should send her to the bottom, save afterwards, not while its burning... plenty of shes to come, dont rush cannonball, it's call it a day after last torp, even if the ship is immobile, wait around 90 meters for others to pass, surface backside and boom boom with DG if u got rounds left, and flank speed of course..