Log in

View Full Version : HMS Nelson keeps spawning in Gilbratar harbour.


Mouftic
03-22-11, 05:51 PM
Is there any fixes out there that prevents ships that have been sunk to spawn again in the next patrol.

I only tried with the HMS Nelson so I dont know if it's isolated or not.

frau kaleun
03-22-11, 06:09 PM
I don't think so.

I sank the Warspite once in April 1940 and she kept showing up in the middle of the Freetown convoys later that year.

For capital ships that have more than one ship in their class I've changed their display names to show their class (i.e., 'Nelson class' instead of 'HMS Nelson' and so on) and not the particular ship's name every time it spawns. At least that way if one of them keeps respawning the game doesn't ID it as the same specific ship by name over and over again.

For the Nelson I think there were only two ships of that class anyway, but I figure the chances I would ever sink both are so slim that if I sink one I can always pretend the other one is not that one if I happen to run into it.

If I sank both I guess I'd just have to pretend I was playing in a parallel universe where the Admiralty just kept churning out Nelson class battleships. :haha:

desirableroasted
03-22-11, 06:35 PM
Capital ships (and I assume others) even respawn in the same patrol. In GWX, 13 April 1940, you can sink Warspite at Narvik in the morning. You can easily encounter her again that evening on the way out.

As far as I know (and this is anecdotal), they do not respawn in the same game session, but other than that, it can be deja vu all over again.

Gargamel
03-22-11, 07:05 PM
As far as I know (and this is anecdotal), they do not respawn in the same game session, but other than that, it can be deja vu all over again.

I believe they can, I've seen logs that have the hood listed multiple times. Same session though, I dunno. Again Anecdotal.

But the OP is basically asking for an early version of a dynamic campaign, which SH3 does not have. By asking it to not use the same ship twice, It would have to find a replacement. And to find a replacement, it would need to altar the campaign to move another ship over. And then that ship needs a replacement. Why stop at ships? You can start adding various thresholds to truly make the game dynamic.

Mouftic
03-22-11, 08:04 PM
I just assumed it would remove it completely :). Would have been realistic that way. Maybe that has been changed in later versions.

Thanks for the replies!!!

Fish In The Water
03-22-11, 08:25 PM
Capital ships (and I assume others) even respawn in the same patrol. In GWX, 13 April 1940, you can sink Warspite at Narvik in the morning. You can easily encounter her again that evening on the way out.

Poor old Warspite doesn't know enough to quit when she's behind...

Gotta admire the tenacity though, takes a lickin' and keeps on tickin'! :O:

danzig70
03-23-11, 10:53 AM
Is there any fixes out there that prevents ships that have been sunk to spawn again in the next patrol.

I only tried with the HMS Nelson so I dont know if it's isolated or not.

You can open the campaign file in the mission editor and remove the units using the explorer to locate them all. Then edit the config file and change the disappear date to the date you sunk her. If you do it after a patrol and before the next, it should be ok.

Alternatively you can edit the campaign file in a text editor and edit it. Eventually, I would like to make a program that does this.

Jimbuna
03-27-11, 09:39 AM
You can open the campaign file in the mission editor and remove the units using the explorer to locate them all. Then edit the config file and change the disappear date to the date you sunk her. If you do it after a patrol and before the next, it should be ok.

Alternatively you can edit the campaign file in a text editor and edit it. Eventually, I would like to make a program that does this.

Been tried....and the quickest way to create CTD's....a mammoth task that one.

Back OT...a ship will respawn once it is beyond your own SH3 world rendering range which is approximately 50km provided it is not set at 'delete at last waypoint' which is less than 50km away.