#Two issues of Masking Time
1 messages · Page 1 of 1 (latest)
There's another way the level can be cheesed:
You can set the Output component to 2-bits wide and just connect Input to Output and enable both ... 
I don't think that's cheese, that's just building specific hardware to solve the problem
It's the same score and principle as the best score, just using fewer components.
Well, yeah, 0 gates 🤷
I fixed issue 2. for the next patch but I couldn't reproduce 1.
Maybe its fixed
This fails, but I don't see the reported -2.
In version 2.1.91 on Windows.
I mean I do see -2 if the display mode is set to -1, but that's not causing the test failure.
I observed -2 by modifying test.si:
if output != input % 4 {
set_error(`{input} mod 4 is {input % 4} but current output is {output}.`)
return fail
}
Does it work normally if the bit maker replaced with 4-bit one? If so, this is possibly the same bug of bad higher bits: https://discord.com/channels/828292123936948244/1496603665006592101
Yes. Seems the same issue.
Has the patch been released? It appears that neither of the issues has been fixed in v2.1.91.
Edit: I just realized that v2.1.91 came out a few hours before your comment, so let's wait for the next patch.
This still happens in 2.1.94
The problem is when 2-bit maker is connected to output, it has garbage in upper bits. I suspect the root of issue is the same as here: https://discord.com/channels/828292123936948244/1498320131070230670