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

Thanks for the advice, clear instructions and the reference document. Your trick works, although "Control AP Pitch with Hardware events" enabled seems to disable script commands for the pitch reference knob. I ended up setting up a script CWS in manner of your screenshots.

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.

Thank you so much. Thats incredible! I'll try not to be a pest and work things out myself in future. I'll post some photos aswell if that's ok. I haven't delved into other aircraft or addons or even fine tuning frame rates etc yet. Just solid building and the analogue king air (mainly sitting on the runway for hours on end)... which has saved my a$$ and made things possible. It's a very niche arm of cockpit building. I have hundreds of design files for 3d prints and laser work for a king air, So if anyone needs anything to kick themselves off I'd be glad to help. It'll save you going down the road i did.

@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

The most recent update we have shared on the Tornado is here: https://www.justflight.com/articles/end-of-year-round-up-2025-part-five Speaking on behalf of the development team, we're all looking forward to spending more time working on the Tornado again! We'll be sure to share more info as development progresses. Mark - Just Flight

My initial impression is that TOW is quite heavy for EGLC, and flap 18 is quite a low flap setting. I just set up a basic EGLC-LSZH flight plan on Simbrief with the RJ100, and opened the Takeoff Performance calculator. For EGLC, it has given me a maximum runway weight of 40,100kg and a Flap 30 takeoff at that weight. That is also with TOGA MAX selected on the TRP. For reference, some airlines would actually takeoff from EGLC with Flap 33 selected! Quite the unique quirk of the RJ. Mark - Just Flight

@chipper_skipper I have to hit the AP twice to get the alarm off.

Hi, I do not have the PMS. Only have what comes with the package. It's completely a matter of hit or miss. The same config sometimes yields to a successful ILS capture, sometimes the ILS does not capture. Yes, the indications are fine, the needles move as they should, but HDG mode remains active, APP remains armed but not activated. So far I only noticed this behavior when I was using a config which included the KNS81 RNAV computer, in which case, the issue happened more than 50% of the time. Yes, I always use the NAV 1 radio for the ILS approach, change the NAV source well in advance, change HSI source, the DME source. Everything is well prepared for the capture. I also tend to use HDG mode to intercept the localizer, even when my RNAV waypoint could achieve the same, I switch to HDG mode and expect the LOC to take over - but it does not happen consistently. I never noticed this before I started to use the RNAV computer. In the early BS days, the RNAV computer wasn't working with the autopilot and so I never chose a RNAV panel config - never experienced the problem of non-captured ILS either. But since I bought the new Baron, and since then the Duke, knowing the RNAV can be used with the autopilot, I actually use it a lot - and interestingly, the issue with the ILS appeared. Therefore, I dare to say this behavior is somehow related to the RNAV system and its methods of utilizing the autpilot. Perhaps 3rd party scnery also play a role here (I only fly to 3rd party scenery, never use stock ones, except for those "enhanced" ones). So it may be more than just one thing.

@toucan08 said in DH98 MSFS2020, Cockpit View: Perhaps I need to go to MSFS forums with more traffic. I'm not sure there is a Mosquito for MSFS yet. What software are you referring to?

Unfortunately, as is the case with all releases, we won't have a release date until development and testing is complete. That's still ongoing but the title is progressing towards completion. It is a complicated aeroplane and we are keen to ensure that it releases in the best condition possible for our customers. The good news is that there is no need to visit our website daily (although the traffic is helpful) - you can sign up to be notified of release here: https://www.justflight.com/email-when-available?product=f70-100-professional

@Black-Square The more I scroll through fs forums, the more glad I am that I went into flying planes over developing simulated ones...

@Iconography Didn't know that was a work around, thank you!