Possible resolution in verve 0.99t3

Hi there,

just played a bit with the new "crop - extend" function via SHIFT F2.
Would like to see others have same results.

Here are my results :
13999x500 - max 4 Layers - < 7.000.000 pixel ATTENTION!! Exception_Access_Violation on save.
6925x1036 - max 3 Layers - < 7.150.000 pixel ATTENTION!! Exception_Access_Violation on save.
etc.

As long I tried around below 7.000.000 pixels it worked fine for drawing.
I never had performance issues. Fluid was really fluid. No lags in drawing.
But it's not save able as a verve project.

For saving without crash it had to be less than 4.000.000 pixels.

Is that somehow same on your machines??

[Taron]

I haven't even dared!
But the saving is weird...even my careful approach now seems to blow the bank compression at such tremendous resolutions. Verve- thus far- is not meant to do building-size print resolutions.
I can, however, try to break up the image a bit more, if it gets to such madness, haha...
I'll have a look at that eventually, just not right now. I still haven't done GLerror checking, which should at least prevent resolutions too high for display memory.

Good testing, though! I will definitely take care of the saving crashes!

Verve- thus far- is not meant to do building-size print resolutions.

...

2k x 2k with multiple layers does work fairly well for me ... Beyond that, things get wacky/crashy
It's quite amazing now to dive into actual 1080p full screen resolution, though ... i am totally cool with that actually

"WEEEEEEEEEEE 1080PPPppppppppppppppppppppppppp ... "

1080P?
phhh - verve can do a hell more
My tests ended as following for today:

Keep resolution below 4.000.000 like ie 3900x900 and you are almost on save side.
I was able to save this with 7! layers, 8 layers crashed.
This is freaking awesome.

3840x1080 - double HD width possible incl. 3 Layers. (saving png or jpeg also possible with 6 Layers)

10000x700 I was able to save as jpg and png but not as vrv. Switching to high res with "h" makes everything black, but switching back is possible.

One thing I am thrilled about verve is it's stability.
Now, with free resolution option, one should take care a bit.
Specially you won't see that you can't save it untill it's too late.
Interesting is, that performance on a, as pilou called it "NASA config " is no problem at all.

It is always running fluently which means the potential is great.

Thanks taron!

[Taron]

1080, by the way. The "p" stance for progressive, I think, referring to replay property to show full frames rather than interlaced 1080i. Thus it's just 1080eeeeeeeeeeeeeeeeeeeeeeeeeeeee.......

And, yeah, I'm just thrilled I can go fullscreen on my little monster here at 2560x1600 and it's pretty much fluent under most circumstances.

I really gotta check what's up with the saving again, though. It's a bit weird, if the number of layers causes a problem there, because now I'd have imagined it would only be if a single layer is too big for a bank. Weird.

Thus it's just 1080eeeeeeeeeeeeeeeeeeeeeeeeeeeee.......

Just meant to say that being able to set Verve to my native screen resolution (1920x1080) now and have it run this smooth really is all i ask for ... i am a very happy panda
... Though, once we are at tileable texture painting we gotta talk about 4k x 4k again

Hey, for things like this ... how about a shortcut to display some real time diagnostics? Framerate, GPU memory usage, ect. (The one between [Esc.] and [Tab] maybe?)
So far, the indications i go by are GPU fan noise and V-Sync issues when i go too crazy with resolutions ... and crashes of course

Aaaaand speaking of fullscreen, ... (this may well again is a problem caused by my dual monitor setup) when i hit [F3], i do get a Windows frame around Verve, only without the window bar on top.
Windowed Fullscreen / [F3] Fullscreen

[Taron]

Yeeeehh, that's a weird one. Not sure why I'm having such a hard time getting rid of that stupid border. I've done that a few times with other things like little games and never had an issue. Gotta check some more into that again.
There's also a slight oversight with loading an image while being in fullscreen. It resizes the window to the image, but leaves the top bar off, haha... ...but that's also something I can change now that I couldn't earlier. So....things are looking brighter!