Daniel

Please iniBuilds, stop updating Sceneries with the MJT. It doesn't help forcing a non-Solution upon everyone.

Sounds great! I mean I hope for the MJT becoming some sorts of "SODE 2.0" for MSFS, I want it to be something great. I see agood Foundation, it just isn't there yet. So given that ini is already in Exchange with Umberto, you Guys need more Patience than I do 😅 Given that my Tool Any2GSX is 50% GSX and most of the Plugins for it are for iniBuilds Aircraft, just ping me if I can help anything 😉

I said breaking the Immersion, not the Game (the CTD seems to be fixed now). While its true that you can't see through some Jetways, there are more than enough "Glass-Jetways" or at least some form of fixed Glass-Bridge leading to Jetways where Passengers could be seen. Since there is technically no Jetway (in Terms of MSFS API) with the MJT, there is no "Path" for the Passengers. And its not only the visibility. Progressive (De)Boarding gets broken on Jetway Stands (since there is no Jetway). All Addons get broken because the MJT doesn't recognize the standard SimEvent to toggle the (at least one) Jetway, so for Example every EFB that uses that to call the Jetway runs into void. Deinstalling the MJT isn't a Solution (especially for Sceneries like OMDB) because then there is absolutely no Way to trigger anything Jetway-wise then. The Users are forced to install it to get at least anything going. There is a Problem, and it needs a Solution. In its current Form the MJT isn't that Solution unfortunately. Its just some custom Scenery Object existing isolated on their own which just happen to be called "Jetways". Maybe it would be supported by other Addons/Devs, but there is no API or Information published. Talking to the iniBuilds' Developers is impossible, at least that's my Experience as solo/freeware Developer, so working collaborative on a Solution seems not possible. Thanks, I'll try to find it. 👍

Is it possible (or planned) to disable Multi-Jetways and use the Scenery with only standard Jetways like before? (i.e. OMDB, EGLL) In its current form it is rather immersion breaking instead of benefiting the Experience (needing to do something manual for Jetways, Pax not visible). The GSX Compatibility is a far stretch when it is rather incompatible to every Addon expecting to control (at least one) Jetway via the standard SimEvent. Because the Multi-Jetways cannot be controlled externally through other Addons there is nothing someone could do about. So I'd rather go for Single-Standard-Jetways that are truly compatible.

Correction: forgot half of the Problem. It is not only that there is no Indication for the Dashed State, there isn't even a Variable to show the current Speed Value (i.e. the Knob is turned, Value is shown, but Aircraft is still in Profile/Nav). So maybe for a future Update, please add additional Variables to build more accurate Integrations (that would also help miniFCU / simpleFCU / custom-built-Hardware Users)

I trying to improve my PilotsDeck/StreamDeck Profiles (which are also shared to the public) with a more accurate MCU. But, could not figure out yet how to replicate the Dashed State (---) correctly. I'm trying with 'FMGS_vertical_mode' and 'INI_MCU_PROFILE_LIGHT' (for the SPD Value) but that does not work out in all Situations. Would be nice if a Dev could share some pseudo-code and Variables Values how to correctly test for the Dashed-State (and in the long-term it would be a nice Idea to just export that to a L-Var - e.g. like on the FBW or Fenix)

I like the Quality of the Sounds, but the overall Mixing of them isn't just very pleasant. Either it is load-af or whisper-quiet

Yeah, the notice that this is known and will be fixed certainly helps, thanks 🙂 I don't have a Problem with the Smoking Switch, that works (for itself) still as expected. I just wanted to add that moving that Smoking Switch (via its L-Var) also changes the L-Var INI_EMER_EXIT_LIGHTS_ON . 😉

There are several Issues - maybe with the Plane, but maybe me just not knowing how the right Behavior should be: I start in Cold & Dark and apply Power to the Airplane (BATs + EXT), and don't see the "Disarm" Indication lit up for the Emergency Exits (with the Switch being in the Off Position). Is that really what it should be? 🤔 (That wasn't the case before 1.0.3) Regardless of that: how is one supposed to read if that Indication Light is on or not? Can't find a L-Var for that 😕 (Before 1.0.3 I could read it via INI_EMER_EXIT_LIGHTS_ON which now turns 1 when the Switch is in the On-Position. It makes totally Sense that a Variable called ...ON reflects the ON State ^^ It is just that there is now no Way to get that Disarm Indication) And speaking of that L-Var: Is it supposed be 1 when the No Smoking Switch is in the Auto Position?! (Freight Variant)

Sorry, only English!

I don't use MF, but when I remember there was some kind of Way to run Code in the Background which then could output to something like a "MobiFlight Variable" - which could then used in the Display Logic. But yeah, a native Variable would definitively reduce the Work! Let alone since sometimes the Display will not immediately go to Dashed (although the vertical_mode changed). I mean ... besides that I still don't know if I really caught all Cases 😅

Yes, of course - that it what I do everytime I need a new List. That is why I wished FSUIPC could also output that directly to File. I assume you want to try to be helpful, which is great. But please do read properly what was written before attempting 😉

And now show me the resulting File please which was written by FSUIPC?

Check out the FMGS_vertical_mode L-Var - with that an others you can rebuild the Logic when to show Dashes instead of a Value! You can use my Lua-Scripts from my StreamDeck/PilotsDeck Profile as Reference if you like: https://flightsim.to/file/67263/pilotsdeck-streamdeck-profile-for-inibuilds-a300

Well, I had one Occasion where GSX crashed in the middle of the Push-Back. But it self recovered (worked without Issue on Departure), the Plane was also fine after that. Apart from that I had also zero Issues.