8/5/2023 0 Comments Java 3d clock not working![]() My programs depend on Modules A, B and C.Ħ. Dependencies: A depend on C and C depends on B. Third wrapper module (Module C) called jogl. placed the gluegen-natives jar into /releases/modules/lib/x86 folder of that module.Ĥ. A second wrapper module (Module B) called gluegen. Copied the natives jars into a folder called /releases/modules/lib/x86 folder.ģ. Created a wrapper module (Module A) called java3d in my program and placed the three modules into it. Downloaded 1.6.0 version of Java 3D (three jars) from github.hharrison (or whatever that site was).Ģ. If it does, what does this module depend on, or what modules should depend on this module?ġ. In my program, if I create a fourth wrapper module (say Module D) and place all possible native libraries (both Windows and Linux 32 and 64 bit jar files), will it work? Will the program automatically pick up the correct jar file at run time? My apologies, if this question is not a jogl specific one, but a NetBeans one. The computer that runs my program could be Windows or Linux, and could be 32 bit or 64 bit. I don’t know on which machine my program will run. What dependencies should I use? Module A depends on Module B and Module B depends on Module C?ĥ. If so, where do I put the natives jar file?Ĥ. Do I need to create three wrapper modules for Java 3D? One for the three Java 3D jars (say Module A), one for gluegen-rt.jar (say Module B) and the last one for (say Module C). I have a lot of modules in my overall program. I need to use NetBeans and the Rich Client Platform application. If I use the natives jar, I don’t need to use any. I need to use the “jogl-all-natives-windows-amd64.jar” file. so files says “This folder contains deprecated plain native libraries for platform windows-amd64, please use the native JAR files in the jar folder.” Ok. My questions are specifically the following:ġ.ğirstly, what are all the jar files that I should use? I guess I should be using the three jar files of Java 3D + + gluegen-rt.jar + a jar file containing the native libraries for the platform I am targeting. I see that there are a lot of jar files and also a lot of. I have downloaded the 7z zip file that you suggested. As I said, the same program works perfectly fine on the home computer (of course with 32 bit libraries). The other menu items and the program functions normally, but with no display on the JPanel (it just remains cold grey).Ĭould somebody please explain this weird behaviour to me. Now the Office computer doesn't even print those to the output window. I have put in a few lines in the model file just to see till what point it has reached. But, the Canvas3D object doesn't get added to the JPanel and therefore does not show my model. Now the program compiles and runs without any errors. So I downloaded 64-bit version (amd64) of Java 3D, and replaced all three jars and the dlls with the 64 bit versions. When I tried to run my program at office, it gave an exception saying you can't use 32 bit native dlls. In that computer I have 64-bit Oracle JDK 1.7.0u5 installed. Now that computer has been replaced by a 64 bit Windows 7 computer. Till recently, I had a 32-bit computer (Win XP) at the Office and the program was working there as well. I also work on the program at the Office. ![]() ![]() In the program I have a JPanel to which I added Canvas3D to show my 3D model. (I have Linux system - Ubuntu 12.04 LTS) with Oracle JDK 1.7.0u4 and Java 3D 1.5.2. The computer at home is a 32 bit computer and everything works fine. You can't seriously use that in production.I am working on a Java application in which I need to use Java 3D. Then, when the version 1.7.0 is ready, we'll do our best to put it into Maven Central, you'll have to use different package names and it will work.Īnd sorry to insist but you won't get any help here on an unmaintained, abandoned and obsolete version of Java3D (1.3.1). The next version, which we'd like to push on Maven Central, uses different package names, it has absolutely nothing to do with the absolutely obsolete version of Java3D (1.3.1) that you obtained elsewhere. We don't maintain the versions 1.5.2 and earlier, it's explained in the sticky note and I advise you to read my tutorial. I remind you that we maintain only the version 1.6.0 and this Mavenization will be probably ready for the version 1.7.0. You mustn't use conflicting versions of Java3D. You must use the very latest version of JOGL to make it work (currently 2.3.2).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |