Krita screen becomes unresponsive - Still able to save and exit

Support and Advice General Questions
21

@AhabGreybeard: I just checked several things on your tip. The entry can be in kritadisplayrc files that use Direct3D, as well as in those that use OpenGL (possibly an artifact of the switch to OpenGL). But there are also OpenGL installations where this entry is missing. All installations with this entry work for me, as well as all without this entry, regardless of the selected renderer.

Aha, okay, as always I’m writing too slow.

@mommabear90: That is “interesting”, it stands on Angle BUT has OpenGL issues.
Before you go and delete the kritadisplayrc can you please try the following:
Because it is such a new machine, can you change the renderer to OpenGL? If it does not work, you can go back without problems.

Michelist

1 Like
22

I have no idea what it does :blush:

2 Likes
23

Same here.

Michelist

2 Likes
24

i wish i would have seen this before! I deleted it already. I had to leave for a bit so i didnt see it right away.

25

ANGLE is a translator between Windows’s preferred Direct3D and Krita’s use of OpenGL, so it’s not unexpected.

Turning off Canvas Graphics Acceleration should avoid OpenGL canvas issues, though you may lose some features.
As for why it might stop working I couldn’t guess, but Help->System information for bug reports has some OpenGL info which could be useful.

Edit: I’ve found that the error message in the screenshot is coming from QtQuick’s QQuickWindowPrivate::contextCreationFailureMessage().

2 Likes
26

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.