CPU touching color does not always match GPU/Scratch 2

[Xeltalliv]

In 2017 (scratch 2) I made this project that scans a costume using touching color blocks and constructs a 3D level based on it. Scanning costume in the project is small, so scratch uses CPU collision.

Expected Behavior

Scratch 2, GPU collision of Scratch 3, unofficial alternative players like Forkphorus all produce the same correct result:

Actual Behavior

CPU collision which scratch uses in this case produces different incorrect results:

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to 'https://scratch.mit.edu/projects/137870287/'
2. Launch the project
3. Look around using arrow keys. The level was scanned incorrectly
4. Open browser console
5. Obtain vm object
6. Run vm.renderer.setUseGpuMode('ForceGPU')
7. Launch the project again
8. Look around using arrow keys. The level was scanned correctly

[adroitwhiz]

Probably resolved by #479