Turing-Complete-Game
[Bug]: Register and Counter outputing a tick late
Discord Thread
https://discord.com/channels/828292123936948244/1272355713481572353
What happened?
Version 0.1117 beta OS: Linux Distro: Manjaro
When writing a value to the register, the output updates 2 ticks after, not 1 like its supposed to
This happens where or not the first tick is - or 0 and on after a factory reset
I constructed this build in the component factory:
I then clicked the tick button 6 times, to make sure it wasn't the - state messing it up, the tick counter now read 5
Tick 5:
Tick 6:
Tick 7:
As you can see, on tick 6 after writing 72 to the register the tick before, the register now holds 72, but the output is still zero Only a tick later, on tick 7, does the output update, 2 ticks after I was writing the input
This holds for changing the write value every tick, the output value is always 2 ticks after its input, the register display showing the value in between
Ive noticed the counter also outputs its number a tick late, unless the display is supposed to show the next number its going to output
Version
0.1117 beta
What OSes are you seeing the problem on?
Linux
Relevant debug.log output, search next to the exectuable
No response
I see you did not read the pinned post... You should not share your save folder publicly without editing out the token.
just deleted that comment, as someone explained to me on discord I did read the pinned post on discord, I assumed "PM me your save" meant just share it in regards to the bug report, I didn't read anywhere it saying it includes private info Rereading it seems theres a line I missed, my bad
If you edit the input on tick 5, you aren't actually changing tick 5, you are just setting up what will happen on tick 6. So on tick 6 the value is stored in the register and on tick 7 it is output. Granted you changed the inputs on tick 5, I don't see any issue here. I need to format my Linux machine but I confirmed it works as it should on macos. Closing for now
