Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-14791

Comparators don't activate when they're getting power from detector rails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 0.16.1
    • 0.14.3, 0.15.0 Beta build 1, 0.15.0 Beta build 2, 0.15.0 Beta build 3, 0.15.0, 0.15.1 Beta 1, 0.15.1, 0.15.2, 0.15.3, 0.15.6, 0.15.90.0, 0.15.7, 0.15.90.1, 0.15.90.2, 0.15.8, 0.15.90.7, 0.16.0
    • Confirmed
    • Android

      My device = Kingzone K1 turbo

      I exspected that the comparator' back is shining AND the comparator makes a redstone signal.

      I saw the comparator was not activated, even it did not make a redstone-signal, normally the comparator should do this!

      How to reproduce:
      1. Place a comparator
      2. Place a detector rail as a redstone-power-source at his back
      3. Place any type of minecart on it
      4. You will see, the comparator is not making anything

      UPDATE: As of 0.16.1, this bug is only partially fixed: Comparators can receive power from redstone dust that is powered by a detector rail, but they cannot recieve power directly from the detector rail. Sometimes, however, placing a comparator next to a detector rail will cause it to be momentarily powered when it is first placed, giving off a pulse of at least 1.5 rticks (3 gameticks), or however long a pulse is required to be in order to invert a redstone torch in MCPE. See this video for a demonstration: youtu.be/9E4gOTQ4W7c

        1. 300px-Detector-comparator-diff.png
          88 kB
          [MCPE Mod] Dr.Awesome4333
        2. Comparator-Detector-Rail-Bug-0.16.1.png
          337 kB
          Zeb
        3. with_redstone_signal.png
          953 kB
          Daniel R.
        4. without_redstone_signal.png
          1.03 MB
          Daniel R.

            uduster Daniel R.
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: