From: Boston, Mass
Other than the tedium of creating new graphics, and a full research tree for new units, it's very straight forward to create new simple units. THANKS to everyone who's written anything about unit and scenario creation.
ON the other hand, some capabilites seem to be hard coded nto the engine. For instance, I'd like to model a GLIDER that is capable of thransporting non-airborne units to remote part of the front. IDEALLY, it would be an airdroppable container from a transport, that held non-airdrop units (Mg, bazooka, you get the idea). Even better if it could hold more than it weighed, since it provided it own lift, ala a dc-3 towing 2 gliders.
On the other hand, I'd setting for a self-destructing transport unit, that could travel like a rocket or kamikaze, to any location within range, and just left its cargo at the spot it landed; I can do that, but only with airdrop units, and the entire goal is NOT to create a replicate unit tree of airdrop units (which is how I got started in this anyway). By giving it a higher fuel consumtion and longer range, one can infer the use of a tow plane, and some extended glide range. The problems seem to be that only cargo ships and transports are programmed to "contain" other SF's, and once a non-airdrop unit is in the SF (eg a JEEP), the transport will only go to another airbase. Ships can unload anywhere, but that seems to be an inherent property, not a statistics screen value that can be granted to another unit type.
Has anyone attempted anythng like this yet, and if so how.
Does anyone have an idea if this is even possible, or is it internal to the engine (VIC ??)? If possbile, any ideas on how to apporaoch it??