From: Hansville, WA, USA
I found that the EC-135 (and variants: EC-135E, EC-135H, etc) has been logged as a possible addition to the database. As above, priority is the issue.
Just as an FYI for all who submit change requests, as items come in they are prioritized kind of along the lines of:
* Is it critical to the simulation operation - this air unit seems only to fly 100nm before running out of fuel.
* Cosmetic - I would like the menu color for this item to be day-glow pink instead of purple (stuff really happens).
* This new unit (ship, aircraft, sub) has been announced by (name your nation) and should be added.
* The A-6E was really modified to carry AGM-84E's in 1991 for the Gulf War and not in 1992.
* Nice to have feature but low priority.
* Not happening - I would really like to see the SR-71 modified to carry nuclear weapons.
You get the idea. Some need immediate action, others not so much. I was recently brought on board to assist the main DB guy in entering change requests and doing research. The more background information submitted by the requester means a higher likelihood of it happening. (Sorry, no nukes for the SR-71)!
When it comes to changing something such as the A-6E/AGM-84E item there are several steps:
* The new loadout must be added (short and maybe long range versions).
* Does it affect the number of hard points available for other weapons.
* The correct aircraft sensors must be included specifying search arcs.
* The correct (if any) datalinks between the aircraft and weapon must be added.
* Check for changes (if any) to fuel consumption, attack ranges and other flight characteristics.
* Update subsequent A-6E (1991+) models as needed.
* Run the entire database validation check for errors (weapons, mounts, sensors, magazines, loadouts, etc). Oops, forgot to include another sensor/datalink to the A-6 and/or specify an associated arc.
* A sensor can only be used during the day and you've said it is good for day/night, all weather.
* Repeat and re-validate.
* Once error free, convert the database file to a .db3 file for subsequent release to the community.
All that to make a relatively small change to an existing platform! Frustratingly, an anticipated 15 minute change can grow to several hours. Adding a new unit, say a nuclear capable Cessna, is a little more involved!
For quite a while there was only one guy doing all this for the DB3K database in addition to other CMANO related things. So, now I am in the fold assisting with the work - which I enjoy.
All the above is just to outline why a suggested change will probably not be accomplished immediately. Database modifications are constantly being done but you generally won't see them until the next major CMANO version release. Or, in the case of our nuclear loadout for the SR-71, not at all!
“There is no limit to what a man can do so long as he does not care a straw who gets the credit for it.”
Charles Edward Montague, English novelist and essayist
~Disenchantment, ch. 15 (1922)