CTD with Museum and Japanese ships

[Cthulhus]

Hello,

I have SH5 1.2+ The Wolves of Steel 1.05 + Update 09.

And nothing more.

I have a CTD all the time at the same moment.

Open the Museum, and brows Japanese ships and you'll get a CTD at the 3rd ship.

Hope that will help.

Not really important but ...

Thanks

[vdr1981]

Originally Posted by Cthulhus

Hello,

I have SH5 1.2+ The Wolves of Steel 1.05 + Update 09.

And nothing more.

I have a CTD all the time at the same moment.

Open the Museum, and brows Japanese ships and you'll get a CTD at the 3rd ship.

Hope that will help.

Not really important but ...

Thanks

I couldn't reproduce the same CTD like you did (on third unit) but museum did eventually crash after ten Japanese warships (or so) displayed. And most of the time on different unit...

Not that I can do much about it because, as far as the game engine is concerned , all displayed units are rendered at the same time. This will inevitably lead to occasional CTDs in the musem. Imported SH3/4 ships and planes will only make thing worse and Japan has plenty of them...

All imported Japanese units comes with OHII mod, so maybe you can leave the comment in the appropriate thread also. Maybe Trevally would like to revise those units and to check for potential errors...

[Cthulhus]

Thanks for the advise ! It's not really important. The most important is to have a stable game (the museum isn't the game for me).

Any way, thanks for your feedback !

[Trevally.]

I remember Uekel and I think it was Echolot discussing this museum issue in the German forums. Not 100% but I think it was an easy fix with either the roster or names doc not matching

[vdr1981]

Originally Posted by Trevally.

I remember Uekel and I think it was Echolot discussing this museum issue in the German forums. Not 100% but I think it was an easy fix with either the roster or names doc not matching

This is not just about museum instability. Same issues can be reproduced in regular campaign gameplay as well if certain conditions are met.
I don't think that we'll ever see proper fix for this issue without official 1.03 patch (that means never).