Hi Mark..., I've checked the navigraph hub and I confirmed the settings/installation of the 2601 cycle. Nav data is installed in: C:\Users\RobSy\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\justflight-aircraft-rj\work\JustFlight\navdata Since I'm running MSFS 2020, v1.5 of the RJ is not applicable....? All I can think of now is to completely uninstall/reinstall the RJ...? Rob

Just to double check, there are two separate settings in the menu, "Crash Damage", and "Aircraft Stress Damage". Do you have both disabled? I think it's only the stress damage setting that actually needs to be off to avoid the "open door = instant crash 'feature'" of MSFS.

Glad to hear that you're enjoying the Bonanza. I recently found that I missed including the vent variables in the temperature simulation, so currently they only influence the rate of temperature equalization if you are not actively heating or cooling the cabin. I'll fix this for the next update. You are also correct that the door seals only serve to reduce noise in the unpressurized Turbine Bonanza. Let me know if you have any more questions! You know where to find me.

@kityatyi Thank you so much for sharing. I derive great pleasure from knowing that there are many who enjoy my aircraft the way they were intended to be. Indeed, there is absolutely a King Air in the works, and you will start to see more details soon

You are correct that both the knob and the switch should be actuated to hear the identifier in the real aircraft, but there is no convenient way for me to simulate this in an aircraft that also makes use of third party GPS systems. In other words, I could accomplish this myself, but since other GPS units already make use of the default NAV IDENT variable, there is no way for me to override their behavior, or at least not in an intuitive way.

@Black-Square I'm still working on my Bonanza Pro Streamdeck buttons. I created a SPAD event that tests most of the circuit breaker conditions and changes the button color from green to red when any of the breakers are tripped, and from red to green when they are reset. I found the Vars for all of them except: Aux Fuel Pump Vent Blowers Air Cond Air Cond Blower STBY Gyro Here's what I see when I look at the Aux Fuel Pump. I can find the 'A:Circuit Connection On:4' variable, but it doesn't respond when I manually trip the breaker. I'm not sure SPAD can control A-Vars. Any help figuring this out is appreciated. [image: f8fb2e6a-99f7-42d0-8f52-e85ba19d2f35.png]

@alanrco said in RJ and the Airbus controller: There are two 'gear up/gear down options but cannot be used because the AB stick is only one button operation. The controller gear stick works on all my other planes exept the PMDG 737 because it has 3 position - raise and secure and lower. Maybe any future patch could resolve this? Regards, Alan I've no idea which position on that throttle results in a button press because I don't own it, but bind whichever position does it to its relevant Gear option (up for up, vice versa). Make sure that Input Repetition is off. Then bind the same button for the opposite Gear option, then select the On Release option. That's how I do my Thrustmaster Boeing yoke (Gear up is the button press for that), and I can even move the PMDG gear lever into Off after it is raised.

@dukman821 No, at the very least the game must be ended normally through the main menu in order for state saving to work. The state is not saved until you quit. If you directly exit to the desktop via the Stop button Steam, Alt-F4, or some other means that's not backing out to the main menu gracefully, it won't work. This is true of every add-on with state saving that I'm aware of.

