Severe graphics corruption on windows since v14.2
Hi there,
I was wondering if I am the only one suffering from severe viewer/export image corruption since v14.2? Up until v14.1 everything was fine, no issues with the viewer image or with the exported images, but since v14.2, hardware acceleration is totally unuseable. Only the first 2/3 minutes after start-up are ok. but as soon as I start to do anything of meaning, the zooming in/out of the images starts producing psychedelic colors/patterns, and exported images are nothing but a scramble of dots, patterns and colors, with not a trace of the real image.
I opened a support case, followed all suggestions and instructions, and nothing helped, but as soon as I re-installed v14.1, all problems were gone. This is on a fairly new Windows 10 PC with a ryzen 7 processor and a nvidia GTX1650 graphics card.
I tested beta v14.3, and it was just as bad. I am wondering if I will be left stranded with v14.1. Does anyone have similar experiences? Of course I can disable hardware acceleration for both viewing and exporting, but that does not help with quickly zooming in/out when working on layers, it gets sluggish on my 4K display. A restart fixes things...... for about 2/3 minutes...
I have zero other issues with OpenCL, Photoshop works smooth and without a trace of artifacts. I wonder how CO1 manages to produce such a total mess of graphics corruption, I simply have never seen any other program making such a mess of graphics. What on earth can be the reason behind that?
Chris
-
If turning Hardware acceleration off eliminates the image corruption problem it might suggest that there is some form of anomaly with the GPU drivers.
Sometimes that can be resolved by updating the drivers or, on rare occasions, reverting to older versions.
If a restart resolves things for a few minutes one might wonder about some fsort of memory management issue, perhaps within the GPU.
I know nothing about Ryzen processors. Does that, like Intel, have a built-in Software GPU?
Did the activities of the Support Case also involve assessing the log file information produced during C1 start up - in particular the checking of the available GPU facilities and generating the kernels that C1 creates in order to make use of the GPU(s)?
It might be worth comparing the log files for a V14.1 start up and a V14.2 startup to see what differences may be apparent.
0 -
I would accept the possibility of a driver issue, but I have a clean install of the latest nvidia driver, and as said, all versions befóre 14.2 worked fine and even now v14.1 works fine without a hint of graphics corruption. CO1 changed something in v14.2, that has messed up the handling of graphics memory, in the first beta of 14.2 I even had freezes and could not close the program, in taskmanager the energy use of the graphics card was deep red, very high, and I had to force quit.
It is so disappointing to have CO1 working fine all year (it used to be different in the past) only to see some véry bad programming totally mess up graphics use. I normally am not impatient, but seeing beta 14.3 being just as bad or even worse is really depressing. Can they not master the art of software programming at PhaseOne. It feels like they are just doing something, randomly messing up things instead of robust programming.0 -
O, and yes, of course I sent all my logs and samples of the graphics corruption. I can only hope they fix it...
0 -
Christiaan,
Sometimes new drivers are not the best option.
For what it is worth I have not, so far, seen the problems you mention when testing V21 on my Intel based system with a combination of Intel Software GPU and nVidia T2000.
I will see if I can force something to go wrong!
0 -
I know, but it's hard to blame my system or drivers when everything worked more than fine with CO1 until I installed v14.2.....
0 -
ich habe das selbe Problem.
Wie kann ich den Fehler beheben
HP Zbook X2G4
Prozessor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz 1.99 GHz
Installierter RAM 32,0 GB
Systemtyp 64-Bit-Betriebssystem, x64-basierter Prozessor
Stift- und Toucheingabe Unterstützung der Stift- und Toucheingabe mit 10 Touchpunkten0 -
I solved this issue by doing a clean install of the latest nvidia graphics driver, but the game-ready version.
I used the studio version for 10bit color in photoshop, but it appears that the game-ready version now also supports 10bit color.
I have a second (older) PC with the same GTX1650 graphics card, but with an intel processor instead of AMD Ryzen, and that PC appeared to work just fine after testing, ALSO with the studio driver. CO1 support did acknowledge that "something changed with OpenCL going from version 14.1 to 14.2", so that apparently set the studio driver off to get out of control.
Conclusion: OpenCL is a mystery to me, but for now, things have luckily been solved.
0
投稿コメントは受け付けていません。
コメント
7件のコメント