
Can’t even make a simple flying machine work on bedrock. I don’t understand why the devs aren’t fixing this. It’s been like this for as long as I can remember bedrock edition existing. They market it as the main version of the game yet it’s just ultimately worse than Java.
As I console player I have no choice but to play bedrock edition, it’s the only version I have access to. And it really pains me to see how many parity issues we still have after all these years. It’s this kind of stuff that makes me feel discouraged and stop playing the game.
by sonneywhits
19 Comments
The machine is dancing instead 💔
I understand your frustration but in this particular case, flying machines do work on bedrock. You just need to find bedrock specific designs
java redstone is like 1+1=3
bedrock redstone is like 1+1=8 but also sometimes 3 but also sometimes 62
When 2 pistons pull a block in opposite directions on Bedrock in the same tick, the piston that pulls the block is chosen at random, while on Java, it’s always the same piston that pulls the block every time so you can make flying machines with 2 pistons that activate in the same tick without having to deal with randomness like on Bedrock
I was using this exact design like a day ago and it was working fine
Ew what is it doing
There’s no quasi connectivity or one tick sticky piston pulses on Bedrock. One of the main reasons why it’s different compared to Java edition.
As a mobile only player, I feel your pain- a lot of basic things are possible, but harder, and anything properly technical is completely impossible. It’s stupid, but at least we can make most basic farms pretty well, and flying machines can work too with some specific designs, theyre just a fair bit different lol.
Someday, we will play Java
i think it’s too late for them. fixing it will destroy contraption that already works, not a step back, just effort comes to a waste. and that surely will get players angry.
Bro just look up a flying machine tutorial for bedrock and boom, problem solved
Actual Explanation
Java runs on a single thread. Everything has an order of execution that is predictable. This is slower, and doesn’t scale well since CPU’s keep getting more Cores, but not higher Clock Speeds
Bedrock runs on multiple threads. Everything gets executed in parallel, with no predictable execution
This is faster, and scales better with multiple Cores, but leads to problems like this, and also desync issues
Bc bedrock is bad
Just one of those weird quirks of BE
The 2 stepper
If you want Java style redstone you can play Legacy Console edition. It’s the same coding language. Only problem is you won’t be getting any new updates and lots of features are missing.
Also to explain why the flying machine isn’t working, it’s because of one tick pulses. Java redstone processes slightly slower, so if you send a one tick pulse through a sticky piston it spits out its block. This is the main mechanic of flying machines. One tick pulses don’t work on bedrock, hence why your flying machine is a ping pong machine instead.
Makes me feel groovy
you are using java specific design, the same doesn’t work in bedrock because sticky pistons do not have the bug that sticky pistons skip animation cycle and end up teleporting block they are pushing when quick pulsed
[here is an example of impossible door done by bedrock editions 2 way flying machines](https://www.reddit.com/r/redstone/s/ZDOhQ6GSzl)
why are you complaining, it’s just learning tango
“their tongues fought for dominance”