When a resize happens to an atlas image 3 commands are issued. Causing the bug above to appear. Two commands to zero the space. One for the new area on the right, and another for the new area on the bottom. A third is then to copy the old image onto the new image. Removing one of the zero commands stops the artifacts from appearing, but then the image is no longer properly zero'd.
A workaround is to zero the entire image and then copy the new image on top which is slightly slower reducing the commands needed to only two which would prevent Basalt from running into this bug.
On linux where this bug doesn't seem to happen at least with amdgpu drivers:
An upstream issue seems to be causing this issue: https://github.com/vulkano-rs/vulkano/issues/1265
When a resize happens to an atlas image 3 commands are issued. Causing the bug above to appear. Two commands to zero the space. One for the new area on the right, and another for the new area on the bottom. A third is then to copy the old image onto the new image. Removing one of the zero commands stops the artifacts from appearing, but then the image is no longer properly zero'd.
A workaround is to zero the entire image and then copy the new image on top which is slightly slower reducing the commands needed to only two which would prevent Basalt from running into this bug.
On linux where this bug doesn't seem to happen at least with amdgpu drivers:
On windows where this bug is encountered: