Why Yamato battleship cannot be set speed?

[all_my_loving]

The battleship cannot be set speed under mission editor, and it also stop in SH5, but I attacked it with torpedoes, When the torpedoes approached the target, The battleship ran away immediately.

[kapuhy]

Originally Posted by all_my_loving

The battleship cannot be set speed under mission editor, and it also stop in SH5, but I attacked it with torpedoes, When the torpedoes approached the target, The battleship ran away immediately.

A lot of japanese ships are like that, it must have something to do with the way they were imported. I'd suggest to check yamato and one of normally behaving imported ships (like Bourrasque) for differences in S3D.

[all_my_loving]

Originally Posted by kapuhy

A lot of japanese ships are like that, it must have something to do with the way they were imported. I'd suggest to check yamato and one of normally behaving imported ships (like Bourrasque) for differences in S3D.

yes, it's a good idea for me. now, I use notepad to edit the NBB_Yamato.cfg which is located at file directory as ..Silent Hunter 5/data/Sea/NBB_Yamato
, I modified MaxSpeed 0 to 27 then save file, so I return the mission that Yamato can move.

[vdr1981]

Originally Posted by all_my_loving

yes, it's a good idea for me. now, I use notepad to edit the NBB_Yamato.cfg which is located at file directory as ..Silent Hunter 5/data/Sea/NBB_Yamato
, I modified MaxSpeed 0 to 27 then save file, so I return the mission that Yamato can move.

If you do that you'll get CTDs in the musem and in the campaign as well. Units with 0 speed in cfg files should be used only as static units.

[kapuhy]

Originally Posted by vdr1981

If you do that you'll get CTDs in the musem and in the campaign as well. Units with 0 speed in cfg files should be used only as static units.

Any idea why are they causing CTDs? By the way, the "motionless" ships include German Raumboot, does this mean it is not operational in campaign?

[vdr1981]

Originally Posted by kapuhy

Any idea why are they causing CTDs? By the way, the "motionless" ships include German Raumboot, does this mean it is not operational in campaign?

It does, but i kept the unit in the game for some harbor scenery... This can happen sometimes with SH3 imported units.No idea why though...

[all_my_loving]

Originally Posted by vdr1981

If you do that you'll get CTDs in the musem and in the campaign as well. Units with 0 speed in cfg files should be used only as static units.

I tried to set a reliable value of MaxSpeed to 9, the Yamato works well in the museum. If I set it to ≥ 10, the game crashes to desktop immediately.

[kapuhy]

Originally Posted by all_my_loving

I tried to set a reliable value of MaxSpeed to 9, the Yamato works well in the museum. If I set it to ≥ 10, the game crashes to desktop immediately.

@vdr1981: I ran this (with MaxSpeed=9) through your rendering test mission. I went through entire roster from left to right without CTD, but unfortunately Yamato still crashes the game if I try to display it again after all other units have already been displayed in museum.

Edit: honestly if this was just the Yamato I wouldn't be concerned, (probability of meeting it in campaign at sea and not in port would be minimal anyway) but I'd really like that option to call nearby Raumboot/E-boot squadron when I'm crippled by Coastal Command in Bay of Biscay so I'll look into it.

[vdr1981]

Originally Posted by all_my_loving

I tried to set a reliable value of MaxSpeed to 9, the Yamato works well in the museum. If I set it to ≥ 10, the game crashes to desktop immediately.

It seems that 9 knots trick holds quite well but I'll have to test this further more... This is really good find all_my_loving.


EDIT: I'm afraid I'll have to take that back. It seems that 9knots will lower the CTD rate, but it's still there after several rendering in the museum. Still, good find though...