FIXED: [2022.33910 Win10 22H2] Blob Track CHOP loses blob0 forever when it 'dies'

Here’s a .tox exhibiting the problem.
base_blob0_bug.tox (1.3 KB)


If the example or message was somehow too cryptic, let it run for a few seconds while observing the blobtrack CHOP. At some point, blob0 will deactivate and remain in that state for the rest of the run. You can increase the blob count to 11, 12 or more to see that there are more blobs to find, and in all cases blob0 ‘dies’ after a while.

This will be fixed in builds 2022.34240 and later. Thanks for the report.

1 Like