Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. Black Square Add-Ons
  5. Piston & Turbine Dukes
  6. Duke (Piston + Turbine) LVAR for MobiFlight

Duke (Piston + Turbine) LVAR for MobiFlight

Scheduled Pinned Locked Moved Piston & Turbine Dukes
58 Posts 8 Posters 8.5k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Black SquareB Offline
    Black SquareB Offline
    Black Square
    Black Square Developer
    wrote on last edited by
    #48

    L:BKSQ_ShowCopilotInterior

    I'm glad you got the altitude alteter working. I will have to think about why it works with that configuration to see if I have any further suggestions for you.

    1 Reply Last reply
    0
    • C Offline
      C Offline
      Captain_J
      wrote on last edited by
      #49

      All good, as always, I appreciate your support, thanks.

      1 Reply Last reply
      0
      • C Offline
        C Offline
        Captain_J
        wrote on last edited by
        #50

        I'm encountering an issue where I've assigned the K:AP_PITCH_LEVELER_ON to my personal VS AP button (to switch to ATT mode), however when I do that GA lights up instead on the AP panel. Is there an error here in that VAR?

        Also I don't understand how/why there is a AP GO-AROUND MODE (AUTO THROTTLE to GA), because I didn't think the Duke had any kind of auto throttle?

        1 Reply Last reply
        0
        • Black SquareB Offline
          Black SquareB Offline
          Black Square
          Black Square Developer
          wrote on last edited by
          #51

          K:AP_PITCH_LEVELER_ON should do the trick, but it's possible that pressing it a second time in some circumstances could result in what you're seeing. Unfortunately, the MSFS variable to detect when go-around mode is activated is broken, so I've had to do some of my own process of elimination for the GA indicator. Looking at my code, I can see many questions I could ask in an attempt to get to the bottom of this, but let me start here: Is the pitch control mode working when you adjust the target pitch with L:var_AP_PitchKnob?

          The Duke has no auto throttle, but the go-around mode can be used to position the flight director at 8° nose up with wings level for initial climb out.

          1 Reply Last reply
          0
          • C Offline
            C Offline
            Captain_J
            wrote on last edited by
            #52

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

            1 Reply Last reply
            0
            • E Offline
              E Offline
              exorbit
              wrote on last edited by
              #53
              This post is deleted!
              1 Reply Last reply
              0
              • Black SquareB Black Square

                No problem!

                You can either use the native magneto events, such as "K:MAGNETO1_OFF", "K:MAGNETO1_LEFT", "K:MAGNETO1_RIGHT", "K:MAGNETO1_BOTH", "K:MAGNETO1_START" (there are more for different purposes)...

                ...or you can use "L:BKSQ_IgnitionPosition_1", which runs from 0-5. 5 is used for holding the start position without automatic return to both.

                T Offline
                T Offline
                Tailhook
                wrote on last edited by
                #54

                @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:
                1.png 2.png

                1 Reply Last reply
                0
                • T Offline
                  T Offline
                  Tailhook
                  wrote last edited by
                  #55

                  (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.

                  1 Reply Last reply
                  0
                  • J Offline
                    J Offline
                    jmarkows
                    wrote last edited by
                    #56

                    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 SquareB 1 Reply Last reply
                    0
                    • J 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 SquareB Offline
                      Black SquareB Offline
                      Black Square
                      Black Square Developer
                      wrote last edited by
                      #57

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

                      T 1 Reply Last reply
                      1
                      • Black SquareB 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.

                        T Offline
                        T Offline
                        Tailhook
                        wrote last edited by
                        #58

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

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users