After doing some additional tests, it appears that only certain items save state properly for the instance. The following ARE set back to the way they were (ie works properly) when I closed the flight and reloaded it: Battery and Alt Switches Fuel Pump Switch Landing Light Switch Anti Collision Light Switch Pitot Heat Avionics Master Switch Transponder state switch - Off, Stby, On, Alt, Tst Fan Speed - Hi, Off, Low The following are NOT saving and are reverting back to their default: Transponder Code - It resets to 7000 normally, but sometimes 2000 or 7004, which is odd. Throttle - It would reset to fully closed (ie fully down) Mixture - It would reset to cutoff (ie fully down) Parking Brake Switch - It resets to ON Carb Heat Switch - It resets to OFF Comm 1 and Comm 2 Frequency - Each resets to 124.850 for both active and standby. Nav 1 and Nav 2 Frequency - Each resets to 110.50 (Active) and 113.90 (Standby) Altimeter Setting Nav/GPS switch next to the Nav 2 VOR Note 1: If it wasn't listed above as saving or not saving, I didn't test to see if its state saved or not. Note 2: During each test I am using the save livery / tail number. Note 3: It appears using End Flight or Main Menu to exit out of the active flight works when restarting. I also tested exiting out of MSFS 2024 and reloading, and it appeared to work but I didn't test multiple state changes for that. The aircraft is setup as follows in the EFB: Auto Fuel Selector - Disabled (Black background) GPS: WT GNS DUAL - Enabled (Light gray background) State Saving - Enabled (Light gray background) HSI - Enabled (Black background)

I made sure my Network connection is not blocking this and it is not. I set it as a specific allowed sie but no difference. I can get the the main OpenTopoMap.org site via browser.

I think this is the well-known MSFS24 problem with turbulence settings in conjunction with terrain and real weather (wind changes of 30kts or more in less than a second, perhaps poorly simulated windshear-stuff or updrafts/downdrafts). There is also some discussion about this in the MSFS forums. I experienced this myself last week in Nuuk (BGGH, RWY22). For several hours (under real weather conditions), there was a repeatable effect where ANY aircraft would simply drop like a stone about 200 meters before touchdown because all lift was completely gone in a fraction of a second. This could only be fixed with turbulence set to medium or low. I suppose, because Starship's front wing stalls first, the aircraft goes hard nose down.

[image: 52160b1a-9f73-48d0-b7b1-6d5dcc4c1963.png] This is what I getting as the map.

Well, you learn something everyday. Makes sense. Thanks for replying.

Hello, I'm an enthusiastic BAe146 and RJ Professional user with MSFS2024 and Xbox. Unfortunately, both products still have their weaknesses: The RJ can finally be loaded onto the gate, but, for example, with the RJ in the Shopping Swiss livery, all the buttons and controls/displays are misconfigured. I flew on several different A146-100, A146-200, and A146-300 aircraft today. Some of them displayed the red WASM warning cards again after boarding. On one occasion, as with the RJ, all the buttons were misaligned. I believe this WASM issue is still ongoing. Please take a look at it. Thank you very much, as it's a wonderfully sophisticated product.

@Black-Square Disabling AI Trim helped. The noise is gone. I also had the noise in the Piston and the Grand Duke; it seems to affect all BlackSquare aircraft.

@capebud1 I’m assuming this is in FS24? The beacons are definitely working – but it has to be sufficiently dark. [image: a03cae7b-1bd2-4211-8197-91c97a4d1bc9.png] It has been reported since the release of FS24, that the exterior lights are too dim in daylight. Here’s a link to the official forum discussing the problem. I’m guessing, that’s what causing problems for you. Same thing with nav and strobe lights, with or without winglets, they’re also working – if it’s dark enough. At least for me.

It's looking like a TDS issue, there's a beta fix available on their discord, in case anyone else ends up at this post looking for something similar.

Thank you for your reply, but not what I'm looking for. I'm talking about things like RNP AR, LPV and RF-leg capability etc. The kind of info you need in order to figure out if a certain RNP approach is allowed or not. Operator approval is also a factor, but that's going to vary from airline to airline.

@Mark, Many thanks for getting back to me. The only odd thing is the entry lights. When you start the APU or connect the GPU in the dark, the cockpit is illuminated well as the panel flood (X2) and console flood are all lit - making the entry lights a bit pointless. Also, if you switch the entry lights on using either of the cockpit switches - it also turns on the entry lights in the galley - but the galley entry light switch then has no impact. If entry lights are off in the cockpit then the galley switch turns the galley entry lighting on/off as expected. Just seems a bit illogical to me, however, maybe that's how it works on the real aircraft. Regards, Neil.