Hans-Christoph Steiner a écrit :
Then what about [FSAA 3(, [FSAA -1(, etc. I think a warning wouldn't hurt, you could add in 5 as a supported value.
i don't think there is any value that is not suported somewhere.
Another option is to have a [antialiasing 0/1( message with just gives a default AA level for people who don't want to think about it.
arggggghhhhhhhh. this is ugly. there is no default. everything is in balance from performance to quality.
c
.hc
On Mar 24, 2009, at 3:47 AM, cyrille henry wrote:
hello,
after few month without antialiasing, i realized that this as changed on new nvidia driver. FSAA 4 is no more valid. you should use FSAA 5 for the same effect (really can't understand nvidia logic).
So, no check / no warning is the best. C
Hans-Christoph Steiner a écrit :
I am documenting the FSAA message to the [gemwin]. It seems to me that it only takes the values 0,2,4,8. There is a check in the C++ code, but its currently a little bit useless: void gemwin :: fsaaMess(int value) { if (value == 2 || value == 4 || value == 8){ GemMan :: fsaa = value; } else{ GemMan :: fsaa = value; } } It seems to me that it should issue a warning if 'value' is not a useful value. Also, [FSAA 0( would be an intuitive way to turn off FSAA, it seems to work. .hc
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr. _______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin