Hello,

I just came across some strange behavior in Krita with the last couple of git builds. I do not know if it is due to the Nvidia driver update, or it had to do with the original file was an .ora file before it was saved as a .kra file, but if I am zoomed in at 200%, or higher, and rotate the canvas the whole image/drawing is blacked out. I only does it on the center of the entire image and it does it at angled degrees; vertical and horizontal the black box disappears. I updated my version of Krita, but it still does it.

Another issue that I found, was when I re-positioned some of my dockers to other sides of my work space, they lagged so bad when moving them... really bad! I have to make the cursor move super slow for it to work. If I moved it to fast, it would barely move after it would disappear for a few seconds. I do not remember having this issue in previous builds, I only noticed it doing this regularly with my canvases in cascade mode when I would try to scale and move them around. This does not have to do with my computer, kwin, or KDE Plasma, it has to do with Krita.

Krita version 4.0.0 -pre-alpha (git fcef2a6)

Thanks.

so... it doesn't happen with 3.2?

Because we changed nearly nothing to the openGL code beyond making sure it won't crash if there's only openGL 2 available...

I am not sure, I just use the git version. It is strange because it does not black out with a fresh canvas, only the one that was originally from a .ora file, or made with an older version of Krita.
With moving the subwindows/dockers it has been doing this for a while now with the releases; it seems to be getting worse.

So I just downloaded the 3.2.1 app-image version of Krita and it blacks out the image when rotating at 200% and higher. Moving the dockers is the same slow behavior as well.

gbear, can you paste the information in help->show system information for bugrapports?

That way we can see which driver is causing this at the very least...

I didn't notice that option before.

Code: Select all

Krita
  Version: 4.0.0-pre-alpha (git d8f07d5)

OS Information
  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.9.8-gentoo
  Pretty Productname: Gentoo/Linux
  Product Type: gentoo
  Product Version: unknown

OpenGL Info
  Vendor:  NVIDIA Corporation
  Renderer:  "GeForce GTX 980 Ti/PCIe/SSE2"
  Version:  4.5.0 NVIDIA 384.59
  Shading language:  4.50 NVIDIA
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile  2)
  Current format:    QSurfaceFormat(version 4.5, options QFlags(0x4), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 0, profile  2)
     Version: 4.5
     Supports deprecated functions true

Hm, that's the same driver I use for my nvidia card on my desktop:

OpenGL Info
Vendor: NVIDIA Corporation
Renderer: Quadro K620/PCIe/SSE2
Version: 4.5.0 NVIDIA 384.59
Shading language: 4.50 NVIDIA
Version: 4.5
Supports deprecated functions: true

So, it's not just the driver. The description sounds like the card/driver are kicking out textures. We've seen that before with the preview for the transform tool, which at high zoom levels also became too big for, in this case, the AMD gpu's memory. I've never heard of that affecting the dockers as well.

Yeah it is strange that the UI is tanked when my brushes run well.
One thing that I forgot to add was, I use the brush out line, when I am painting with the preset and lift the pen, the outline will blow up to full screen size for a split second, then return to regular size. It does it randomly with any of the presets. Nothing that affects my painting, just glitchy behavior.

Would you like me to do a screen capture and turn on logging to help to figure out why Krita is acting this way?