wjdrijfhout
Member
I know this issue has been reported before.
Solutions for Windows are published and suggestions that MacOS would not have a problem (anymore).
However, the problem is here still very present on Intel MacOS.
After upgrading to 1.8.9-2 it started, when re-installing 1.8.9-1 it's gone, going back to 1.8.9-2 it started again.
See screenshots of the versions I'm using.
Noticed that 1.8.9-1 mentions OpenGL is active, in 1.8.9-2 it doesn't say this, instead it mentions GPU acceleration enabled. Still when checking with 'echo $QSG_RHI_BACKEND', it returns 'OpenGL'.
The problem occurs on my Mac Pro 2019 (16-core, 160GB RAM, AMD Radeon Pro W5700X 16 GB).
No problems on my MacBook Pro M2 Max
It makes it pretty impossible to work. You never know where you are on the image, or when you're at the edge of it. So applying masks, cloning, minimising, grabbing preview, etc, etc. is all hit and miss. I have abandoned 1.8.9-2 for now and re-installed 1.8.9-1
What can be done about this?
Best regards, Willem Jan.
Solutions for Windows are published and suggestions that MacOS would not have a problem (anymore).
However, the problem is here still very present on Intel MacOS.
After upgrading to 1.8.9-2 it started, when re-installing 1.8.9-1 it's gone, going back to 1.8.9-2 it started again.
See screenshots of the versions I'm using.
Noticed that 1.8.9-1 mentions OpenGL is active, in 1.8.9-2 it doesn't say this, instead it mentions GPU acceleration enabled. Still when checking with 'echo $QSG_RHI_BACKEND', it returns 'OpenGL'.
The problem occurs on my Mac Pro 2019 (16-core, 160GB RAM, AMD Radeon Pro W5700X 16 GB).
No problems on my MacBook Pro M2 Max
It makes it pretty impossible to work. You never know where you are on the image, or when you're at the edge of it. So applying masks, cloning, minimising, grabbing preview, etc, etc. is all hit and miss. I have abandoned 1.8.9-2 for now and re-installed 1.8.9-1
What can be done about this?
Best regards, Willem Jan.