New! v01.01.15 Public Beta Available

[loki100]

ORIGINAL: Beethoven1

ORIGINAL: loki100

if you make it using the build screen, yes its clear, what status/TOE the formation will have. Realistically this only affects the Tank Corps (its very unlikely you'll have many mot brigades at Gds level before the Gds Mech corps can be formed). So since you can't build Tank Corps by on-map merger its pretty safe.

To make it using the build screen, wouldn't you have to send them to reserve? You generally would not want to do that if you can just form them on the map because you will lose CPP etc as well as time, as compared to simply forming them on the map and throwing them into a battle on the same turn they are formed.

well, worth stressing the obvious - tank brigades cannot be on the map so you can't construct a Tank Corps by combining on map (unlike say a Rifle Corps)

but no, they don't have to go to the reserve, just you do have to use the build screen.

At which stage I tend to refer to the manual and a table that took a fair bit of getting right:



given how tank corps appear - they tend to draw in a lot of fresh elements as well as what was in the original brigades - I really wouldn't be throwing them into battle the turn they are formed

edit: just in case of confusion, the only Rifle Corps you can form before June 42 must be Gds, you can form Gds Cavalry from Dec 41 (so no problem there). But you can feasibly have the building blocks for a Gds Tank Corp or Gds Mech Corp before the relevant TOE is available. So all this rule does is to stop you building those 2 formations before the date they are available.

[Beethoven1]

ORIGINAL: loki100

ORIGINAL: Beethoven1

ORIGINAL: loki100

if you make it using the build screen, yes its clear, what status/TOE the formation will have. Realistically this only affects the Tank Corps (its very unlikely you'll have many mot brigades at Gds level before the Gds Mech corps can be formed). So since you can't build Tank Corps by on-map merger its pretty safe.

To make it using the build screen, wouldn't you have to send them to reserve? You generally would not want to do that if you can just form them on the map because you will lose CPP etc as well as time, as compared to simply forming them on the map and throwing them into a battle on the same turn they are formed.

well, worth stressing the obvious - tank brigades cannot be on the map so you can't construct a Tank Corps by combining on map (unlike say a Rifle Corps)

but no, they don't have to go to the reserve, just you do have to use the build screen.

At which stage I tend to refer to the manual and a table that took a fair bit of getting right:



given how tank corps appear - they tend to draw in a lot of fresh elements as well as what was in the original brigades - I really wouldn't be throwing them into battle the turn they are formed

edit: just in case of confusion, the only Rifle Corps you can form before June 42 must be Gds, you can form Gds Cavalry from Dec 41 (so no problem there). But you can feasibly have the building blocks for a Gds Tank Corp or Gds Mech Corp before the relevant TOE is available. So all this rule does is to stop you building those 2 formations before the date they are available.

Thanks Loki, I think I was confused by the patch notes wording of "if an appropriate guards OB is not available, the newly formed corps will not be a guards unit." I thought that meant that it wouldn't form a Gds Rifle Corps if you were over the percentage limits of Gds units allowed or something like that, as compared to the OOB not being available.

Also I was thinking about Gds rifle corps more so than mech/tank corps, because I have not formed a single mech/tank corps in the StB scenario due to the AFV losses being so high even in the previous patch, whereas I had formed quite a few rifle corps and Gds rifle corps.

[Darojax]

Is it safe to upgrade from 01.01.09 (stable) to this new beta patch, during an ongoing game?

[Joel Billings]

Yes.

[wkuh]

Finally have 01.01.15. Difficulty for me was registering or logging in to the download placard. Had assumed that being logged in to the game and the forum was enough.

Worth mentioning for others as that may be their problem as well.

[Hardradi]

I am not sure if it my old PC but I have had two crashes to Desktop with the new patch. One was at the end of the air phase and the other was on loading.

The game has always been pretty stable for me. I think it has only crashed twice before this.

[Joel Billings]

If you start experiencing non-repeatable crashes that others aren't, it may be a good idea to reinstall. We haven't had any reports of greater instability with the recent versions.

[Hardradi]

I had one more today. I will do a re-install.

Thanks for the advice.

[Beethoven1]

It randomly crashed just now for me also, I hadn't done anything right before other than clicking on the map (hadn't just been moving units or anything).

[dgrimes]

Two observations.

Ground combat with combat message at level 7 flashes by on screen. The combat message detail message no longer seems to matter for ground combat. It still works for air to air combat and bombing.

Second in locations where there have been multiple attacks you are no longer able to click through both attacks using the combat display. (This started occurring several beta versions ago.)

[Erik Rutins]

ORIGINAL: dgrimes
Second in locations where there have been multiple attacks you are no longer able to click through both attacks using the combat display. (This started occurring several beta versions ago.)

The UI for this changed with the scaling updates, but it's still possible.

[AlbertN]

Can Fortified Units be disbanded even if within 8 hexes from the enemy?
It seems the whole starting line east of Bessarabia disappeared in one of my games vs a player - and that was not because of Axis forces attacking it.

[MarkShot]

Your game is cursed, you met the poltergeist of FM Paulus!

[loki100]

ORIGINAL: AlbertN

Can Fortified Units be disbanded even if within 8 hexes from the enemy?
It seems the whole starting line east of Bessarabia disappeared in one of my games vs a player - and that was not because of Axis forces attacking it.

yes

but, as explained a few times, units that are low on TOE and/or low on morale/experience (& stacked alone) can simply collapse either in the logistics phase or if an enemy unit later moves adjacent to them

so a good way to deal with the Soviet fortified lines is to isolate them without combat and they will collapse - saves you CPP. Not always possible but worth trying to achieve

[AlbertN]

Hmm I did not wanted them to collapse admittedly, I wanted to use them as training grounds for my Romanians.
I have read of the collapse but I thought when they were isolated, not just because something went to picnic at 0 movement remaining adjacent to them, they dispersed!
I'd have gladly wasted Romanian CCPs in buckets for Romanian combat experience for the few units of worth they may have!

Though also other Fortified Units disappeared without being adjacent (The ones in the Pripet MArshes, not found them there) but I assume they did not started with 8 hexes of distance so they could be freely disbanded!

[loki100]

they can collapse when isolatd, as stated above.

I believe these are not then recorded in the lost unit chart due to the phase, if your opponent disbanded them then they are shown in the chart

so -- you can check

[MarkShot]

Possible bug: ACTIVATE AI AIR ASSIST does nothing on turn #1. So, if you delete anything, or clear out everything. There is no way to get it back. Works fine on follow on turns.

Thanks.

PS: Tested Road to Leningrad playing Germans vs AI

[Joel Billings]

Yes, the AI assist does nothing on turn 1 by design. This way it will not alter our scenario designed ADs for the first turn. I think we mention this in the rules, but I realize it's a big manual.

[MarkShot]

BUG

Joel,

About the SHFT-y thing. Check the rollover text, it says something about "flak" which is obviously wrong.

Thanks.

[Joel Billings]

Yes, just noticed that and mentioned it in my bug report on the "ground targets only" text over the last button. BTW, confirmed with Roger that this should be "Active Targets only" like in WitW (not sure why the manual changed). As for this issue with the rollover text, it's a bigger systemic issue. Click on one of the multi-step buttons like show recon. Then rollover another multi-state button (like show AD targets) and open up all the buttons and note the rollover text is from the prior button. It doesn't happen on 100% of the multi-state buttons, but it happens on several of them. Not sure how easy that will be to fix. For now you have to click on one of the buttons before the rollover for the complete set of buttons shifts over. Hope I didn't totally confuse you with this description.