MSFS Products

There are a few bugs ive noticed on the AVRO RJ (v0.1.5) on MSFS 2024 SU4 Release. Some have been around for a while now. Aircraft specific configuration options (such as HF Aerials, Metric Altimeter, VHF Tail Aerial) does not save between sessions and is restored to a default configuration. The N1 indications for engine no.3 and no.4 when on the ground at idle has this jittering effect where the indication jumps between 24 to 25 percent n1 (only a problem in msfs2024 and is fine in msfs2020). You are unable to change the flipchart weight option when "FLIPCHART WT SYNC" in the efb is not selected. This will only happen in the next sessions that you fly after you have deselected this option. The autopilot seems to lag behind the flight director when in use, especially in the roll axis, when I look up any cockpit videos of any AVRO RJ, the autopilot flies dead true onto the Flight director even when banking, but I could be misinformed here. External light bulbs during the day have a strange black orb artifact. During night time ops they seem fine. I do believe I read somewhere that you guys were planning a large update for the AVRO RJ like you have done with the 146 recently, but I could be wrong. Nevertheless I thought I should inform your team about these issues I have encountered.

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.

WORKING FINE NOW

Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change. It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface. Mark - Just Flight

@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

Re: Feature Requests Can we please get an updated FS Traffic Manual that shows SETUP Global settings for the latest version of MSFS 2024 instead of ones that no longer exist (e.g. "TRAFFIC AIRPORT QUALITY"). Thanks.

Please see: https://community.justflight.com/post/46913 Mark - Just Flight

From our internal testing of the post-SU4 updates, we reliably see the correct state recalled on the first flight of a session, and then it becomes inconsistent on subsequent flights in the same session. Mark - Just Flight

Stand down everyone. I figured it out. Well, not so much 'figured' but stumbled upon it. You know the saying 'If you throw enough s**t at the wall, some of it will stick'? That the method I used.