Created attachment 142484 [details] 3 layers doc This has only been tested on macOS on git (804225bc51e9) STEPS TO REPRODUCE 1. Move any layer stack that contains a layer with a transform mask(Warp, cage, liquify or Mesh) in it OBSERVED RESULT Layer with the transform mask will disppear for a few moments (up to 6 seconds) Attached image for quick test. Since loading the content takes up to 6 seconds to appear, after it shows, move either of the paint layers to make the content dissapear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I cannot reproduce this with master at 958a8d7aafd7ac6f693f677cc5be052d60a85b07
Using the Jun 28 5.2.0-prealpha (git 930da6975e) appimage on Debian 10, if I move either of the paint layers, I see no disappearance of any part of the image. If I turn off the visibility of the transform mask then I see the not-transformed image immediately. If I then turn it back on again, the image disappears then the mask shows activity for a very short time and there ia a delay of about four seconds until I see the transformed image.
Still happens to me. On windows 10. Both 5.1.2 and 5.2.0-beta2. The transform mask is *extremely* unstable to a point it's unusable when Warp, Cage or Liquify is involved. The whole layer can just disappear after toggling the transform mask's visibility. It can also partially disappear, leaving the file in an weird state. I even renewed my PS license today for this...
From what I can tell, this is only reproducible when the transform preview set to "Fast". The issue doesn't occur with "Accurate" preview. In that sense, I can confirm this. Also, it occurs regardless if the user is using a transform layer or doing a raw transform. In general, the "Fast" mode is prone to disappearance through a variety of methods. The most common method of making a Fast transform disappear for a short time is by undoing or redoing a Fast transform, which produces an annoying flicker in the case of transform comparisons. It's a shame, as Accurate mode's current performance is very impractical for large transformations and liquifys.
Remove triaged keyword from CONFIRMED bugs