I'm wondering why my fullscreen is running so damn fast:
308x334 With pix-doubling in small screen:
44fps
848x480 With pix-doubling on full screen
55fps
on
/\/\y573rY pr3527
I'll only tell you that it has a convo filter two buffersaves and two simple DM's. Whay could be causing this speed? I'm quite interested.
Really Fast Fullscreen
12 posts
maybe because it has no render?
So damn mystery..
oh...uh..
oh...uh..
Re: Really Fast Fullscreen
is that really an available fullscreen res? you must have some weird gfx card...
[and you really set your fullscreen res from the dropdown menu in the fullscreen settings, and don't set a windowed size and then simply click on fullscreen? 😕 just sth that came to my mind...]
GC
Originally posted by JFASI🤪
848x480 With pix-doubling on full screen
is that really an available fullscreen res? you must have some weird gfx card...
[and you really set your fullscreen res from the dropdown menu in the fullscreen settings, and don't set a windowed size and then simply click on fullscreen? 😕 just sth that came to my mind...]
GC
Aaargh!!! Black and whiiiiiite!!!
I'll exclude the lineup for evil reasons. Ok, so it did drop a tad, but still, it's really fast. It does have a clear screen, and the convofilter is kinda beefed, but still, why the big difference?
I'll exclude the lineup for evil reasons. Ok, so it did drop a tad, but still, it's really fast. It does have a clear screen, and the convofilter is kinda beefed, but still, why the big difference?
probably has to do with bpp? 848x480 can be divided more "efficiently" by 32 or 16.. just a guess and i can't give you the tech mumbojumbo 🙂
You mean AVS draws the screen in sectors?
In full-screen mode, Windows can give AVS direct access to the screen and doesn't need to worry about any of that object and windowing stuff. That could account for some FPS increase, but probably not a 25% increase!
So let's look at those resolutions again...
Because of the effect of pixel doubling, the resolutions are actually a little misleading. 848x480 with pixel doubling is treated like 424x240, which is 101760 pixels. 308x334 is 102872 pixels. As a result, AVS actually has more work to do in the windowed resolution, because it's a slightly larger screen (in terms of number of pixels). When you combine that with a couple of convolution filters, that could explain most of your FPS difference.
Sort of interesting how that works, isn't it?
So let's look at those resolutions again...
Because of the effect of pixel doubling, the resolutions are actually a little misleading. 848x480 with pixel doubling is treated like 424x240, which is 101760 pixels. 308x334 is 102872 pixels. As a result, AVS actually has more work to do in the windowed resolution, because it's a slightly larger screen (in terms of number of pixels). When you combine that with a couple of convolution filters, that could explain most of your FPS difference.
Sort of interesting how that works, isn't it?
but he pxl-doubled in windowed mode too!
still confusing...
still confusing...
Yes, and when you turn that on, the AVS editor shows you the halved resolution (in this case, 308x334), not the actual resolution (which would be 616x668).
aaah, i get it!
now it's obvious.
well done sherlock!
now it's obvious.
well done sherlock!
Wow. That does explain a lot.