Feature requests
-
I'm adding a +1 for expanded state saving options. Default behaviour can be as it is now, with extra features toggle-able by the user (to save a few support headaches). It may mean working around sim limitations as I'm aware it uses the sim's own state-saving feature.
Adding more would bring so much more to the shutdown procedure, in terms of how you find the aircraft on the next flight. To me it's almost as valuable as the realistic start up, requiring proper procedures. Finding most elements in perfectly consistent configuration on each flight is a small detractor in simming (for me).
Headphone mode would be great too. I generally enjoy listening to the sound of my virtual engines, but with the Comanche it's a joy to be able to soften the sounds (engine + significant wind noise) with a single click.
-
I would agree to all state savings ideas. It's mandatory. Maybe some dev can elaborate why they only save a few things. I wish the same implemented for every black square product.
That topic is the only reason I registered to this forum to push this brilliant idea. -
M Mustang referenced this topic on
-
Another idea that would be very welcome: Expanded information on some of the in-sim checklist items. You may have seen this on other aircraft. When you select an in-sim checklist item, the bottom of the windows gives some additional context for why the highlighted row of the checklist is done, what to look for, or what to do if the check fails.
This wouldn't be needed for every item, of course, just the ones which are not so self-explanatory.
As an example, here's part of the checklist .xml file for a community-made DC-6 checklist I downloaded. The extra info is added with the "clue" element, as in this example:
<Checkpoint> <Clue name="Check door indication lights above att. pilot"/> <CheckpointDesc SubjectTT="Doors closed" ExpectationTT=" Checked"/> <Instrument Id="dc6_251_obj"/> <Instrument Id="dc6_253_obj"/> </Checkpoint>So rather than the checklist simply calling for "Doors closed: Checked", it tells you specifically where you can look for a warning light, other than physically checking the doors which would be the obvious thing to look for. (An alternative would be for the checklist to call for "Door warning lights: Checked off" but you get my point.)
-
Add my vote to this.
Better state saving would take this product to the next level. I want to be able to pick up my Duke the way I left it.
This is an area where A2A rocks. In the Comanche, literally everything will be as you last left it. Every switch, button, dial.
For me, it's a little immersion breaking to shut down my Duke, have the props feathered, fuel selectors off, all my light intensities exactly how I like them, only to have them reset for the next flight.
Interestingly, I don't think the Comanche relies on having to escape to the Main menu to trigger state saving. Not sure how they do it, but with the instability of MSFS (for me), more often than not, nothing in the Duke gets saved because the app crashes or freezes. The Comanche? Somehow everything gets saved, even if the app crashes.
I'd also love to see things like oil consumption and brake wear. I love that in the Comanche I can actually walk around, pull out the oil dipstick, and see the quantity and quality degrade over time.
Just my two cents.
-
-
Plus one on the state saving.. Especially light settings and fuel state is driving me nuts.
apart from that, a windshield fogging simulation would be cool, especially as the cabin temp is so well modeled.
Not only if could fog from the inside, but also on the outside if you descend with a cold soaked windshield into warm, moistureous air. It will soon become a habit to turn on the windshield heat before the descend.. -
Add me to the list of state savings but comparing it to the Comanches state savings might not be the best bc Accusim runs outside of the sim where BS runs inside so they might be limited to what can be done.
Further down the road, It would be nice to have oil management available. The need to change the oil & filters and planes burn oil so oil levels as well as the already included oil coloring to show age/usage. If this is already available, I havent gotten that far to discover it yet so just going off of the tutorial/intro videos.
Out of the gate I'm loving everything about both versions and am starting to dive into memorizing the key parts of the Dukes that a RL plane owner would know or want to know without looking it up.
-
Another couple of small ideas that might be easy to implement in a future update:
- Add the total payload value on the tablet
- Allow more granular changes on the weights (both fuel + payload)
I often fly cargo with Air Hauler 2 and it's useful to be able to see my total payload so I don't have to add up all the weights in each seat. Being able to set it more precisely would be nice, but not essential.
-
Hey all. I'd like to second the requests for custom headphone / noise canceling simulation. I like the ideas mentioned to avoid blocking the OAT gauge. I'd like custom sounds though because the default method leads to a really annoying sound imo with the turbine duke.
My main addition to this thread though is to request a clickspot to hide the throttle/prop/condition levers. The 414 has this and with the Duke it would make it much easier to read the oil gauges. As is I have to slew the camera to check the right oil gauge (in the turbine) which is a bit annoying.
-
@lucaseowen said in Feature requests:
clickspot to hide the throttle/prop/condition levers
Click below the propeller levers, above the autopilot panel :)
-
@Black-Square Amazing! Thanks for the response!
-
Wondering if the in game navigraph app could be added to the tablet in the duke. I use my plates a lot on the GTN750 and I also have the navigraph window minimized usually to use in the sim but I think it would be cool to have the Navigraph app on the tablet. I know the HPG H145 has implemented this it would also be nice to see an active checklist similar to the one that is used in the Hotstart Challenger for Xplane.
-
Copied from somewhere else I posted about this recently:
As for Navigraph, I had a conversation with them at Flight Sim Expo this summer. I was expecting that they would have a generic interface package to make integration with EFB's easy, but I was surprised to discover that they do not. Instead, every EFB developer must create their own Navigraph interface that takes user input, requests the documents from their server, and displays them to the user. While this is not something completely outside of my talents, it's not over the bullseye either. It's something on my radar, but I don't want to make any promises.
