Duke (Piston + Turbine) LVAR for MobiFlight

Captain_J

Yes, when in ATT mode, that coding works perfectly for pitch control.

exorbit

This post is deleted!

Tailhook

@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:

Tailhook

(see above post)

You did the exact same thing on the Baron professional. Please correct them so both mag switches are similar. Change MAG1 to K:SET_STARTER1_HELD.

jmarkows

Had a similar issue in the Bonanza regarding the Ignition Position not working right for positions 4 and 5. Nick has fixed it for a patch next week, hopefully the same fix can be applied to previous aircraft.

Black Square

@jmarkows Yes, that change should solve any issues here too, with the 5 position now working as a start position with no spring return.

Tailhook

@Black-Square I'm open to testing anything prior to release.

Black Square

@Tailhook Thanks for volunteering! Believe it or not, it should be as simple as doing the following find-and-replace on the main behaviors XML, and of course for BKSQ_IgnitionPosition_2, as well.

Find: (L:BKSQ_IgnitionPosition_1, number) 4 ==
Replace: (L:BKSQ_IgnitionPosition_1, number) 4 >=

Tailhook

@Black-Square

Find: (L:BKSQ_IgnitionPosition_1, number) 4 ==
Replace: (L:BKSQ_IgnitionPosition_1, number) 4 >=

Tried this (3 lines, both mags), no difference. The mags won't go into START now at all. Still need to use the two different event's I posted above to get any action out of both L/R starters.

Black Square

@Tailhook Three lines? I only see two. Also, when you say you tried it, do you mean that you tried your previous homebrew solution, or you tried incrementing/decrementing L:BKSQ_IgnitionPosition_1 0 -> 1 -> 2 -> 3 -> 5?

Tailhook

@Black-Square Lines 5256 and 5298 were the '3rd' for each. ¯_(ツ)_/¯

I reverted those lines and tested again. Setting ignition to 5 does crank the starter now. But this change is not realistic because the knob only counts to 0-4 when using mouse.

Instead, I replaced:
(A:GENERAL ENG STARTER:1, bool) if{ 0 (>A:GENERAL ENG STARTER:1, bool) }
with
(A:GENERAL ENG STARTER:1, bool) if{ 0 (>K:STARTER1_SET) }

and

(A:GENERAL ENG STARTER:2, bool) if{ 0 (>K:SET_STARTER2_HELD) }
with
(A:GENERAL ENG STARTER:2, bool) if{ 0 (>K:STARTER2_SET) }

NOW the magneto switches go to START when in position 4, like they should.

jmarkows

@Black-Square said in Duke (Piston + Turbine) LVAR for MobiFlight:

@Tailhook Three lines? I only see two. Also, when you say you tried it, do you mean that you tried your previous homebrew solution, or you tried incrementing/decrementing L:BKSQ_IgnitionPosition_1 0 -> 1 -> 2 -> 3 -> 5?

So when the patch comes out, or we put the fix in manually, we should skip a value of 4?