Closed Pouf842 closed 7 years ago
Hm. This doesn't work for me - can you post a screenshot with the memory included?
Sure :
Hrm, that screenshot is of a different (much faster) solution. I tried yours and it ran out of time for me - can you send a screenshot of the slower solution (from the first screenshot) setting memory correctly?
Yeah, sorry, I've tried to beat the ticks ideal in between. My bad.
But, now when I come back to the old solution, it is indeed too slow...
My only guess is that a bug made the time limit not respected by the tests, because I'm sure the solution worked, I had the finish screen.
I'll try and erase my save and redo the same solution in a first run. Maybe the bug will occur again...
Before erasing your save, try fiddling around with the test you're looking at?
E.g., start on test 2, 25, 26, 50...
Ok, I've made a new profile and get to that level again, and did the exact same solution. I now have a 13 modules/32 tick solution, which is fast enough :
You can see the 32 at the bottom behind the finish screen.
Now, when I've passed the final video sequence and back to the level, my solution is now at 34 ticks, and therefore too slow.
Edit : and after that, by simply erasing the solution and making it from scratch, I come to 32 ticks again. Quitting the level and reloading it makes it 34 ticks again. It seems that the maths are made different wethear you load the solution or you build it from scratch.
That's seriously weird. Will investigate.
Thanks for finding this!
By 'made a new profile', do you actually mean you started from the beginning of the game and got back to this puzzle that quickly, or did you just erase the save for this puzzle or something like that?
Exactly, I've quit the game, copied the save files from the old profile folder to the new one, erased Delay-CPU save in the new one, start the game, and went through all levels, loading the solutions and simply validating until I got to Delay-CPU. There, I built the same solution from scratch, and voila.
But again, you just have to empty the level, and redo it from scratch.
OK, that should be enough for me to replicate the problem, hopefully. I'll get back to you once I have a look at it.
Ohhhhh. Figured it out. The delay for the input/output selectors doesn't change correctly when you edit them; not until you reload the level.
Fun bug!
"why does the delay for input/output selectors vary by size?"
"it seemed like a good idea at the time"
I'm afraid this bug may have induced some ticks "Par" I've submitted to you... Gotta check'em all.
Yeah, good point. I check the tick-pars you send me before I put them in game, but I could've run into the same bug while checking!
Core bug fixed in 4c1e35f4.
puzz-Delay CPU.zip