On Apr 6, 2006, at 3:25 PM, chris clepper wrote:
We place no limitations of this kind when it comes to dealing with
the GPU. Anything like this is very probably going to be a driver
issue.
...to enhance chris' comments, I'd say it's more a VRAM issue, too:
anytime you do FSAA, the gpu is essentially making multiple renders
of the screen, then averaging them...so, if you make a 1200x1000
window, multiply that by 32, then multiply that by two screens, then
multiply that by the level of anti-aliasing...so, just doing it once
as described above, you're already looking at about 64MB's worth of
VRAM needed!
...beyond that, cards and their driver support would be the
limitation...
jamie
On 4/6/06, timon timon@sosolimited.com wrote: Hi, I have found some issues with screen sizes when sending FSAA number to gemwin. When I send any FSAA number (anything from 2-24) on a G5 running two screens i am not able to generate a window higher 1200 x 1000 . Sending 0 lets me make as big of a window as 3800x1200. But thats without any anti aliasing, and since Im working with text objects it looks a bit pre-dated. Is there anywhere I can find some information about optimising the FSAA while having big gem windows?
Its odd that the antialiasing affects the screen size. In older Gem versions this has not been an issue (sorry, dont mean to complain).