To add to my earlier comments, I usually copy j3d.dll from the jre folder into the same folder as the your_app.jar file, to guarantee that it will be found at runtime. This may or may not be necessary. It seemed to be necessary the last time I ran a Java3D app on a computer that had no Java runtime environment already installed. It may be unnecessary if one goes through the trouble of adjusting the PATH, by I didn't want to bother with that. I have been compiling Java3D apps by utilizing VisualCafe4 Professional Edition compiler (with Project | Options | Directories | Input_Class_Files pointing to the Java3D JDK .jar files such as java3d-utils-src.jar, etc). I then package them as I described in my previous e-mail, with the latest Sun (Java2 + Java3D) jre folder (JRE1.3). This has worked well, although eventually I will need to change the VisualCafe4 settings so that it compiles using the latest JDK instead of the VisualCafe4 compiler, when the VisualCafe4 compiler becomes out-of-date (at this time, the VisualCafe4 compiler seems to be quite compatible with the latest Sun JRE, JRE1.3). Perhaps VisualCafe5 or some version that has the next java compiler will be available before that becomes necessary. By the way, I have bemoaned the fact that I have never been able to use VisualCafe4's native compiler to create a native executable using Java3D. Something seems to be wrong with VisualCafe4 in that respect. Therefore, all of my Java3D apps are interpreted, not native. However, the interpreted versions seem sufficiently fast, for my purposes. Rob =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
