Re: JCanvas3D on OSX Java 7
Posted by
gouessej on
Apr 26, 2013; 9:28am
URL: https://forum.jogamp.org/JCanvas3D-on-OSX-Java-7-tp4028980p4029041.html
joshp wrote
In the meantime I have to admit that I tried to get JMonkeyEngine to work - I'm afraid my project is getting a bit urgent and I'm looking for anything that will help me out of a tight spot at the moment. The LWJGL renderer in JME does seem to work ok in when embedded in a netbeans canvas - at least on my laptop, but for some reason, even with an apparently identical java/gl environment on my desktop machine it fails with an error about loading the jawt native libraries.
I then tried JMonkeyEngine with GouesseJ's Jogl renderer - interestingly, even though it appears to be based on Newt, it seems to have exactly the same behaviour as Canvas3D when running in netbeans - i.e. the 3d canvas always appears at the bottom left of the parent window.
I agree with Harvey (but it should work with Netbeans RCP too) and I would prefer bugs and performance improvements on the basic canvases of Java3D to be done directly in Java3D rather than in a third party library. It doesn't mean that libraries written above Java3D have no interest but they shouldn't become an absolute necessity. I highly encourage August to contribute and he already helped us a lot in the past :)
@joshp please use the very latest version of JOGL 2.0, recompile Java3D if necessary. If there is still a problem with the position of the canvas, write a bug report, provide a small test case.
In my humble opinion, it will be difficult to make Java3D evolve, some design flaws complicates this task. A merge of Java3D with Xith3D would be interesting but I don't advise to use Java3D on the long term in industrial applications. You can try Ardor3D too and I remind you that JMonkeyEngine 3 still uses an "old" build of JOGL 2.0, I haven't updated for several weeks or months. Tell me what you need to do with a scenegraph.
The JOGL renderer of JMonkeyEngine 3 can use both AWT or NEWT. Ardor3D offers a bigger choice, you can use the NEWT AWT bridge too.
If you really want to have serious troubles on some hardware, switch to the competitor of JOGL but you will lose the advantages of the render quirks and you will have to explain to your customers why your software crashes and why you can't do anything to solve their problems. Moreover, the renderer that relies on our competitor doesn't use its third version, expect a major rewrite in some months (at least before the release of the stable release) with possible regressions. Then, the renderer based on JOGL 2 will be already more stable than this. I'm not here to defend our competitor. We sometimes collaborate but I know why I have used JOGL since 2006.