[GEM-dev] anti-aliased [text3d]

[IOhannes m zmölnig]

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.


> 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.

> So for me it is important to have [antialias 0( as default.

how many of your patches would be broken?

gfmdars
IOhannes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 880 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20140416/562fbaeb/attachment.pgp>