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. Steam Gauge Overhaul
  6. Baron 58P - AP altitude captures pressure alt instead "indicated" one

Baron 58P - AP altitude captures pressure alt instead "indicated" one

Scheduled Pinned Locked Moved Steam Gauge Overhaul
12 Posts 6 Posters 550 Views 4 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.
  • R Offline
    R Offline
    RzEmYk
    wrote on last edited by RzEmYk
    #1

    Hi,
    currently Baron's AP captures pressure altitude after flight (shown i.e. at Transponder) not altitude from main baro altitude.
    Standard flight, at destination I set current QNH (999 hPa), then I set 1013 hPa after TA. AP maintains FL190. At descent I set 3000 ft and destination QNH (1001 hPa).
    AP descent to pressure altitude FL030, but it's 2720 ft at 1001 hPa altimeter setting.
    AP altitude logic should use "indicated" value (at baro altitude) as input for calculations.
    AP altitiude

    F 1 Reply Last reply
    2
    • R RzEmYk

      Hi,
      currently Baron's AP captures pressure altitude after flight (shown i.e. at Transponder) not altitude from main baro altitude.
      Standard flight, at destination I set current QNH (999 hPa), then I set 1013 hPa after TA. AP maintains FL190. At descent I set 3000 ft and destination QNH (1001 hPa).
      AP descent to pressure altitude FL030, but it's 2720 ft at 1001 hPa altimeter setting.
      AP altitude logic should use "indicated" value (at baro altitude) as input for calculations.
      AP altitiude

      F Offline
      F Offline
      ftrdoc
      wrote on last edited by
      #2

      @rzemyk Having exactly same problem. I think you're spot on for the problem.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        Schmidde
        wrote on last edited by
        #3

        Same problem.

        1 Reply Last reply
        0
        • V Offline
          V Offline
          Voice of Reason
          JF Staff
          wrote on last edited by
          #4

          Answer from the dev for you...

          I've seen more than a few reports of this, but have been unable to reproduce the problem. It may be an issue with only the PMS50 supplied WTT Mode package, if you are using it. Either way, please delete this single line in the two systems.cfg files (one for the normally aspirated, one for the pressurized) aircraft:

          altimeter_indicator = 2

          Please let us know if that fixed the problem so that it can be included in the next update. If not, we will continue searching for the problem. Thank you!

          Please reply here to this one, once tested. Thank you.

          F S G 3 Replies Last reply
          1
          • V Voice of Reason

            Answer from the dev for you...

            I've seen more than a few reports of this, but have been unable to reproduce the problem. It may be an issue with only the PMS50 supplied WTT Mode package, if you are using it. Either way, please delete this single line in the two systems.cfg files (one for the normally aspirated, one for the pressurized) aircraft:

            altimeter_indicator = 2

            Please let us know if that fixed the problem so that it can be included in the next update. If not, we will continue searching for the problem. Thank you!

            Please reply here to this one, once tested. Thank you.

            F Offline
            F Offline
            ftrdoc
            wrote on last edited by
            #5

            @voice-of-reason Sorry. What’s the pathway to those files.

            R 1 Reply Last reply
            0
            • F ftrdoc

              @voice-of-reason Sorry. What’s the pathway to those files.

              R Offline
              R Offline
              RzEmYk
              wrote on last edited by
              #6

              @voice-of-reason said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

              altimeter_indicator = 2

              First try - it works :)
              I will try another flight tomorow to proof that solution.

              @ftrdoc said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

              @voice-of-reason Sorry. What’s the pathway to those files.
              ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron
              and
              ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaronturbo\

              F 2 Replies Last reply
              0
              • R RzEmYk

                @voice-of-reason said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

                altimeter_indicator = 2

                First try - it works :)
                I will try another flight tomorow to proof that solution.

                @ftrdoc said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

                @voice-of-reason Sorry. What’s the pathway to those files.
                ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron
                and
                ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaronturbo\

                F Offline
                F Offline
                ftrdoc
                wrote on last edited by
                #7

                @rzemyk Well try as I might for some reason windows 10 will not open that config file.

                1 Reply Last reply
                0
                • V Voice of Reason

                  Answer from the dev for you...

                  I've seen more than a few reports of this, but have been unable to reproduce the problem. It may be an issue with only the PMS50 supplied WTT Mode package, if you are using it. Either way, please delete this single line in the two systems.cfg files (one for the normally aspirated, one for the pressurized) aircraft:

                  altimeter_indicator = 2

                  Please let us know if that fixed the problem so that it can be included in the next update. If not, we will continue searching for the problem. Thank you!

                  Please reply here to this one, once tested. Thank you.

                  S Offline
                  S Offline
                  Schmidde
                  wrote on last edited by
                  #8

                  @voice-of-reason thanks for the reply. I had the problem with the TDS GTNXi too, but I'll give it a try today.

                  1 Reply Last reply
                  0
                  • V Voice of Reason

                    Answer from the dev for you...

                    I've seen more than a few reports of this, but have been unable to reproduce the problem. It may be an issue with only the PMS50 supplied WTT Mode package, if you are using it. Either way, please delete this single line in the two systems.cfg files (one for the normally aspirated, one for the pressurized) aircraft:

                    altimeter_indicator = 2

                    Please let us know if that fixed the problem so that it can be included in the next update. If not, we will continue searching for the problem. Thank you!

                    Please reply here to this one, once tested. Thank you.

                    G Offline
                    G Offline
                    GeorgNaujoks
                    wrote on last edited by
                    #9

                    @voice-of-reason

                    I have the PMS50 installed but am using the TDS GTNXi but I can confirm, after deleting the line the AP now captures the correct height.

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      Schmidde
                      wrote on last edited by
                      #10

                      Can confirm, PMS50 GTN installed and using the TDS.
                      AP levels at the set Baro altitude after applying the "fix".

                      2023-03-28 18_57_22-Microsoft Flight Simulator - 1.31.22.0_2.jpeg

                      1 Reply Last reply
                      0
                      • R RzEmYk

                        @voice-of-reason said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

                        altimeter_indicator = 2

                        First try - it works :)
                        I will try another flight tomorow to proof that solution.

                        @ftrdoc said in Baron 58P - AP altitude captures pressure alt instead "indicated" one:

                        @voice-of-reason Sorry. What’s the pathway to those files.
                        ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaron
                        and
                        ..\Community\bksq-aircraft-analogbaron\SimObjects\Airplanes\bksq-aircraft-analogbaronturbo\

                        F Offline
                        F Offline
                        ftrdoc
                        wrote on last edited by
                        #11

                        @rzemyk Confirm that deleting the line from sys config fixed the problem. Thx for rapid response and help! 👍🏻😎

                        1 Reply Last reply
                        0
                        • C Offline
                          C Offline
                          Cristi Neagu
                          wrote on last edited by
                          #12

                          As a note, I have heard of an issue similar to this. I think it was in the base sim, not sure if it was fixed. Back then the developer also said they couldn't replicate it. Turns out the reason for this was that the developer was pressing B to set the altimeter. This also did other things in the background that fixed the discrepancy. Not sure if this is the same issue here, but if anyone is trying to replicate this, try to do it without hitting B and by setting the altimeter by hand.

                          1 Reply Last reply
                          1
                          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