|
Post by Adseria on May 16, 2019 13:50:21 GMT -6
It's quite possible--witness how rarely the HSF sortied in WW1, despite routine activity by the Grand Fleet. Yes, but shouldn't it at least give you the choice, and penalise whichever side declines (since the other side basically has free reign)?
|
|
|
Post by dougphresh on May 16, 2019 15:17:31 GMT -6
Even if they are acting as a fleet in being and holed up in harbour, there would still be naval operations. French/Soviet warships run into mines and subs fairly often, so they’re out there.
RTW addressed this with bombardment and coastal raids, as well as cruiser and destroyer actions. Now that there are aircraft, that adds another dimension too, with maybe the possibility of air raids on airfields, ports, facilities.
Anyone who has played WITPAE or War Plan Orange knows that there can still be lots to do without major surface combatants.
|
|
|
Post by Adseria on May 16, 2019 15:54:55 GMT -6
Even if they are acting as a fleet in being and holed up in harbour, there would still be naval operations. French/Soviet warships run into mines and subs fairly often, so they’re out there. Obviously, you were just loading mines and subs onto your bombers and dropping them on the enemies' decks!
|
|
|
Post by archelaos on May 16, 2019 17:58:07 GMT -6
It's quite possible--witness how rarely the HSF sortied in WW1, despite routine activity by the Grand Fleet.
HSF? Italian battleline was at sea for 70 HOURS TOTAL during World War I. Yeah that's less than 4 days in 4 year long war. 70 hours at 16 kts is 1120 miles and the distance from Genoa to Taranto is around 800 miles...
|
|
|
Post by williammiller on May 16, 2019 19:23:42 GMT -6
The RTW2 Demo has been updated to version RC5, which has a number of fixes for issues reported with the previous demos.
|
|
|
Post by Adseria on May 16, 2019 19:55:05 GMT -6
The RTW2 Demo has been updated to version RC5, which has a number of fixes for issues reported with the previous demos.
Nice, thanks.
In the meantime, I found one that I haven't seen reported yet:
There are only 4 Spitfires in the attack, but it says 34 here.
Incidentally, there's actually an amusing story behind this attack. I got into a major battle; I had 4 BBs, 2 CVLs and a bunch of escorts. I'm still in the middle of the battle, so I don't know yet exactly what the enemy has, but I know they have at least 5 BBs and 2 BCs, plus escorts.
My light cruisers found the enemy BCs right at the start, so I immediately started preparing a strike and told it to launch against them. Unfortunately, I didn't realise that I'd left the CVLs on manual control, so they were just suicide charging at what later turned out to be the entire enemy force. I quickly turned them around, but I'd already ordered the strike; they couldn't turn into the wind and launch because they were in sight of the enemy, but the planes were on deck and ready to go as soon as the carriers could safely turn into the wind (which meant, back towards the enemy). Because of this, the strike didn't launch until about half an hour after the order was given. The BCs were well away from the target location at that point, but there was nothing I could do.
Then, just as we were launching, I started spotting a new group of enemy ships. The strike, launching late and aimed at a point well away from where the BCs were, was now instead aimed directly on top of the enemies' main BB force. The strike has just finished; we lost 2/3 planes, but scored 4 torpedo hits. I'm gonna call that one a win!
|
|
|
Post by williammiller on May 16, 2019 19:57:41 GMT -6
The RTW2 Demo has been updated to version RC5, which has a number of fixes for issues reported with the previous demos.
Nice, thanks.
In the meantime, I found one that I haven't seen reported yet:
There are only 4 Spitfires in the attack, but it sys 34 here.
Do you happen to have a save game from that? It would help us determine what the issue might be... Thanks!
(If you do, please zip it and post it here if its small enough if you wouldn't mind)
|
|
keris
New Member
Posts: 31
|
Post by keris on May 16, 2019 20:02:52 GMT -6
I'm getting this occurring off of regular fleet engagements. (like all of them on this save, didn't occur at all on my first playthrough.) Continuing to progress the game after closing the message will result in no new battles generating, although no additional error messages will pop up. Saving the game, exiting, and then reloading resumes normal engagements, at least until you end an engagement and the error pops up again.
I'm getting this "No MCI Device Open" error as well, exactly as stanmckhanic quoted above. I'll post specs/full dxdiag if necessary.
|
|
|
Post by williammiller on May 16, 2019 20:07:11 GMT -6
I'm getting this occurring off of regular fleet engagements. (like all of them on this save, didn't occur at all on my first playthrough.) Continuing to progress the game after closing the message will result in no new battles generating, although no additional error messages will pop up. Saving the game, exiting, and then reloading resumes normal engagements, at least until you end an engagement and the error pops up again.
I'm getting this "No MCI Device Open" error as well, exactly as stanmckhanic quoted above. I'll post specs/full dxdiag if necessary. I would try the new version RC5 Demo, that is one of the issues that was addressed in the new release that went up a few minutes ago. If it still does occur in that release please let us know.
|
|
|
Post by Adseria on May 16, 2019 20:09:02 GMT -6
Nice, thanks.
In the meantime, I found one that I haven't seen reported yet:
There are only 4 Spitfires in the attack, but it sys 34 here.
Do you happen to have a save game from that? It would help us determine what the issue might be... Thanks!
(If you do, please zip it and post it here if its small enough if you wouldn't mind)
From the battle? Sure.
EDIT: I just noticed it's happening with every attack; I'm getting reports of attacks being launched by hundreds of aircraft being launched by 2 carriers with a total capacity of 50 aircraft! I should clarify, by the way; this isn't happening in the log at the side of the screen, only when I open the log window. Attachments:Save file.zip (38.19 KB)
|
|
|
Post by charliezulu on May 16, 2019 20:15:21 GMT -6
I'm not sure if it's been reported, but TDS (or at least the UI) is broken when rebuilding. It doesn't show the TDS level, nor bulging.
|
|
keris
New Member
Posts: 31
|
Post by keris on May 16, 2019 20:21:04 GMT -6
I'm getting this "No MCI Device Open" error as well, exactly as stanmckhanic quoted above. I'll post specs/full dxdiag if necessary. I would try the new version RC5 Demo, that is one of the issues that was addressed in the new release that went up a few minutes ago. If it still does occur in that release please let us know. Ah great, thanks. I didn't realize there were revisions up, still have the first version probably lol.
|
|
|
Post by Adseria on May 16, 2019 20:49:47 GMT -6
So I was experimenting with all-forward armament designs, and I noticed that, while an ABL arrangement does count as all-forward, an ABC arrangement does not. Is this intentional? If so, it seems a bit odd, given that C turret is actually positioned forward of L turret.
|
|
Warspite
Full Member
Sky of blue/And sea of green
Posts: 230
|
Post by Warspite on May 16, 2019 21:13:54 GMT -6
Bug 1 I had a fleet exercise with all of my CVLs and there were no air groups on any of the carriers even though I had placed air groups on all of the carriers. After the exercise ended I checked that they had air groups and sure enough they did. During the exercise they just disappeared.
Bug 2 I fought a battle against the US and there were constant error messages towards the end of the battle. I must have clicked through over 50 of them. The error messages were:
"Error in CheckForceWithdrawal procedure! Access violation at address 00403F10 in module 'RTW2Demo.exe'. Read of address 6570754F
Some of the numbers and letters would change with each error message.
|
|
|
Post by seawolf on May 16, 2019 21:23:45 GMT -6
Airstrike hits (torpedo hits on ships) are not recorded in the after action report for aircraft
|
|