-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 16/04/2014 17:30, IOhannes m zmölnig a écrit :
On 04/16/2014 11:49 AM, Jack wrote:
Hmm, people who used to use FSAA message to manage antialiasing for their fonts, will have something different in the 3D scene.
yes they will, but the question is, whether this hurts. openGL never guarantees pixel-accurate rendering across implementations, so (in theory) your scene can look differently when you upgrade your drivers. and FSAA never consistently worked across all platforms.
Yep, that's true.
And people who applied texture on their fonts, won't be able to apply them.
yes. that's probably more of a problem. one possibility would be to detect whether there is a texture in the gemlist, and if so, fall back to the old behaviour (at least in some default "autotexture" mode)
another would be to allow configuring the default [text3d] backend via gem.conf.
Don't know. For me, if you can't antialiased all geos, why you particulary want to antialiased the text3d object (even if I know why). There is the same problem on curve, small square, small circle, etc. Then, you have several possibilties working on all geos (with different result) : - - FSAA - - shaders - - upsampling
So for me it is important to have [antialias 0( as default.
how many of your patches would be broken?
0 % :) ++
Jack
gfmdars IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev