Healing glitch for C1 15.3.0.109
Is anyone having the same issue?
When adding healing brushes I did notice a glitch in the image area was displaying a yellow/gray pattern over the photo.
- After adding more healing retouches the image stays with the pattern and I can't work on the image
- I did hide the layer (unchecked the box to hide the healings), and I was able to see the image
- If I show the layer, then the patter can be seen again
- I did restart C1 a couple of times and nothing, also tried restarting my computer
In order to fix it, I had to disable in settings the Hardware Acceleration for the display
My computer is an intel MacBook pro late 2013
regards
-
Seems that on old computer, using the HW can be counter-productive.
0 -
I'm experiencing the same issue with the display only I didn't add any brushes/layers - just selecting a new image causes a long flash with the same focus grid shown in your screen shot. I too, turned off HW acceleration for the display.
UPDATE: Upon Export from RAW to JPEG, some images are unusable. They are either fully or partially covered by the focus grid. Using MacBook Pro late 2013 16GB 2.6GHz Quad-Core Intel Core i7 NVIDIA GeForce GT 750M 2 GB
1 -
Well that sucks!
Seems then "auto" option for Hardware Acceleration is not working at all?
You may need to turn off the hardware acceleration for both options (display and processing)1 -
Thanks for the idea Ramon. I turned off HW acceleration for both display AND processing. That seems to have fixed the issue exporting images. That should keep me working for now. Thank you! Jim
1 -
One more follow up. I read through the support article and followed the steps to delete the contents of ImageCore in hopes of being able to restart HW acceleration. In short, it did not work. I've turned off HW acceleration for both display and processing and am able to export images without artifacts (so far). C1does seem to execute slightly more quickly with HW acceleration turned off. Since my MacBook meets/exceeds C1 specifications, this appears to be a bug. Thanks again Ramon!
1 -
No problem James!
0
Post is closed for comments.
Comments
6 comments