What's so
smart about having to wait a year (best case scenario) for ALL your tanks to upgrade to a new chassis then wait another year to wait for the guns.
That's
stupid .
It's like the Germans first fielding only the Tiger chassis and then 1 year later the Tiger gun. That's smart?? Yeah,smart as Halo.
At least they could program the upgrade system as a "pipeline" that seeks to upgrade all components of one brigade before moving to the next in the queue.
Sure,it's a far cry from each component having its own upgrade "progress bar",thus allowing for any component that
can be upgraded to
be upgraded
as soon as possible rather than wait for the first component to be done.
EDIT :
I'm sorry,but I just have to get this out of my system.
I'm not some guru programmer,but I know a thing or two about software engineering. And one of the things drilled into my head in college was "patterns".
So my question is :
If the "pattern" of "independent, parallel upgrading of thingies whose attributes increase" can work in HOI2 where the "thingies" were divisions, why can't this parallelism be imported for components?
If divisions in HOI2 and brigades in HOI3 are entities whose attributes increase
in a parallel and independent manner of one another they
each upgrade at their own pace , why force a linear,sequential (instead of parallel) upgrade system for the most basic "attribute growth thingie",the brigade component?
If the upgrade queue has something like "Brigade X upgrades component Y to model Z" then why can't the next parallel,independent entry be "Brigade X (same bde) upgrades component Y2 to model Z" as well? Why can't one brigade upgrade multiple components at the same time?
I don't care about synchronization (though that would be nice and downright necessary if a new gun needs a new chassis), but really,why can't the very system that worked so well on divisions in HOI2 be applied to brigade components?