This has never happened to me before the last update, but I have a critical bug where my files are displayed with strange patterns. There are no alpha channels or masks on the image layer, and the patterns are not visible in color channels.
If I duplicate the file, flatten the (one layer) image, and copy that layer back to the original, the problem is gone. So I'm a bit baffled.
The display problem goes away for things like the inspector window within unsharp mask. The problem is, I cannot perform tasks like dusting as it is.
I hope that is an easy revert of a recent change : /
file:
same file when resized:
If I duplicate the file, flatten the (one layer) image, and copy that layer back to the original, the problem is gone. So I'm a bit baffled.
The display problem goes away for things like the inspector window within unsharp mask. The problem is, I cannot perform tasks like dusting as it is.
I hope that is an easy revert of a recent change : /
file:
same file when resized:
Posted 3 years ago
Hello Chris,
I am using OSX 10.9.5 with a AMD Radeon HD 7950
It's the first time I've seen it happen, I've gone through 200 or so such files in the last few months (of similar dimension, bit depth and characteristics such as layer count, masks, etc.) I have not performed any system updates recently, so it's a bit bizzare that it appeared out of the blue.
I am using OSX 10.9.5 with a AMD Radeon HD 7950
It's the first time I've seen it happen, I've gone through 200 or so such files in the last few months (of similar dimension, bit depth and characteristics such as layer count, masks, etc.) I have not performed any system updates recently, so it's a bit bizzare that it appeared out of the blue.
Is the document 16 bit/channel?
Does it disappear if you convert to 8 bit/channel?
Does it disappear if you change the GPU mode in Photoshop to "Basic", then restart the app (Basic means it runs without shaders, and thus won't hit the shader bug)?
What you posted looks like the old shader bug (appeared on Windows a few years back, and was fixed back then as well) that we thought appeared in MacOS 10.10, but there were also driver updates in 10.9.x that could have introduced it as well.
Does it disappear if you convert to 8 bit/channel?
Does it disappear if you change the GPU mode in Photoshop to "Basic", then restart the app (Basic means it runs without shaders, and thus won't hit the shader bug)?
What you posted looks like the old shader bug (appeared on Windows a few years back, and was fixed back then as well) that we thought appeared in MacOS 10.10, but there were also driver updates in 10.9.x that could have introduced it as well.
It is indeed 16bit/channel
It does disappear if I convert to 8 bit/channel
It also does go away in Basic mode
*is there hidden documentation somewhere that lists what specifically the different modes entail in terms of performance gain?
It does disappear if I convert to 8 bit/channel
It also does go away in Basic mode
*is there hidden documentation somewhere that lists what specifically the different modes entail in terms of performance gain?
No, there is no good documentation for the GPU modes that I know of.
But you have confirmed that this is the same shader bug that we saw before on Windows, and have seen more recently in MacOS 10.10. We'll add this to the documentation on the bug for Apple.
But you have confirmed that this is the same shader bug that we saw before on Windows, and have seen more recently in MacOS 10.10. We'll add this to the documentation on the bug for Apple.
Hello Chris,
Any updates, this bug has stayed with me since, and I have it on three computers of entirely different configuration (one is an old mac pro running 10.10, the other is a new one with a hd7950 running 10.).
Any updates, this bug has stayed with me since, and I have it on three computers of entirely different configuration (one is an old mac pro running 10.10, the other is a new one with a hd7950 running 10.).
