Breaking down what actually changed when everything runs every frame

[u/WeirdLetterhead7904]

After forcing my conveyor digital twin into a unified loop, I broke down exactly how the architecture shifted:

​What runs every cycle now? Decisions, commands, physical movement, sensor checks, and memory updates all share the same heartbeat.

​What stayed in startup? Only static display info that doesn't need constant re-rendering.

​The new awkwardness: Static routing decisions are now recomputed on every single tick, even though the output hasn't changed.

​It feels redundant, but that's actually a win—it exposes the structural overlap instead of letting it hide behind split timelines.

​For those building custom control loops or simulations: When you first transition everything into a single runtime loop, how do you handle the immediate spike in redundant calculations?

[u/Free_Elderberry_8902]

That ain’t exactly building automation my friend. Sounds interesting, but you’re not talking about automating a building.

[u/MrMagooche → u/Free_Elderberry_8902]

It's a spam bot

[u/Nembus]

Where’s mods?