Hello.

I've recently got into pixel art in Gimp, but the wrap around ability in Krita for tiling seemed really useful so I thought I'd give it a go.

Unfortunately it hasn't been smooth sailing.

Every now and then I'd find the canvas would be all in black if OpenGL was enabled. I can still draw, but I can only see what I've done once I turn OpenGL off again.

I figured it was a driver problem and so spent a couple of days reinstalling and messing around with updating drivers, trying unofficial drivers (I have a dual switchable gfx laptop and getting the right drivers can be tricky)...

No luck.

Then I installed ubuntu as a dual boot back on my laptop to see if the linux version would work any better...

No luck.

Finally I noticed that actually, OpenGL does work on both ubuntu and windows 7, but only with certain sizes of image canvas...

Some luck?

Essentially, the bigger canvas sizes work fine, but below a certain threshold, things start getting very strange...
For example in ubuntu afaict as long as the height is 484 or more pixels then whatever the width of the image, opengl works fine. If the height is below that, then the width has to be quite big to work...
On windows the same thing seems to apply even though the exact numbers are different.

TLDR If the size of the image canvas (or some combination of width & height) is too small, enabling opengl makes my canvas black, and I can't see what I'm doing.

Of course creating pixel art tiles, means I want very small image size...

So does anyone know what on earth is going on here, and how I can fix this problem (I'm quite emotionally invested now ) ?!

Thanks in advance for any help!

Ah... I know that bug. It _should_ be fixed in the current development versions of Krita, either the Windows download or the Krita Lime package for Ubuntu. Unfortunately, I haven't managed to backport it to 2.8 yet.

Thanks a lot for the quick reply, and thanks for what looks like great software (haven't really had the chance to use it much yet )

Good to know that it is a known and fixed bug...

So... not to be impertinent or anything, but what kind of time frame are we looking at before the next update?!

For 2.8, it's a bit uncertain. I need to find time to backport and test the fix, then make new Windows builds and we'd need to do a new release. For what will be 2.9, you can already have the fix: either use the windows development builds from files.kde.org or the Krita Lime repo for *buntu. In general, developments are pretty much as stable as releases -- with the occasional snafu.

Sweet, 2.9 dev build it is,

Thanks again!