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.

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

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 !

Odd Couple 2026 [image: e53157f9-35b0-49d6-adc3-e78ff561a0cc.png]

@Black-Square When do you expect to implement these changes in your Add-On? I love both Bonanza and Baron and would like the small objects culling problem to be sorted out.

This would be an awesome feature, I would definitely use it on the whole range of JF aircraft, I assume the a300 will have the UNS1 as well so that would be perfect. I think the code would carry over to the Boeing FMC as well, as far as the Pyhton script goes.

Generally speaking you should not utilize the autopilot when flying any light twin single engine. That said if you are single pilot and, it may not be a bad idea to engage it momentarily to maintain a safe attitude while completing something like an approach briefing. I used a KFC 225 momentarily on my Multi IFR training, but found I did not need it. In the sim where you are using a mouse and keyboard to look around and complete actions I can imagine it would be very helpful. Extra Blurb: When experiencing an engine failure you are to conduct the appropriate emergency checklist for the phase of flight from memory in a timely manner and then declare an emergency. My flow for the turbine duke would look like this: Disengage autopilot Maintain control (Maintain ALT if able and pitch up to compensate for power loss ensuring your speed does not fall below the blue line speed) If Fire: extinguish and continue below next two items Identify the failed engine visually with rpm gauge verify (utilizing the throttle to ensure the identified engine's gauges are unresponsive to inputs) Inop Eng Power Lever Idle Inop Eng Propeller Feather Inop Eng Condition Lever Cutoff Op Eng Propeller Full Forward (Not in Checklist but should be) Op Eng Power Lever 1200 FT-LBS if level; 1260 FT-LBS if climb is required Establish a safe flight attitude (very important and why you should not utilize A/P): Hold dead engine wing up with 3-5 degree bank and apply appropriate rudder to keep the turn coordinator ball half out towards the dead engine (consider using rudder trim if extended flight is required on one engine) Continue rest of checklist items utilizing emergency checklist and declare emergency with ATS Everything before last bullet point should be able to be executed within 15 seconds of the engine failing if you are proficient. In a piston engine aircraft in cruise phase of flight you would also need to demonstrate executing troubleshooting items from memory as well before cleaning up and feathering the failed engine if the failure was not obviously catastrophic.

This bug is confirmed. Sometime after engine start, anti skid becomes INOP and nothing can fix it. Hydraulic pressure is adequate. All systems are in normal position.

@Derek Hi Derek, My bad? I've installed the airport. I don't know what went wrong but it's a different animal. Guess it could have been a glitch (as you do with bits and bytes) anyway all okay now. Thanks for your prompt reply Alan

Yeah, I looked a lot closer at this, and I have now decided that I just couldn't see the instrument lights, and it's not a bug. I can see the instruments well enough, but was expecting a bit more illumination if I turned on the lights. All good.

Just realized I never replied here. No issues found. I do not have PMS and do not intend to get it.

@Mark disse em UNS-1: Banco de Dados Expirado: Cada solicitação de recurso que é passada para nós, incluindo as listadas neste tópico, é registrada em nossos rastreadores internos de solicitação de recursos. Quando chegar a hora de começarmos a trabalhar em uma atualização para um de nossos produtos, nossa equipe de desenvolvimento analisará todos os itens registrados em nossos rastreadores de solicitações de bugs e recursos e, em seguida, criará um escopo para essa atualização. Com a gente apoiando ativamente 10 produtos para MSFS, além de continuar trabalhando em nossos produtos em desenvolvimento, infelizmente não é viável para nós trabalharmos em toda a solicitação de recursos toda vez que um produto é atualizado, então, naturalmente, temos que priorizar bugs/solicitações de recursos. Ao longo de 2025, o foco principal da nossa equipe de desenvolvimento tem sido fornecer atualizações/atualizações gratuitas para todos os 10 produtos MSFS, atualizando-os para o padrão nativo MSFS 2024. Você pode ler mais sobre isso aqui: https://www.justflight.com/articles/end-of-year-round-up-2025-part-one Como o foco principal de cada uma dessas atualizações era atualizar os produtos para o status nativo do MSFS 2024, qualquer trabalho relacionado ao MSFS 2024 era a maior prioridade. Solicitações de recursos, especialmente aquelas relacionadas a alterações no código FMS principal, eram de menor prioridade para essas atualizações e, portanto, bastante mínimas. Nunca removemos bugs ou solicitações de recursos de nossos rastreadores internos até que sejam corrigidos ou concluídos, portanto, tenha certeza de que as solicitações neste tópico permanecem registradas e serão consideradas novamente quando criarmos o escopo para atualizações futuras. No entanto, como o desenvolvimento do simulador de voo é muito fluido, não fornecemos prazos para quando bugs específicos ou solicitações de recursos serão corrigidos. Se você preferir não usar o FMS UNS-1 no F28, ainda pode aproveitar ao máximo os outros dois métodos de navegação, que usam os dados de navegação dos simuladores padrão que são atualizados gratuitamente todos os meses: Navegação Tradicional usando os rádios ADF e VHF NAV (configurado desativando a opção "OPÇÕES DE RNAV" no EFB/Tablet) GPS GNS430 (configurado ativando a opção "OPÇÕES RNAV" no EFB/Tablet e selecionando o "GNS 430") Mark - Apenas Voo I have no doubt about your support, but I believe this should be an even higher priority for the community, especially for those on Xbox (who are always the most affected by the limitations we already know). The 'urgency' in implementing this improvement (database updates via the tablet) is perhaps because other developers, like PMDG for example, implemented this a long time ago without much delay. And it works perfectly on both PC and Xbox. I understand your explanation, but as a customer, I don't feel comfortable having a product that could offer even greater immersion and realism if it weren't for an extremely outdated database. I hope new projects like the A300 have this feature (if you offer the UNS-1 as a navigation option there as well).

Thanks for the feedback. There are no plans at the moment for further changes to the sound set in the 146, as we are happy with the current implementation. With regards to engine sound at altitude, it is worth considering how close the engines are to the cockpit in the 146 compared to other aircraft. 4 engines a few meters behind the cockpit compared to 2 engines 10+ meters back on a more conventional aircraft. The rain sound effects aren't something I have seen reported before. Could I kindly ask you to record a video of that and then send it in a ticket to Just Flight Support at the following link: https://www.justflight.com/support Then our support team will be able to assist with troubleshooting that, or they will properly log the feedback on our internal trackers for further investigation. Mark - Just Flight

The first thing I typically recommend is setting the MSFS Turbulence settings to LOW or MEDIUM. This is based on feedback from pilots on our various testing teams that state that the REALISTIC option produces much more aggressive winds than they would encounter in the real world. This setting is located at: MSFS Options > Assistance > Piloting If that behaviour persists, we would recommend raising a ticket with Just Flight Support via the following link, and our support team will be able to further assist: https://www.justflight.com/support Mark - Just Flight