Feature requests
-
-
This is a small thing, but given that the gyros take over 30 mins to fully wind down:
I wish the engine shutdown in the turbine duke was more realistic.Both the deceleration of the turbine and the associated sound effects seem significantly sped up. (True on the TBM as well).
I wish that weren't the case. This is something that X-Plane and DCS seem to do well with their turbine simulations. -
If "better" state saving is added, then please add a few preset states to the tablet.
I like state saving right up until MSFS crashes or I am called away for an extended period and have to close the sim, which results in me spawning at an airfield in some Frankenstein flight configuration.
-
Where do you get state saving like that? Most planes only state save when you properly power down the plane and go out to the menu.
Either way, adding to the topic:
Some failures related to control surfaces. No point in doing a flight controls check if they cannot fail. Can be just a mild one without full control loss to not make it too deadly :D
-
@Tadeus72 said in Feature requests:
Where do you get state saving like that? Most planes only state save when you properly power down the plane and go out to the menu.
The Just Flight 146 does that. If I quit the flight or crash, it tries to load me into a half running plane when I load onto the tarmac next time, though fortunately they have a C&D button so it's not that big a deal.
The crashing isn't frequent but having to leave sometimes is.
-
-
@rjwalter This would normally be my preferred way of doing this, but the Duke is a special unfortunate exception, because I can't really come up with a way to do headphone jacks without completely obscuring the outside air temperature gauge. Ideas are always welcome!
-
@Black-Square There's an option for binding headphones simulation in MSFS but it doesn't work. Could it it possible to add such an option on the tablet ?
-
@Black-Square it could be just a click spot without the physical cables, like how the cows diamond does it.
-
@Black-Square It could be just silver metallic caps closing the holes of the sockets (maybe with the Black Square "B" logo on it, or engraved headphones). No protruding cables or so...
-
I would be totally fine with it just being a click spot without any graphical element. Or Asobo could finally fix the headphone mode hotkey assignment in the options after so many months :D
That saying, the inbuilt Asobo headphone mode is kind of ok-ish, headphone modes made for specific planes with their specific soundscapes work better in my experience.
-
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.)
