Piston & Turbine Dukes

I saw exactly this while testing with the Dukes in SU3 Beta. Before SU3, there were big problems with lights shining through objects, being misaligned, and other issue. In SU3, Asobo provided a new flag for us to set in the lighting effects that prohibited the halos/flares that were causing the issues, specifically on omni-directional lights. I believe this is what's going on in your screenshots, since I don't see the navigation lights shining through, but only the omni-directional lights that I've added to enhance the lighting effects. Are you using the newly updated 2024 native version of the Dukes? Do you have any liveries/mods installed that may have overwritten my new lighting effects? It's also possible there was a reversion in the latest SU4 Beta, if you're on the beta branch. I can help you troubleshoot more from there, but I hope this might give you some places to start looking for what's interfering with those new files.

@Donka I'm glad I could help. I noticed some strange effects with volumes varying during my occasional uses of 2024, and was surprised to find this option lurking in the menus. It's not a bad idea to include such a feature, but didn't like that it was enabled by default.

Nice to know Nick, cheers. CG

Still no news about the Dukes in FS2024 Marketplace?

I found the key, thanks anyway. FYI it was during the update from the Contrail store and the key is found within their app. The confusion arose when their app invoked an update window with a JUST FLIGHT title border requesting a key that begins with CONT-XXXX-XXXX-XXXX-XXXX

@Black-Square The funny thing is, I noticed it in 2020. No worries. (Although, I wouldn't mind paying for a separate livery pack or 4 on Xbox....)

I've always assumed that this was by design, but I will ask my sound designer about it.

No it hasn't. I was only referring to the Piston Duke.

Bought both aircraft in 2020 marketplace, can confirm the updates have made it into 2024. Wonderful updates and thank you for continuing to add the PNS750 for us Xbox users.

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]

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.

Even worse for me. I do a free flight with the duke selected. Next time I fly it shows the previous aircraft as the default selected. I then have to select the duke and update the control options every time I want to fly the duke. Rinse and repeat. Not sure whats going on here.