MSFS Products

Hi folks, I notice on the APU panel in FS2024, when you shut the APU down, the RPM and TGT both spool down slowly. Of course, I don't have access to real a/c as JF do (and Ryan, who is very helpful on these forums), but my understanding, purely from footage I've watched, is that the APU doesn't really spool down so much as shut straight off, and both gauges simply flick straight to nought (always struck me as odd on the 146, that). This is certainly the case (and simulated) in the JF 146. Is this different on the RJ IRL? Or is this a bit of a bug/sim-ism?

@Black-Square said in CDU and MFD buttons bug when assigned in axis and ohs: What events are you using for those interactions in Axis and Ohs? I assume the ones at the end of my manual in the Inputs/Outputs section? Well.. not really. I was looking to map the letter CDU buttons (1ABC, 2DEF etc) but I don't see those in the manual, only the line select so I downloaded a profile where the letters supposedly worked on a winwing MCDU but I don't have one so I tried re-mapping them to the virpil push buttons. For example, the profile uses H:CDU_3Button_1 for 3DEF button but when I remap it, nothing happens when pressed.

Managed to get on before leaving. Did a proper reinstall still the same. Convinced it was something in my settings. Had a look around and not one of my switches wasn’t in the same position as usual. Flicked that to the normal position and bingo. It was mapped to ‘toggle engine 1 fuel value‘. Removed the binding so won’t happen again. Once again thanks for your reply. It made me do more digging.

https://community.justflight.com/topic/8933/state-saving-in-the-a36-doesn-t-work

I think it must be the navdata for that particular airport. Possibly the third party addon messing with it. When I tried a different airport (KSRQ) it worked just fine. The SID from KATL also worked just fine in both flight plans.

Yeah would be very nice to get the amazing 146 into 2024 for sure ... I fear that the F70/100 will be ahead of getting the 146 moved up. Hopefully some news soon

I was having similar issues, but I think I fixed them with settings. I already had aircraft traffic quantity and parked a/c quantitiy to none, but there's another setting called "characters quantity". I have no idea what that is, but turning that off too seemed to fix it. Now I load into a major airport and there's traffic all over. With "characters quantity" on I was getting either no traffic, or like a single plane. Just posting this in case it helps anyone else out.

Typically, behaviour such as this will be related to a control assignment conflict. An easy way to confirm if this is the case is to unplug all your external hardware (Joystick, Throttle Quadrant, etc.) and then take off using only the mouse and keyboard. If the landing gear/hydraulic issue no longer exists with just the keyboard and mouse plugged in, then it is likely a control conflict with your other hardware. If this behaviour persists, could I kindly ask you to raise a ticket with Just Flight Support via the following link and one of our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

Oh wow - I totally missed the fuel auto-switch option in the EFB Thanks for following up - will wait an see if the lights come good with the next few MSFS updates.

@Delta558 No worries, have fun! I investigated it a bit further in the meantime. The trim tab seems to have a lot more impact on the overall lift coefficient than the elevator itself - which is odd to me. I tried to map my joystick to the trim axis and the trim to the elevator axis and that actually gave me realistic control over it in slow flight (looks very funny to steer that thing but only the trim tab moves). Can you try landing that thing without trimming it, because that seems to be the core of my problem - i.e. without trim, no slow flight possible because elevator alone cannot create enough lift with that low power setting.