Skip to main content

Performance Problems with AntiAliasing

5 replies [Last post]
Joined: 2010-06-25

im from germany so the spelling or grammar might not be the best ...
my problem:
i have enormously performance problem

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2010-08-17

Hi again, I tried your demo running.
Well, the good thing is: there was no bucking at all. The bad thing is that I couldn't notice any antialiasing at all, even when the text field said "on".. >_<

As far as I'm concerned, the .getPreferredConfiguration() call doesn't always return an appropriate config with antialias support. At least my programs on my machine always stated, that Canvas3D.getSceneAntialiasingAvailable() flag was false. And all the attempts to set antialiasing modes failed. I don't know exactly why that happens, but since there wasn't any exact task for me to turn it on, I never cared much about it.

I'm sorry, but adraid I can't help you solve this problem at the moment. I'll be looking over the docs and srcs on j3d, and if something comes up I'll let you know.

Meanwhile, there is a chance that the reason lies within that GraphicsConfiguration class (along with its neighbour GraphicsEnvironment). I bet it would require some deeper knowledge about graphics hardware. Sorry for being helpful only this much.

Joined: 2010-06-25

finally i got it...
the function
GraphicsConfigTemplate3D template = new GraphicsConfigTemplate3D();
// 1 = Multisampling Antialiasing
template.setSceneAntialiasing(1);// GraphicsConfigTemplate3D.REQUIRED
c = new Canvas3D(GraphicsEnvironment.

was not workling just because my videocard does not support multisampling(normaly the card sould support - i think this function is broken -.-)

the multisampling test is @
->QueryProperties-> sceneAntialiasingNumPasses = 1 --> support multisampling
->QueryProperties-> sceneAntialiasingNumPasses = 8 --> dosnt support multisampling

Joined: 2003-07-17

Query sceneAntialiasingNumPasses before you create your running Canvas3D.
And set graphicsConfigTemplate3D.setSceneAntialiasing as REQUIRED / PREFERRED when sceneAntialiasingNumPasses == 1.

btw, check if the D3D renderer gives better AA performance.

Joined: 2010-08-17

Would you post a link for a demo or at least some code source? It's hard to tell what causes your bucking and how big that thing is.

And check out this applet to compare: Maybe your anxiety's out of nothing. You know, antialising is something that always demand hardware resources.

Joined: 2010-06-25

thanks for your reply
yes i know... aliasing is depending on hardware...
I post a demo tomorrow at midday...

you will see every computer should be able to render a fluent scene (even 4 dots bucks)...

by the way...i just got few bucks..but it is no comparison with my (realy simple) scene


so I link to the zip file, with the src-code and a html view of the applet -> so you are able to understand what I mean with every pc should be able to render this mini scene fluently...

Message was edited by: mattn

Message was edited by: mattn