Suggestions

[Taron]

New version is up! v.05

whatever you did....
its working

I still have a funky twitchy funky driver issue in my bootcamp
but even with that
I just saved and re-opened a 2000x3500 pix image ( may be able to squeeze even more oix in...ill see )
with my modest 1 gb of vram on nvidia 650m
up from 1440x2560 which was my previous limit
This is great!
yehaw!

Thanks you Taron!

[Taron]

AH yeah, I really hope you get that resolved with them twitches!
However, yep, if your card can handle it, there's kinda no real limit on the size now.
If it somehow did come to some trouble, I can alter my routine again, but I doubt it will be necessary.
RIght now I have a fixed split into 16 sections. I could go higher, of course, but I figure this should be ok. Considering what used to work, this would allow theoretically for something like 30000 by 30000 I think. But I wouldn't push that, hahahaha! Saving would take half a day, I'm afraid, hahaha!

So, yeah, for your normal print res work this should cut it just fine!

Extremely cool.
Could save and reopen a 6400x4000 picture .
But today, after restarting the computer it's not possible to open it again?
Export to png ended in a crash anyway.
4000x4000 did successfully export to png.
One Layer for sure - HQ is not possible.

Sometimes I see some numbers like 0.50000000 or 0.7500000000? Percent I thought first, but they are static.

[Taron]

Oh, that means you should download again, but it was just a cosmetic issue. I did a little test for rest pixels after any segmentation, you know.
So, download again.
However, if yours crashes, that's kind of interesting, especially because it worked before. Very strange.
Could you have had some other openGL apps open at the time of the crash? Could be a graphics memory thing, you know.

I'm sure there are still a few hickups to be expected, but the system is there!

Could realize A3 = 4961 x 3508 one layer no HQ.
Trying to get even higher.

Thanks a ton taron. That is monster cool

EDIT:
4999x4999 is possible to save but not to open again.

[Taron]

UGH, it's not entirely unlikely that that's a 32bit issue.
PFffff...ok, for those massive resolutions I may have to do either something really weird with memory blocks or wait until I go C++.
Dang...

[Taron]

Hmmm...I've uploaded a version that doesn't crash, BUT it also doesn't quite work either for that resolution. I'm almost certain it's a 32bit issue, but could be wrong. If my calculation makes any sense, a single color/alpha float buffer at 4999x4999 should have roughly 390Mb, bringing it well below any 32bit issue. I'm not sure...however, truncating the redundancy off of my material buffer made it not crash, so that makes me wonder, you know.
I could try to split the image during loading into as many texture sections and then paste them properly into the then created image buffers. It might possibly make some sense, but I'm puzzled by those troubles to begin with, considering my calculations. Sure, I'm using a few more buffers, including the canvas and then all the fluid stuff, including wet buffers and so on. It's likely that the one extra piece of texture buffer needed to load the image is too much for any conventional card?!
Well... let's be excited about the sizes that do work, which are still pretty high and a lot higher than they used to be, hehe...

It's such a big progress already and to be honest. 5000x5000 is a serious resolution for any graphic app here on my computer.
Verve still works smooth but I wouldn't work in this resolution because of multiple layers etc.

So maybe not for this screen one (screen 24*100 m) 24 millions pixels! (I am spectic about the sizes meters given)