|
|
Post by xenontennessee on Nov 23, 2021 0:36:48 GMT -6
I made an experiment to test this decision procedure of hidden flaws in ship design.
I have a class of 3 battleships, whose construction is to be finished next month. So I clicked save, and skipped to the next month. The ships were commissioned, with no flaws.
After exiting without saving, I loaded the savefile of last month again, and repeated the process for several times. Then, I saw the reminder, "the ship has trouble reaching its design speed".
After that, although each time I still loaded the savefile of last month, when the flaws shouldn't have been decided, the ships were completed with the same flaw of low speed, even without a reminder! In that way, the savefile mechanism seems to be useless.
I don't quite understand the principle. How is a "hidden flaw" decided? Is this a bug?
|
|
|
|
Post by xenontennessee on Nov 23, 2021 1:00:17 GMT -6
I noticed another rule of this. The first ship to finish construction will be "normal" when you load again and there isn't any flaw, while the other ships of the class will remain the same status as last time. For example, the ships A, B and C are of the same class, and in a game they all meet the problem of not reaching design speed 28 knots, only 27. I quit without saving and load the savefile again, skip to next month, and there aren't any flaws in them, then the ship A will be 28, while the other two remain 27.
|
|
|
|
Post by dorn on Nov 23, 2021 3:35:27 GMT -6
When you get event of launching ship, any changes to ship is included on that ship and are saved when you save the game and on class file.
If new ship is launched it takes all information from class file so reloading game will not change this event if this event made some change.
|
|
|
|
Post by xenontennessee on Nov 23, 2021 4:41:04 GMT -6
When you get event of launching ship, any changes to ship is included on that ship and are saved when you save the game and on class file. If new ship is launched it takes all information from class file so reloading game will not change this event if this event made some change. That seems to explain most of the problem. Thanks! |
|
|
|
Post by director on Nov 24, 2021 16:21:44 GMT -6
This can also be an issue if you are building multiple units of a class and (for example) put the first one in for a rebuild while the second one comes out.
If you accept the 'fit latest fire control' to one class member and not to another, you may end up with two 'identical' classes.
|
|
w2c
Full Member
Posts: 178
|
Post by w2c on Nov 24, 2021 17:22:30 GMT -6
This can also be an issue if you are building multiple units of a class and (for example) put the first one in for a rebuild while the second one comes out. If you accept the 'fit latest fire control' to one class member and not to another, you may end up with two 'identical' classes. It's been awhile since I had that happen, but doesn't the game simply create a retrofit design and you could just immediately rebuild any already built ships into that design to get them all the same though? That would mean they're actually 2 different ship files. The base class and then the retrofit class. |
|
|
|
Post by director on Nov 29, 2021 11:58:12 GMT -6
I've found that the game considers them two different ships. You cannot refit one into the other or use a common refit design even if the original two are identical.
|
|
