|
Post by jwsmith26 on Jul 23, 2016 14:25:30 GMT -6
The training interface does seem pretty broken. When I opened the training screen this morning there was more weirdness. This time all three training boxes were checked and both the "Stop Training" and "Apply" buttons were active. When I clicked on the "Stop training" button it popped up its normal message "This will stop all training immediately ...", which is as it should be. But, strangely the "Apply" button was also active, and when clicked, popped up the confirmation box to start training. Both buttons should not be active at once. I then checked the RTWGame2.bcs and noted that it indicated I was in the midst of training in all three areas but the time remaining was 0. I started training in July 1916. I ran three months, to October, then checked the RTWGame2.bcs file. No changes - the training time remaining was still listed as 0. I Checked the date stamp on RTWGame2.bcs and noted that it had not updated since 6:49 yesterday even though I had made changes to training in the interim. I checked the attributes on the RTWGame2.bcs file and it is writeable. I also noted that other files in the Game2 save directory had been updated just a few minutes ago. The autosave.bcs did update properly but showed the same information for training as the RTWGame2.bcs (training in three areas for 0 months). I also noted that the date shown at the top of RTWGame2.bcs was incorrect at 6/1/1916 while in the atuosave.bcs it was correct at 9/1/1916. So, yeah, things seem a bit buggy with the training system at the moment. As a followup to the above I should report that when I went back into the training screen and correctly selected just two areas to train in everything seems to work correctly again. After several months of play the RTWGame2.bcs file has updated as it should and shows the values that would be expected.
|
|
|
Post by ddg on Jul 23, 2016 20:18:39 GMT -6
Hardly game-ending, but I'm encountering a bug with sunk dates. Raiders that are forced to scuttle seem to record their sinking date as 12/30/1899: Attachment DeletedThere also seems to be an extra space prepended to the "Sunk in duel with <ship name>" sinking and in the middle of the "Sunk in battle <extra space here><location description>."
|
|
Roumba
Junior Member
Posts: 88
|
Post by Roumba on Aug 14, 2016 22:28:09 GMT -6
Near the end of 1906, I researched Cross-Deck Firing. However, I have neither Medium Wing Turrets nor Main Battery Wing Turrets researched. Wouldn't it make sense if one or both of those techs were a prerequisite? As it is now, only my DDs and CLs(with <7") can possibly use a Cross-firing configuration.
Is this WaI?
|
|
|
Post by joebob73 on Aug 15, 2016 0:47:37 GMT -6
I'm noticing a bug with the "ships sunk" list. Sometimes, ships sunk near the start of the game disappear from the list by the end. Only seems to happen for enemy ships, and is extremely noticeable if you play all the way to 1950.
|
|
|
Post by dimovski on Aug 16, 2016 12:38:58 GMT -6
Not sure if this has been mentioned before, but if you have a battleship with, say, A and Y triple turrets, and you have "only" twin wing turrets, when rebuilding the main armament to a higher calibre you only need to reduce the number of guns in the A and Y turrets, but you get to keep the twin wing turrets (with increased gun size).
|
|
|
Post by Fredrik W on Aug 16, 2016 13:45:51 GMT -6
Near the end of 1906, I researched Cross-Deck Firing. However, I have neither Medium Wing Turrets nor Main Battery Wing Turrets researched. Wouldn't it make sense if one or both of those techs were a prerequisite? As it is now, only my DDs and CLs(with <7") can possibly use a Cross-firing configuration. Is this WaI? Some destroyers and cruisers had cross deck firing, so, yeah, until you research wing turrets you can only use it on light ships.
|
|
|
Post by joebob73 on Aug 16, 2016 13:51:05 GMT -6
Attachment DeletedAny idea why I'm getting a message saying "illegal speed value" after hitting the "turn" button?
|
|
|
Post by Fredrik W on Aug 16, 2016 14:02:31 GMT -6
Any idea why I'm getting a message saying "illegal speed value" after hitting the "turn" button? I am guessing the AI is trying to design something illegal. Was it only once or does it persist?
|
|
|
Post by joebob73 on Aug 16, 2016 14:05:48 GMT -6
Any idea why I'm getting a message saying "illegal speed value" after hitting the "turn" button? I am guessing the AI is trying to design something illegal. Was it only once or does it persist? Only once, but it happens 2-3 times per game. Could it be a 35 knot DD design hitting the "exceeding design speed" event?
|
|
|
Post by Fredrik W on Aug 16, 2016 14:12:12 GMT -6
I am guessing the AI is trying to design something illegal. Was it only once or does it persist? Only once, but it happens 2-3 times per game. Could it be a 35 knot DD design hitting the "exceeding design speed" event? I don't think so, but if you have 35 knot DDs it might well be the AI thinking that it wants an even faster DD and forgetting about the 35 knot upper limit.
|
|
|
Post by JagdFlanker on Aug 16, 2016 17:05:59 GMT -6
i get the ai ship design error here and there, every game at least once. usually there's at least a few errors at game initial start, i'v been playing only Italy and Hungry the last month. i save every turn so i'l try and catch one next time
|
|
|
Post by jwsmith26 on Aug 21, 2016 9:31:06 GMT -6
I've run into a bug in Ver. 1.33 b1 that was not present in version 1.32. In tactical battles the division ship screen is not showing torpedoes correctly. It is displaying 2/0 or 4/0, which is obviously incorrect. The problem appeared on every ship I examined. The number of torpedoes does display correctly on the individual ship screen. A slightly more serious version of the bug also appeared. The division screen reported that I had one unlaunched torpedo remaining when in fact that torpedo was associated with a launcher that had been destroyed. I've attached a screen shot showing this. Attachment Deleted
|
|
|
Post by jwsmith26 on Aug 21, 2016 9:55:58 GMT -6
Here's another bug that I have not seen before installing v1.33 b1. When I reloaded a game that had an ongoing battle I could see the location of all of the enemy ships, as you can see in the screen shot below. When I zoomed into the battle area, the ships that I should not be able to see disappeared. When I zoomed out again there they were. Attachment DeletedHere's an update to this bug. After the battle I moved some ships down toward the group of enemy ships visible in the screen shot. When I arrived on the scene there were no enemy ships in the area. When I zoomed out again the blue dots that normally indicate enemy ships appeared again in exactly the same position they appeared earlier in the battle. So, obviously not actual ships but this does still appear to be a bug. Attachment Deleted
|
|
|
Post by Fredrik W on Aug 21, 2016 13:45:26 GMT -6
Here's another bug that I have not seen before installing v1.33 b1. When I reloaded a game that had an ongoing battle I could see the location of all of the enemy ships, as you can see in the screen shot below. When I zoomed into the battle area, the ships that I should not be able to see disappeared. When I zoomed out again there they were. Here's an update to this bug. After the battle I moved some ships down toward the group of enemy ships visible in the screen shot. When I arrived on the scene there were no enemy ships in the area. When I zoomed out again the blue dots that normally indicate enemy ships appeared again in exactly the same position they appeared earlier in the battle. So, obviously not actual ships but this does still appear to be a bug. Thanks! I'll take a look at it.
|
|
|
Post by HolyDragoon on Aug 22, 2016 15:31:40 GMT -6
I'm afraid the battle objectives are bugged as well, at least the Sink X ships (any).
In two battles, I have the Sink 2 ships (any) objective. Well, I sunk more than two of them, and the objective wasn't accomplished.
I figured something was wrong when I right clicked on the objective, and the 'Locate' option gave me a target somewhere near Korea, when my battle was somewhere in the Adriatic. Is the mission generator derping when assigning the location for the objective?
|
|