Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Screen and mask issues

NN181837UL2
C1 v 10:
The screen often blacks out or explodes in multi color patches when making some adjustments or painting masks. Irregulary, sometimes C1 works without these problems. Reason?

Yesterday the mask paining stopped work, you can edit old masks (but not expand them/paint them larger). Restarting C1 or computer doesn´t help.

My old C1 v9 works well, but I can´t get access to adjustments made in v 10.
0

Comments

5 comments

Date Votes
  • Permanently deleted user
    Same issue here with masks (black and multicolor masks). C1 10.0.2. Only when openCl is turned on I think. I opened a support case.
    0
  • NN181837UL2
    I have solved the mask paint problem temporarily by re-installing v 10.0.1.23. However, the irregular issue with screen updating remains.
    0
  • John Gambriel
    I am experiencing the same thing. Some of my develops have also replicated the blackout/multicolor screen spasms. Going back into C1 (10.0.2.😎 and reprocessing usually produces a good develop. I have also noticed that performance hits the floor when a conversion is going on in the background. Overall performance is noticeably slower in this release. Focus masks do disappear while adjusting, so OpenGL does appear to be working properly. Newest Nvidia drivers are installed. Running Core i7-2600 CPU @ 3.4Ghz; 16GB RAM; 64bit Windows 10 (up-to-date patches); NVIDIA GeForce GT 730 (378.92-03/16/17).
    0
  • SFA
    It might be worth try to step back one or two driver releases for the GPU.

    The latest releases are not always the most appropriate, or so I have found.


    Grant
    0
  • Luke Miller
    I've experienced similar issues at times. The fix was installing the latest graphic driver update. It seems to occur after a C1 update. My suspicion is that some sort of interaction occurs between the C1 installation process and the graphics driver, which results in the issues I've experienced. Updating the driver corrects the problem. If my suspicions are correct - rolling back the driver would do the same although I haven't tried it.
    0

Post is closed for comments.