Items that should be adressed (feedback after several flights)
-
Ta-da, and now I can manage W&B without the toolbar W&B panel :)
-
@knidarkness very nice to have ;-)
-
Quick reply direct from Nick at Black Square, mainly for @knidarkness
'Thank you all for your contributions here. Clearly, a web designer is exactly what it takes to make this interface a reality! I would be delighted to work on this together (I believe you've been in touch with Just Flight on my behalf), but I will provide a warning out of an abundance of caution. When it comes to an aircraft as complex as mine, there can be cascades of unintended consequences when making modifications like this. For instance (though I'm sure you already thought of this), simply toggling the doors with the native commands does not lock/unlock them, which may confuse the pressurization system. Nearly every system in my aircraft has some caveat like this, some more severe than others. I am happy to put significant time into achieving a goal like this, but I thought I should offer fair warning that it's not always as easy as it may seem. I would look forward to the opportunity, though!'
-
@voice-of-reason Thanks for relaying it back and to Nick for taking a look at it!
The warning is absolutely fair! It would be great to make this addition as this is quite nice QoL feature for products I thoroughly enjoy. For the fuel and payload -- you seem to be using the default simvars for tanks & payload stations, so that seems to work fine.
For the more complex "flows" so far I've been looking into the (IIRC)
interior.xml(or whatever is the filename that matches "clickspots" with proper events) and replicating the flow via the JS code (by calling theKevebts and/orLvarsas it is defined in the xml) with some delay between actions to allow for animations/internal state change. That seems to work for the doors at least, and I'd imagine should work for other stuff as that's (at least in the eyes of the sim) they way user would interact with the plane?As for the failures (which is ultimately something that's IMHO is very beneficial and at the same time most complex to properly integrate) -- probably the "simplest" way (as of now -- mostly guess) would be to have the triggering logic in the EFB/tablet/etc, and whenever we want a new fault to occur -- send custom event (or at worst change LVAR) that can be intercepted in the current codebase and set in the
activeFailuresListThis would allow to add more complex triggers (e.g. altitude, IAS, additional exceedances and so on) without completely overhauling (or overriding) existing codebase.For the immediate future (most likely in the end of this week, when I once again will have more free time, or at the latest the one after it) I'll spend a few more hours improving the WXR "fake-efb" and try to publish to flightsim[.]to.
The only question I don't have an answer to with it regard is how to make it into a mod without violating the license of the product -- because as of now I modify the
bksq_wradar1.jswhich is a part of a product, and hence can't be redistributed.I guess the "least bad" option would be to do a diff of two files and somehow merge them on user's machine (be it by python script or manually via online tool). But ultimately, having an HTML gauge that one can "harmlessly" override (i.e. tablet/notebook/something in VCockpit) would help with this aspect as well. And indeed simply having more space and not needing to rely on the WXR for "EFB screen" would be ideal.
-
@knidarkness Can you please drop me an email and I'll get you connected to Nick at Black Square.
Email me at scott.phillips@justflight.com
Thanks.
-
@voice-of-reason done!
-
Can someone explain why I am getting a
"TQ Exceedance 2472.8" warning when I'm at 95 percent TQ and 2000 rpm and in 850 Mode ?
All temps are within limits.
Thnx.
EDIT: Sussed it: It's 121 % of 200 RPM in 850 mode. It's quite easy to exceed it.
=================
P.S. Any chance of the Lvar for toggling 850 mode ?