-
Bug
-
Resolution: Awaiting Response
-
None
-
1.20.10.23 Preview, 1.20.0
-
None
-
Unconfirmed
-
Multiple
I used a lot of pistons in my friend's Bedrock server to build redstone circuits.
However, when my machine started running, the server became stuttering abnormally.
I've learned from other players that when the Pistons needs to push/pull back, but can't succeed, it tries every Redstone tick until it succeeds. I think this is a glitch (programming flaw).
(Next is my thoughts, please read carefully)
So, I'm thinking. Whether replacing a better detection algorithm can reduce the performance overhead.(This method may work for Java Edition)
When the piston is pushed out or pulled back, the driven block is like a tree. Slime blocks and honey blocks are like trunks and branches, and the blocks that are driven are like leaves.
So, we can build a "moving block tree" and when the piston fails to push or pull back, only check if it can be pushed out or pulled back when the blocks around the "moving block tree" are updated.
- is duplicated by
-
BDS-18460 Piston performance issues
- Resolved
- relates to
-
MCPE-157252 A large number of pistons will cause lag
- Reopened
-
MCPE-134473 Updating redstone components with pistons causes excessive server lag when they are connected to large amounts of producers
- Resolved
-
MCPE-170320 When pushed by pistons, blocks may briefly become invisible.
- Open