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. Black Square Custom Failure Notes

Black Square Custom Failure Notes

Scheduled Pinned Locked Moved Black Square Add-Ons
13 Posts 4 Posters 357 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 last edited by
    #4

    Oh, I didn't think I had an event to reset all failures, but I do! It's H:BKSQ_FAILURE_RESET_ALL_FAILURES. I'll check on the rest soon.

    1 Reply Last reply
    0
    • K Offline
      K Offline
      ksmith
      wrote last edited by
      #5

      There are a couple of sync issues with the sync of the display when H:Event are used to toggle failures.
      Here are 2 use cases specifically:

      USE CASE 1, "show only active failures ENABLED"

      1. Here are two failures being toggled remotely in the TBM (causing them to enter FAIL state, as expected)
        Screenshot 2026-04-03 124015.png

      The tablet shows the state correctly.

      1. I then toggle the R BRAKE, causing it to be fixed...
        Screenshot 2026-04-03 124545.png

      ALL GOOD SO FAR.

      1. Lastly, I toggle the GEAR CONTROLLER, which was the only remaining failure. This fixes it as expected however the LAST item isn't cleared from the list and remains in red. Notice ACTIVE FAILURES is 0, which is correct:
        7d1c24fd-f813-46e8-aed0-b8072fbb39ed-image.png

      2. if I click RESET on the tablet....it actually triggers the failure... (photo taken after clicking RESET)
        544c347c-d17a-4990-962f-625edde78327-image.png

      3. if I click RESET on the tablet AGAIN...it works as expected, 0 failures and clear panel:
        622f4d64-902c-4c50-8e81-727f5c2e26d2-image.png

      USE CASE #2: "Show only active failures DISABLED"

      1. I click R BRAKE and toggle remotely (triggers a fail, as expected)
        0027b297-c482-46c0-9476-8c31477846ce-image.png

      2. I click R BRAKE and toggle (triggers a fix, as expected). Notice the tablet remains RED for that item, despite Active Failures correctly updating to 0.
        f620e2bb-2e6e-41dd-9fc2-6d6b6a87cab5-image.png

      The same behavior from use case #1 also happens here where if I click RESET on the tablet, it things it's resetting but it's actually toggling to fail mode...it then takes ANOTHER reset to clear.

      Keith Smith
      PilotEdge

      Black SquareB 1 Reply Last reply
      0
      • B Offline
        B Offline
        Buzz
        wrote last edited by Buzz
        #6

        Turbine Duke - Prop Governor Failure
        During a failed prop governor, with indications showing an inability for the governor to push the prop to fine pitch (Lower RPM than set with prop lever) we would expect to see a drop in oil pressure to confirm due to a leak at or before the governor. With the TDuke, a Governor failure causes a drop in RPM, (Inability to drive the prop to fine pitch), but we still have prop control along the lower band of the prop lever, which would indicate a low oil pressure condition at the governor. Maybe a fix in the future, or atleast corrected for any future Turboprops?

        1 Reply Last reply
        0
        • B Offline
          B Offline
          Buzz
          wrote last edited by Buzz
          #7

          All Black Square Aircraft - Pitot Blockage
          When a "Pitot Blockage" is triggered, the pitot heat switches get locked in the current position, regardless if they are on or off. Would it be possible to free up the switches from there locked state after a pitot tube blockage so that we can work through the failure procedure?

          J 1 Reply Last reply
          0
          • B Buzz

            All Black Square Aircraft - Pitot Blockage
            When a "Pitot Blockage" is triggered, the pitot heat switches get locked in the current position, regardless if they are on or off. Would it be possible to free up the switches from there locked state after a pitot tube blockage so that we can work through the failure procedure?

            J Offline
            J Offline
            jmarkows
            wrote last edited by
            #8

            @Buzz said in Black Square Custom Failure Notes:

            All Black Square Aircraft - Pitot Blockage
            When a "Pitot Blockage" is triggered, the pitot heat switches get locked in the current position, regardless if they are on or off. Would it be possible to free up the switches from there locked state after a pitot tube blockage so that we can work through the failure procedure?

            https://community.justflight.com/topic/9708/pitot-blockage-disables-the-pitot-heat/4?_=1775437463744

            That one is a sim issue.

            B 1 Reply Last reply
            0
            • J jmarkows

              @Buzz said in Black Square Custom Failure Notes:

              All Black Square Aircraft - Pitot Blockage
              When a "Pitot Blockage" is triggered, the pitot heat switches get locked in the current position, regardless if they are on or off. Would it be possible to free up the switches from there locked state after a pitot tube blockage so that we can work through the failure procedure?

              https://community.justflight.com/topic/9708/pitot-blockage-disables-the-pitot-heat/4?_=1775437463744

              That one is a sim issue.

              B Offline
              B Offline
              Buzz
              wrote last edited by
              #9

              @jmarkows Thanks.

              1 Reply Last reply
              0
              • K ksmith

                There are a couple of sync issues with the sync of the display when H:Event are used to toggle failures.
                Here are 2 use cases specifically:

                USE CASE 1, "show only active failures ENABLED"

                1. Here are two failures being toggled remotely in the TBM (causing them to enter FAIL state, as expected)
                  Screenshot 2026-04-03 124015.png

                The tablet shows the state correctly.

                1. I then toggle the R BRAKE, causing it to be fixed...
                  Screenshot 2026-04-03 124545.png

                ALL GOOD SO FAR.

                1. Lastly, I toggle the GEAR CONTROLLER, which was the only remaining failure. This fixes it as expected however the LAST item isn't cleared from the list and remains in red. Notice ACTIVE FAILURES is 0, which is correct:
                  7d1c24fd-f813-46e8-aed0-b8072fbb39ed-image.png

                2. if I click RESET on the tablet....it actually triggers the failure... (photo taken after clicking RESET)
                  544c347c-d17a-4990-962f-625edde78327-image.png

                3. if I click RESET on the tablet AGAIN...it works as expected, 0 failures and clear panel:
                  622f4d64-902c-4c50-8e81-727f5c2e26d2-image.png

                USE CASE #2: "Show only active failures DISABLED"

                1. I click R BRAKE and toggle remotely (triggers a fail, as expected)
                  0027b297-c482-46c0-9476-8c31477846ce-image.png

                2. I click R BRAKE and toggle (triggers a fix, as expected). Notice the tablet remains RED for that item, despite Active Failures correctly updating to 0.
                  f620e2bb-2e6e-41dd-9fc2-6d6b6a87cab5-image.png

                The same behavior from use case #1 also happens here where if I click RESET on the tablet, it things it's resetting but it's actually toggling to fail mode...it then takes ANOTHER reset to clear.

                Keith Smith
                PilotEdge

                Black SquareB Offline
                Black SquareB Offline
                Black Square
                Black Square Developer
                wrote last edited by
                #10

                @ksmith Hi Keith! Thanks for posting this here. I'm sorry that I haven't been as responsive over email as I have been here. Just a habit of what I check and when. My apologies.

                I believe I've fixed this for you guys. Pretty simple solution if you want to try it yourself. If you search for BlackSquareTablet.js, and then the comment containing Initiating HTML Failure for:, add the following block of code right before the next return;

                if(this.onlyActiveFailuresSwitch.checked)
                    this.updateFailureFilter();
                this.updateFailureBlock(this.failureMatrix[i]);
                

                I'm pretty confident that should fix all the synchronization problems you noted, so I will add that to all my other aircraft too. Let me know if that works, and if there is anything else I can do for you!

                K 1 Reply Last reply
                0
                • Black SquareB Black Square

                  @ksmith Hi Keith! Thanks for posting this here. I'm sorry that I haven't been as responsive over email as I have been here. Just a habit of what I check and when. My apologies.

                  I believe I've fixed this for you guys. Pretty simple solution if you want to try it yourself. If you search for BlackSquareTablet.js, and then the comment containing Initiating HTML Failure for:, add the following block of code right before the next return;

                  if(this.onlyActiveFailuresSwitch.checked)
                      this.updateFailureFilter();
                  this.updateFailureBlock(this.failureMatrix[i]);
                  

                  I'm pretty confident that should fix all the synchronization problems you noted, so I will add that to all my other aircraft too. Let me know if that works, and if there is anything else I can do for you!

                  K Offline
                  K Offline
                  ksmith
                  wrote last edited by
                  #11

                  @Black-Square That fixes both use cases, thank you.

                  Black SquareB 1 Reply Last reply
                  0
                  • K ksmith

                    @Black-Square That fixes both use cases, thank you.

                    Black SquareB Offline
                    Black SquareB Offline
                    Black Square
                    Black Square Developer
                    wrote last edited by
                    #12

                    @ksmith Wonderful! Thanks for the feedback. Let me know if there's anything else I can do for you guys!

                    1 Reply Last reply
                    0
                    • B Offline
                      B Offline
                      Buzz
                      wrote last edited by Buzz
                      #13

                      Blacksquare Baron P.

                      When an alternator check is done during runnup, taking one of the two alternators offline prompts an annunciation light. When a single alternator failure is triggered, we lose voltage for the failed alternator but we receive no annunciation light even though the failed alternator is not putting out any voltage.

                      Once voltage drops below a certain threshold, we should receive a light.

                      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