Something very strange is happening with redstone torches lately. Normally, a torch would turn off when the block it’s attached to receives a redstone signal. It still does this, but only to an extent. It’ll work, until you leave and reload into the world. After that, for some reason, it’ll only turn off when the signal strength that the torch is receiving is at it highest possible strength, 15. Any lower, and the torch will stay on. What’s weirder is that once you change anything to the circuit, like breaking and re-placing a redstone dust or torch, it’ll work again. What’s even WEIRDER is that when I discovered this issue, another NOT gate right next to the one that was having this issue was working just fine. I think it might have to do with direction? The buggy NOT gate had the torch facing east, with the normal working one facing west.
Related issues
Attachments
Comments
migrated
[Mod] Umija5895M
This may be a duplicate of MCPE-48054
GoldenHelmet
Could you upload a picture of your cirtuits, or upload the world or a small test world that reproduces the issue?
migrated
RPReplay_Final1585934323.MP4
RPReplay_Final1585934626.MP4
The first video in the superflat world is what’s supposed to happen. The second one is what happens in my other world. The redstone torch doesn’t turn off, until I literally prove to the game that it should.
Also, I don’t know if these links will work, but I’m trying.
migrated
Dang it they don’t work. I’ll try to get iCloud links as soon as I can.
migrated
GoldenHelmet
Thanks for providing the videos. What's causing the issue is not the direction of the torch, but the fact that the block it is attached to is on a chunk border at X = 208. The dust going into it at X = 207 is in a different chunk. That much is the same as the setup shared by the original poster of MCPE-48054.
What occurs in the MCPE-48054 setup is that the two chunks are loaded and update their redstone circuits at different times. The result is that when the chunk with the block and torch is reloaded, the redstone dust going into has already finished its updates and does not try to update the block again, so they both stay on. (I just added steps to reproduce MCPE-48054 in a comment today, by the way.)
Your setup is peculiar in that you are sending a signal through the redstone dust while the chunk with the torch is loaded. This should trigger the block and then the torch to update their power states, but in your world it doesn't. However, when you trigger block updates by breaking the blocks above the dust, then everything updates correctly.
I am going to do some testing with setups like yours to try to understand better what is happening determine how to reproduce the issue. The problem could be coming from inner workings of the block, the redstone dust, or the pressure plate, but at this point I don't think it is the torch itself.
GoldenHelmet
@Taylor S could you tell me the coordinates where you relog in your world to reproduce the stuck circuit, or does it happen anywhere you relog?
Nevermind, I've reproduced it just by relogging in a neighboring chunk!
GoldenHelmet
I've determined that this is the same issue as MCPE-48054, just occuring in a different context. They key points that are the same are redstone dust pointing into an opaque block in a neighboring chunk, and the block getting stuck at power level 0 and unable to receive redstone updates from the dust. Thus:
[media]Also, redstone updating linkage can be restored in the same ways: by either a block update to the redstone dust, or a redstone update to the block. But not by a redstone update to the dust (i.e. change in power level).
The scenario in this ticket is actually much easier to reproduce, as you only need to relog in a nearby chunk closer to the dust chunk than the block chunk, and the block will have a chance of getting stuck. It does not happen every time. It is probably more likely if you can generate loading lag/delay.