Hello Mark, The problem has been resolved. Thank you for your efforts and quick responses. With kind regards, Robert. [image: a2256e26-decd-4d5f-902f-c103e0aea4b5.jpg]

That's great. Thanks!

OK thanks! I just wanted to confirm whether it was something I was doing wrong, or a future fix, or even it may be working as intended verified by a real world RJ pilot. I know you guys have bigger fish to fry now, like the 146 update.

Do you use FSRealistic?

@Black-Square Bumping this thread because this is wrong and because the cockpit XML for piston duke needs fixing. I've been trying to get both engines started through SimConnect for 4 hours. That is until I realized the cockpit XML is different for each engine mag switch. When using the behaviors variable list, "BKSQ_IgnitionPosition_1/2" is only writable 0-3. Setting it to 4 auto-reverts back to 3 and setting it to 5 does nothing but animate it to START while starting nothing. i finally managed to start the left engine with A:GENERAL ENG STARTER:1 and K:SET_STARTER1_HELD. And start the right engine with A:GENERAL ENG STARTER:2 and K:MAGNETO2_START. Nothing else worked for me. I tried all the SimConnect magneto and starter set/toggle events and achieved nothing. The prop would just twitch or do nothing at all. The plane appears to require the usage of A:GENERAL ENG STARTER:x and doesn't respond to standalone K events. Please correct this section: [image: f8787597-7d12-4d8f-b4f3-b54c6fde0795.png] [image: 8e2b2df9-45b0-4758-bf0d-cc4801311d30.png]

Perfect! It works, thank you!

No Luck so far.

@Black-Square Wait, I mean I knew that turbines are significantly lighter than reciprocating engines, but I hadn't ever thought much of the fact that the empty weight on the piston Dukes is lower, and by a few hundred pounds that can't all come from the second battery. Where could all that extra weight come from? I thought other than the engines, second battery and the requisite differences to the HVAC, pressurization systems and panel they were largely identical?

Understood.

Hi Guys, I get the same problem (from time to time) using MSFS popout Manager and my.... G1000 King Air homecockpit (but with the great Black Square Analog King Air as a backbone). So any help on that matter would be appreciated. Regards, Francois

If this behaviour occurs again, could we kindly ask you to raise a ticket with Just Flight support at the following link: https://www.justflight.com/support In the ticket, if you could include screenshots/videos of the behaviour, plus any steps to reproduce the issue, then that will give our support team the best shot at trying to replicate this behaviour, which can then be passed on to our development team if required. Mark - Just Flight

The NAV light LOD behaviour isn't directly fixed by building a product as an MSFS 2024 native package, as the behaviour exists with the RJ, which post v0.1.4, is an MSFS 2024 native package. We do have some ideas on how we can work around the NAV lights LOD limitation, and we will be investigating them ahead of the next update to the RJ. Mark - Just Flight

If this behaviour occurs again, we kindly recommend that you raise a ticket with Just Flight support at the following link: https://www.justflight.com/support In the ticket, if you could include screenshots/videos of the behaviour, plus any steps to reproduce the issue, then that will give our support team the best shot at trying to replicate this behaviour, which can then be passed on to our development team if required. Mark - Just Flight

Maybe I have seen a similar issue (but on SU4 beta, don't know if that plays probably a role) I was on a course which had sth like a wide rectangle path. [image: 87f4610b-0448-436f-81e3-df107cac48df.png] Original active leg was from the left position to 1 (note: its just for illustration. "1" was not the first WPT on the plan) Then I set a direct-to to 3. What happened then was, that the leg from 2 to 3 got magenta. And the Starship was flying a course like the direction from 2 to 3. But not heading to the leg or to 3. What I would have been expecting was, that it steers at this point directly to 3, maybe "illustrated by a magenta line from PPOS to 3?! But no line was drawn, just the active magenta leg from 2 to 3. I then made a direct to to 4, leg 3 to 4 got active and Starship was flying to that leg. Mysterious ...

Thanks Mark i’ll reach out to them for further assistance.

Correct, using Spad.Next.

Hmm, the files manifest.jason in my 2020 installation specify version 0.1.3 for the Piston Duke and 0.1.2 for the Turbine Duke. As of today the Dukes do not appear on the 2024 Marketplace.

Oh okay. Maybe it's a case where my references are too old and the starships you modeled this after behave differently? But yeah the other stuff I mention was fixed so thank you for that and sorry, it's just the manual boot tests are not displaying and extinguishing the various messages.

@Pixel-of-Life I am wondering if anything came of this idea. I have looked for the file with the yellow sticky note to see if I could mod it. Given the functionality of the yoke light it would be very useful to create a file you could use from maybe the ipad that allowed you to change out the sticky note with useful cruise/climb settings, etc.

@DrZGard the only things I have working in modded files right now are the transponder presets and changing the fuel increment from 10 to 5. I have tried the others in modded files, and I think they should work but they don't, either as a separate mod or modding the files directly in the aircraft folder (which I hate doing). I should mention this is in 2024 SU3.