Mr. Colin "krazycolin,"
Please consider the following as requests to answer the question that you posed here:
Please define what you mean by "A2A Accu-sim" like features...
Accu-Sim features that I'm interested in are...
1. The weight of the aircraft: changes with different payloads, ordinances, etc. and the all wheel hydralics systems reflect it as well (CaptainSim's XLoad F-18D is a rather extreme example but none the less leaning to being more accurate in visual representation as payloads are added on the wings, the aircraft "tips" to meet gravity). Therefore, due to these added payloads, it flies and taxi's differently, too. The takeoff role is extended, the number of G's one can pull in a bank is different and the overall behavior between both versions (C & E) varies - they are NOT the same plane; so, the model(s) should reflect that. Also, Aerial-refueling, with correct changes in flight behavior as the number of pounds of fuel is added to the aircraft would be "Features for Accu-Sim".
2. Actual Sounds features: with proper use of FSX's 3D surround Sound Cone should increase the immersion factor. When flying this model, the "Sim-Pilot" should have some
semblance of "believability" - So, if a button is pushed or a switch is clicked, you hear some (if not all) of those little indications audibly, which you would in the actual aircraft while it is parked on the ground, for instance. Amoungst others types of sounds would be the Pilot breathing, VMS - Callouts, announciator alerts, etc.
3. Engine "ware and tear": is a feature of A2A's Accusim and that means that you have to fly the aircraft to more accurate specifications. With a Jet like this there are fewer restrictions with its flight envelope and maintaince is done regularly so that is NOT necessarily a requirement here. However, it would be nice to have changes in Engine performance with altitude and temperature, icing and Rain water (due to flying in heavily numbus clouds), or stall induced charactistics. And the actual use of instruments to indicate that (VC gauges or MFD management and warnings for N1 and N2, FUEL, STALLS, equiptment failures, etc.)
4. System Management of flight/Life essentials: eg. Oxygen systems, in the A2A P-47, if you go above 10,000 ft. or higher and you're not wearing your mask or turn the O2 flow, you'll take a long nap and might NOT recover. Also, Pitot heat management in known Icing or if dirt were to enter the tube from "NAP-of-the-earth" flying or a bomb drop, etc.
These are generally the kind of things that makes the "Sim" experience more lively, interesting, fun, and most importantly - durable for the user (i.e. one doesn't get bored easily or mentally fatigued because there is so much book work and little to no enjoyment).
Here are other things that some users have already mentioned but I'd like to add a litte more to what was written:
1. Menu system that permits adding/removing components for these "eye candy" features. Like, Pilot Glasses ON/OFF, protector labels and chocks ON/OFF, and FOD covers.
2.Ordinance management within the VC (with MFD's that reflect a jettison or release (changing loadouts) of a weapon or fuel tank for FUEL/Weight calculations for TOF/ETA/TMZ, etc. and realism within the cockpit. Later, these features could be made to work with this...
FSWeapons : http://www.sim-outhouse.com/sohforums/showthread.php?t=17341
[YOUTUBE]nqPPEEqLEDo&fmt=18[/YOUTUBE]
This is NOT, currently, possible for a commercial product. But, it wouldn't hurt to co-ordinate your efforts with this developer. Since, Military Aircraft are a major product line of FSD/MilViz and almost all Fighters do these kind of activities.
3. Navigation: Creation of flight plans within the VC with the ability to make modifications to waypoints "bulleyes" and perhaps use actual GPS (with TACAN & MLS/ILS) capabilities with NON-FSX DEFAULT GPS'.
4. MP capability: REAR (RIO) VC (E version) MP cockpit capability is essential. This is where the #3 suggestion (above) comes into to play. The Fuel management, Navigational management, and Limited ordinance and weight management could be managed by the RIO, while the pilot has the responsibility of "Aviate, Communicate, & Navigate" to the intended objective. This permits at MP crew situation, a great feature of FSX that hasn't been fully exploited for fighters, so far.
Don't get me wrong here cause I am just asking. I wish to understand more about what it is that you are looking for? As I understand Accu-sim, it's designed around treating your engines/plane correctly. Otherwise, it will breakdown and stop working. Plus all the extra sounds... Am I mistaken?
... We do know that we can easily do CCIP in a variety of ways plus we might be using Phlerp's systems should it be ready by then.
We actually do have the same guy who did the HUD in the F-16 working on the HUD and possibly the MFD's and PFD for the E version. The C version will more than likely use the standard F-18C HUD as they are/were, in real life, pretty much the same system.
You've already mentioned CCIP implementations (perhaps within Missions) and startup proceedures. That would be a MUST for the E version and the A-A features for the C as perscribed by their roles. I understand the limitations and look forward to what you'll come up with. These are merely suggestions and perhaps "hopes" for you to consider. Keep in mind that there are users that own the IRIS or FREEWARE F-15's for FSX and those are similar in behavior to what most FSX military aircraft behave like (i.e. stock .air files, etc). That is why, I'm requesting these features. I already own those, why would I need to buy another that is little to no different. Please understand my goal is realism, usability, fun, and longevity with the use of FSD's products. It doesn't have to be a "400 page manual" product, but should require a little bit of a "learning curve" for it to be useful. Or, it won't take too long to get bored and, my thinking of it, to consider it to be "too expensive" for nothing more over the other models out there.
I have a suggestion: I will mail the F-15 Manuals (C and E) to anyone who wishes to participate in making a list of things that are must have, should have and could have... We will then collate this list and try for that...
We really do wish it to be as cool as possible. Really... So your assistance would be invaluable. Any ideas about systems and their implementation would be more than welcome.
Contact me at
colin@milviz.com or by PM here.
Thank you for the compliments. I will be doing a vid of the pit in the coming days/weeks...
Please feel free to send me what ever manuals you would like as I would very much like to make requests of features that might be possible. And, I look forward to your video(s).
Thank you for your consideration.
PS: Mr. Fred Highland "Horten229", is a professional developer who has fixed several issues with the Aerosoft F-16's HUD (from the "HUD erractic bouncing" to missing elements). I'm sure that he could be of great help to your developer in resolving these issues with the new model. I've noticed those similar issues in previous HUD versions that I also own, that is "why" I've mentioned it and NOT as a bash.
