JWE
Posts: 6580
Joined: 7/19/2005
Status: offline
|
quote:
ORIGINAL: AlaskanWarrior
It appears that a non-squad device load cost also equals its troop count. Why is this so?
Not quite true, load cost is not troop count: and because that is how the game engine works. A non-squad device will load according to WHAT it is (gun, vehicle, afv) and HOW BIG its LC numeric is (<5, or <9, or >10, or something like that, I forget, offhand) and they load into cargo at 2x or 3x (respectively) their LC numeric.
quote:
With severe personnel limits on small island bases I find it hard to believe, as an example, that a company of lights tanks, 14 Vickers Tankettes and 12 support squads, would equal well over 500 personnel. For stock the figures are 15 LP for Mot Support and 20 LP for Tankettes. Historically the figure would be roughly 14 thanks and 2 support squads with maybe 40 people max. Two per tankette and 12 man support.
Because of how the game engine works, one must have enough Sup to host their combat units. If you have a unit with 50 tanks, you will REQUIRE 40-45 Sup to keep them reasonably running and relatively combat effective. That's just the way the game works. Cannot (will not) be changed.
The "stock" paradigm is to list AFVs, etc, LCs according to their weight, but since LC is also expressed as troop count, this does tend to skew LCU values.
DaBabes recognizes these imperatives, and has done several things to minimize the negative impact.
1) remove all the useless halftracks and other vehicles that have no substantial utility, but consume Sup.
2) aggregate AFV devices into groups of 2 or 3, thereby reducing the Sup requirement.
3) redefine the LC for an aggregate AFV or vehicle in terms of its crew size and a weighted proportion of weight.
i.e., a Stuart don't take up more room than a 3/4 ton weapons carrier, and a Sherman ain't that much bigger than a deuce & a half. Weight is not an issue, it is footprint. Since the engine treats AFVs as 3x their numeric (in terms of LC), it's not hard to figure out. We have a calculation methodology that seems to work just fine.
Cutting the number of AFVs in half (or thirds) is not a big deal, since a smaller number of devices get to shoot at a proportionally smaller number of devices. We did the same thing (but multiplied by 2 or 3) with other devices that have dinky LCs, but require Sup in proportion; mostly AAMG kinda stuff.
So, DaBabes has troop counts that are much closer to reality, while accommodating the load algorithm. It's a 4 way matrix, and a real bitch to keep straight, but should be copacetic.
|
Printable Version
Device load cost and troop counts - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread