Horati,
I welcome your fast response. Not to say, I appreciate Xith3d, which seems a bit overkill compared to the current state of Java3D, but running smoother - if it is running.
Why are you using Swing rendering?
Because of UI design decisions. Not to say, we currently are experimenting with both Xith3D and Java3D, as both technologies have their advantages, drawbacks and issues with certain device hardware. Just to get more flexibility and certainty to get one technology running with a certain device. Unfortunately Java3D is not running on certain machines, so Xith is an option in such cases.
There is an interface between these and the application layer. UI design layers of both technologies are too special and proprietary to derive any universal solution from both. Therefore, Swing layer over any Swing 3D canvas is the best choice for any general architecture. Anyway, the reason why shall not be topic of my question.
There's a lot of slowness in that area in general. Depending on what you need to do, we might be able to suggest a faster UI design.
Here I have to correct myself: The Xith3D AWT canvas is crashing on that machine however, therefore any different approach would not work. Anyway, it would not be useful for us. For example, AWT does not provide easy transparancies for overlay controls, Drwaing them pixel by pixel by the application is not a choice in this case. Therefore I can ignore this fact.
Anyway, 25 fps would be great for our purpose. 90 fps is more than expected, but 7 fps with Xith is horrible. Indeed. I cannot explain this simply by using offscreen drawing or using Swing components in general. Even a native bitmap conversion by using the main processor would be a lot faster than the handbrake seen here. Also we tested with no Swing overlay components (thus not any transparency) and got the same result from the simple Swing Canvas drawing context. Frame rate will not extend to more than 7 fps.
I have absolutely no idea, why any OpenGL benchmark is running much faster than the combination of Xith3D/JOGL. Is seems, as if Xith3D would not use hardware acceleration on that machine.
Having said that, I'm not sure why the difference is so extreme compared to your development machines. Could you run several of the xith-tk benchmark applications on both machines and report the results?
I would give it a try, if this would be the last option. We currently are evaluating a general software architecture and a lot of issues with all those 3D frameworks in general. Thus, evaluating Xith3D features, which we don't need, is not in my focus.