@avnx Not yet. When did you message them? The support team is usually pretty quick about such things. Sorry for the delay.

@Woolies said in Mixture lever in 114TC not working: I use the default Axis 0-100% for mixture no problems I have apparently been using Mixture 1 Axis (-100 to 100) based on the bindings from the Bonanza that I copied for the Commander; an initial test showed that it seemed to work ok based on observed travel of the virtual lever and the engine running rough near cutoff, but I switched to Mixture 1 Axis (0 to 100) since the manual calls for the 0 to 100 values. I'll have to fix that next time I fly my other Black Square planes.

There's nothing to catch, it's an OS limitation and there is a well-known workaround: https://support.justflight.com/support/solutions/articles/17000153015-file-error-0x3-during-the-installation Many of us don't have that issue.

I think the way around this is to use custom install location with teh installer, which seems to default to a short folder structure of c:\justflight\product (paraphrasing). It also then creates a shortcut in your correct packages folder so this will just work, but I delete that shortcut and manually copy the folder from the c:\justflightfolder into my community folder because I dont want it to live on my C: drive.

Well if it was restricted it didn't seem to be affecting performance. I'll have to recheck

I'd really like to have the weather, best of luck on getting it in!

Yep, OAT and temp monitor fine and working for me.

I expect Just Flight to develop the Hawker Siddeley Trident series for MSFS 2020 and MSFS 2024, not JustTrains, okay?

@Fabbi I just checked, and I have applied the exact same fix to the 114. I've also done it for all my other aircraft for future updates.

@jrustyshaffer Did you reset the L:Var to zero when you release the button?

@Mark I'm personally not all concerned with different passenger configurations from cabin / visual perspective. I just want to be able to add a ZFW in simbrief for example that exceeds the default 100pax weight in the fokker f100 without breaking the aircraft loading logic, and for the fokker f70 (since many carriers used 80 seat configs in their F70 for example). Let me know if that makes sense

[image: 8191cde9-28c4-48ae-b250-3f03edfac157.jpg] I'm making good progress - have the CDU, RTU, MFD, and EICAS nearly fully functional (haven't messed with the brightness yet). This is my first attempt at coding buttons etc in air manager. I'll clean up the graphics later - just getting things functional for now. Question though - this is based on the RTU but I would assume applies to everything else. How are you handling the reversionary modes? It "seems" like what happens is you swap the display and buttons etc from the other unit?

@SinkRate I didn't mean to step on your toes. I don't know if there is any easy way for you to merge or take over my server... lmk as I'm hardly qualified to manage one

@Mad_X Im from Canada and was told by my IFR instructor to enter sids and stars manually into the 430/530. Though many of our sids and stars appear to say "RNAV1 or GNSS required". Regardless very good to know as I thought I was fine to accept RNAV 1 with many of these older GPS units. I assume it may have to do with pre-programmed fly over waypoints vs fly by waypoints?...

I also had visible lightning but no indication, sitting on ground at EGPC with live weather at 1835Z.

@venemair I experienced a combination of the poor ATS response, but more notably the crosswind issue just before landing using historic weather (Active Sky) on approach to 28L at EIDW. On first attempt I went around as was certainly not a stable approach. On 2nd attempt exactly the same issue, but carried on to land (not pretty) as was out of time for the evening! Because I was using ActiveSky for the weather injection I don't think this can be the system clock issue, but might be a corrupt weather file? As regards the ATS, I had this disengaged for the final approach, but find I keep fighting it as it turns itself on to protect speed. TBF, I think I was in the amber, but how do you tell the computer that it's within parameters for the approach? The correct flap setting was set with an approach speed of 141Kts which I was maintaining, so not really sure what I'm getting wrong if anything... I have done some good landings in the Fokker 100 (in fact some my best), but it does seem very inconsistent.

So, in FSUIPC I have the condition levers set in Axis as "Send to FS Preset". And the preset being "BS Starship Condition Lever 1 (2) Axis". No ranges or anything. Just like that. In the profile, they show up as: x=xU,256,F,PBS_Starship_Condition Lever 1 Axis,0,0,0,(star character)-1 -{ TO SIM: Preset Control }- x=xZ,256,F,PBS_Starship_Condition Lever 2 Axis,0,0,0,(star character)-1 -{ TO SIM: Preset Control }- Where the "x" will be different in your case. I also type (star character) instead of the actual character as the forum interprets it as Italic. But yes, I mean the Shift-8 sign to invert the movement.

@Mark now that I think about it, I meant to try a reinstall before posting. Will let you know if that solves the issue.