pcm@pcmxa.com

In order to get around instability caused by the text2d object, I am using text3d objects. The trouble is, to get them to be about 14 font in the jit.windon they have to be at z position -60 or so making them look very pixelated. Is their a way to get smooth small text3d objects?

turning of depth-enabled helps but thay are just nowhere near as sharp as the text2d can be.

In order to get around instability caused by the text2d object, I am using text3d objects.  The trouble is, to get them to be about 14 font in the jit.windon they have to be at z position -60 or so making them look very pixelated.  Is their a way to get smooth small text3d objects?

good-looking-small-text3d-objects

Turn on fsaa for the context, if you haven't already. That's as good as you'll get. Again the single jit.gl.tex2d approach should be without issue.

Also, for jit.gl.text3d, you shouldn't need to use z position, since you can also use the scale attribute..

Turn on fsaa for the context, if you haven't already. That's as good as you'll get. Again the single jit.gl.tex2d approach should be without issue. 

Also, for jit.gl.text3d, you shouldn't need to use z position, since you can also use the scale attribute..


Thanks, scale improves over zposition but it is still not as nice as 2d text. With fsaa it will work for now.

I did do a rework of the patch so that there was only 1 text2d object. It is responsible for animating 90 discrete elements. All being called independently. I got it to work, but it also crashes with the error relating to text2d append to and a java related memory issue (I don't have the file on this computer), but that could be also related to the intensive amount of calling the loop through the array iterating through the different settings of the text2d object between renders that might be only a few milliseconds apart was getting. I tried to contro for that so that independent animations weren't asking for the loop through at the same time, but I don't know how successful that was.

https://cycling74.com/forums/masive-patcher-with-memory-leak-anybody-hire-out-for-revieweing-patchers

Anyway thanks again for all of you help and suggestions.

Thanks, scale improves over zposition but it is still not as nice as 2d text.  With fsaa it will work for now.  

I did do a rework of the patch so that there was only 1 text2d object.  It is responsible for animating 90 discrete elements. All being called independently.  I got it to work, but it also crashes with the error relating to text2d append to and a java related memory issue (I don't have the file on this computer), but that could be also related to the intensive amount of calling the loop through the array iterating through the different settings of the text2d object between renders that might be only a few milliseconds apart was getting.  I tried to contro for that so that independent animations weren't asking for the loop through at the same time, but I don't know how successful that was.

I posted it at the end of this thread https://cycling74.com/forums/masive-patcher-with-memory-leak-anybody-hire-out-for-revieweing-patchers

@JKC it would be nice if instructions in this forum would be given in a more explicit phrasing. For instance, rather than "Turn on fsaa for the context", "set fsaa in the jit.window object using the @fsaa attribute" would be much clearer.

good looking small text3d objects?