@fenthanyl It's a good suggestion, but the LOD system doesn't differentiate between visible and invisible components, so the popping problem would still persist. The only way I could provide an option would be to have two sets of the airframe models for each aircraft configuration, and allow the user to select via the menu, which is making a lot of trouble for one feature in my estimation. However, this is the kind of feature that I frequently "explore" with my users and beta testers as I go. As the bumps in the MSFS 2024 road get smoothed out and we understand the performance impact of certain features, I tend to add things over time, so I would not be surprised to find myself adding this to all my aircraft during a round of updates at some point in the future.

I did four flights in the Baron today, and on the last one I used the 3rd Party KLN90B GPS. The flight was to EGGP. ATC gave me vectors for the ILS RWY 27 approach. As I no longer needed to follow the GPS, I switched the NAV source from GPS to NAV. I had the ILS tuned into NAV 1 (111.75) and the course set on the HSI. The ILS was identified and the needles started to creep in. I was in HDG mode, with APP armed. But the localizer was never captured, the Baron continued in HDG mode. I tracked the localizer in HDG mode, then disengaged HDG mode, clicked APP but nothing happened. Turned off the F/D and the A/P completely, back on, hit APP, nothing. I eventually landed manually. It would appear to me this issue does not occur with the GNS 530/430 but it does occur when either the Black Square RNAV system or the KLN90B panel config is used. I am yet to fully verify if the GNS 530/430 aren't affected but I can't recall this happening with that GPS config. I will download the free PMS and see if the issue happens with it.

@Black-Square any plans to include landing gear wear and tear systems maybe?

I think it would have been a customer choice rather than before/after a particular year. I've seen pics of early F28s with the bars, but there's also an (excellent) autobiography of an F28 pilot flying in the early 1970s where he specifically mentions the flight director being a 'bird'. So it may have been one of the many customer choices. Although it would be an absolute time/effort sink for JF, in an ideal world it would be great to see some more of the flight deck variations reflected in the model. Bar/Bird flight director, single or twin flight director controls (for different settings for Capt. and FO), autopilot master controls on the pedestal vs. the glareshield, the centre tank fuel pump switches and gauge disappearing when the tank isn't fitted (relatively few F28s had the centre tank bags - mostly military/govt. ones, it seems) and even the early engine instruments (with mechanical fuel flow gauges rather than the digital 'totaliser', which I think was only available on the 4000s and late 3000s). It would be a complete minefield trying to do the job thoroughly though - I've spotted three different positions for the Altitude Controller alone from old photos.

@fenthanyl I know the feeling. I'm also one to try solve my own problems before asking for help, probably to a fault. I'm just glad it's working now and you're able to enjoy this unique method of navigation. As always, let me know if there is anything else I can do for you!

Hold up guys. Dont get the release delayed due to these latecomer ideas lol

SimBrief has performance built-in. Even takeoff performance. Which I have checked is spot on!

Hello, I had the same on the TFDi MD-11. And I believe that if the aircraft is coded a certain way using MSFS's icing model and loading, you will notice the ice weight on your payload manager. On the MD-11 you will see the extra weight on the FMC's payload page as a higher gross weight than the sum of your airplane weight and fuel weight. This one I am not sure about. All I can think of is that maybe your intakes were clogged with and ice/or your inertial separators were closed. Leading to engines being chocked for air.

@Rich Thank you for sharing this information. It is nice to know where things stand.

Absolutely love to see this. I noticed the analog king air appeared to be a better trainer than the B200 sim I was trained on. It felt like the systems were modelled for a full cockpit sim as well.

Your explanations are always complete and thorough. Thank you every time you provide them. I have already replicated this behavior with SPAD.neXt. Regards.

Thanks for the feedback. Could we kindly ask you to forward that feedback to Just Flight Support via the following link: https://www.justflight.com/support Our support team will then be best suited to assist with troubleshooting and/or ensuring that any valid bugs are properly logged. However, just to note that point 1 is intentional logic, as each RJ livery is fitted with accurate equipment configurations by default. Point 2 sounds like expected logic if the engine parameters are on the limit of rounding up/down to the nearest whole number. This will likely vary on every flight as the engines will idle at different speeds/temperatures depending on weather conditions. Mark - Just Flight

Sorry for the delay. I was not sure if this would really be feasible to tutorialize, but after looking at the code, I think you will be able to figure it out. Here is the process. Let me know if you have any trouble following it. This is probably one of the more complicated things I have ever offered to walk someone through, so I apologize if I'm assuming any knowledge or skills that you don't already possess. Locate the following block of text in KR87.js: case "frqTransfert": if(this.multiMode != 0) this.multiMode = 0; else SimVar.SetSimVarValue("K:ADF" + this.radioIndex + "_RADIO_SWAP", "Boolean", 0); break; Copy this block below the break;, and rename the case for what you want to call your HTML event. For example, bigInc, will correspond to the HTML event, >H:adf_bigInc. Edit the second to last line of the code block to trigger the native K:Event that you would like. For example... SimVar.SetSimVarValue("K:ADF" + this.radioIndex + "100_INC", "Boolean", 0); For the small knob, which depends on the state of the knob being pulled or not, it would be... if(SimVar.GetSimVarValue("L:var_adfKnobPulled", "bool")){ SimVar.SetSimVarValue("K:ADF" + this.radioIndex + "10_INC", "Boolean", 0); else SimVar.SetSimVarValue("K:ADF" + this.radioIndex + "1_INC", "Boolean", 0); Now, search for ADF_Knob_Frequency_MHz_1 in AnalogTBM.XML. Here, replace the two following K:Events... <CLOCKWISE_CODE>(&gt;K:ADF_100_INC)</CLOCKWISE_CODE> <ANTICLOCKWISE_CODE>(&gt;K:ADF_100_DEC)</ANTICLOCKWISE_CODE> With your own new HTML events: <CLOCKWISE_CODE>(&gt;H:adf_bigInc)</CLOCKWISE_CODE> <ANTICLOCKWISE_CODE>(&gt;H:adf_bigDec)</ANTICLOCKWISE_CODE> This is the basic principle for all the changes that you want to make. Please let me know how this goes, and what else I can help you with. Thanks for being willing to experiment with this on your own! Like I said, I will consider doing this for all my aircraft in the future when I see exactly how many interactions would have to be updated across all my aircraft, but in the meantime, I am happy to help!

Close. You're looking for var_engineDamage_L, and var_engineDamage_R. Interesting. Is that what the URL gave you while the aircraft was loaded and running, or was that only within the main menu?

Thanks Mark !