P: If a 'multiply' layer is at the top of my layer stack, moving a layer beneath it doesn't work

I'm getting this exact same issue that @chrisell99 has been describing and turning off GPU compositing worked for me. Cheers guys!

@Mark.Dahm Aha - yeah that fixed it. I'd actually been into the performance prefs before and tried disabling "multithreaded compositing" and it made no difference. I didn't go down into the GPU advanced settings. 

At least I have a workaround now but that's definitely some weirdo bug that could do with fixing. Thanks!

@Mark.Dahm 

It is still happening here with v25.0 using an RTX3090 24GB VRAM and Studio driver 531.61*

Sames steps as earlier to replicate it :

Create an 8 bit RGB file (must be 8 bit - the glitch does not happen in 16 bit), 512x512 px, with just 3 layers :

Lower layer : Background filled with 50% grey,

Middle layer Text

Upper Layer filled with a light grey set to multiply.

Moving the text layer around caused on screen glitches.

*I also updated the GPU driver to the latest Studio driver which is 546.01 released today using a clean install. The issue still remains.

Dave

I figured a video is as good as anything - there's audio narration on here explaining it too. @Mark.Dahm 

Also it's not limited to dragging layers around - ANYTHING I do on a lower layer causes this. For example if I marquee a section of a lower layer and fill it with a colour, it fills partially white until I either hide and unhide the layer, or do it with the multiply layer turned off.

<edited into above reply>

@davescm was able to replicate it in his later post. I've reverted to v24.5 for the time being as it's the only way I can get work done. It's basically every image I have - I do a lot of videogame work and all my textures are stored as 8bit RGB. They all work great in v24.5 but once I go higher than that, I get this compositing error which makes it all but impossible to use.

In v24.5 the document status indicator does say D3D12

It's worth noting that between the start of this thread and now, I've swapped out graphics cards and it still happens. It also happens on the machines in my office across various cards (where we have tens of thousands of textures that are all 8bit RGB). The only way to get rid of it is to revert to v24.5 or earlier versions of Photoshop.

Yes - new documents or existing documents. Anything that is an 8bit RGB doc and it does it.

@chrisell99 

I am not able to replicate the issue on my Windows box; as Dave mentioned, it does look like the GPU is pooping out; one certain way to confirm is to switch the document status indicator to GPU Mode and make sure that it says D3D12; if it says anything else, then the document is not working.

Do any other documents misbehave like this? If you create a new document of the same dimensions, and copy/paste everything into that, does that work?

@CShubert  <-- tagging also to try to get some attention on this