I succeeded run M-gui on mac os but failed on windows 64 bit.
I downloaded latest version of this (mgui-1.0.22-alpha) and have installed latest java program (jdk-8u91-windows-x64) already.
However when I run the mgui-amd64.bat, there were some error messages in DOS window.

Here is the message.

Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Users\A\Documents\mgui-1.0.22-alpha\gluegen-rt.dll

How can I fix this?

Best,
Saske

I am using a MacBook Pro (2014) with OS X 10.9.5, and I downloaded mgui-1.0.22-alpha release from the mgui-core series released 2014-06-01.
The JDK is installed in:
/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk

and this is the output of java -version:

java version "1.8.0_40" Java(TM) SE Runtime Environment (build 1.8.0_40-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode

If I use the command for mac in the README, which has the amd64 option, I get:

~/Downloads/mgui-1.0.22-alpha: java -Djava.library.path=bin/amd64 -Xmx1000m -classpath .:lib:lib/* mgui.interfaces.exec.MguiStart mgui.mac.init Error: Could not find or load main class mgui.interfaces.exec.MguiStart

If I use the mgui-mac command, which has the i586 option, I get:

~/Downloads/mgui-1.0.22-alpha: ./mgui-mac Could not initiate driver 'JDBC-ODBC', class 'sun.jdbc.odbc.JdbcOdbcDriver' Details: sun.jdbc.odbc.JdbcOdbcDriver Exception in thread "main" java.lang.UnsatisfiedLinkError: no J3D in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1865) at java.lang.Runtime.loadLibrary0(Runtime.java:870) at java.lang.System.loadLibrary(System.java:1122) at javax.media.j3d.MasterControl$22.run(MasterControl.java:891) at java.security.AccessController.doPrivileged(Native Method) at javax.media.j3d.MasterControl.loadLibraries(MasterControl.java:888) at javax.media.j3d.VirtualUniverse.<clinit>(VirtualUniverse.java:233) at mgui.interfaces.graphics.InterfaceGraphic3D.init(InterfaceGraphic3D.java:241) at mgui.interfaces.graphics.InterfaceGraphic3D.<init>(InterfaceGraphic3D.java:183) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at mgui.interfaces.InterfaceEnvironment$InterfaceGraphicLoader.loadClass(InterfaceEnvironment.java:2025) at mgui.interfaces.InterfaceEnvironment.addInterfaceGraphicClass(InterfaceEnvironment.java:1087) at mgui.interfaces.InterfaceEnvironment.init(InterfaceEnvironment.java:466) at mgui.interfaces.InterfaceEnvironment.init(InterfaceEnvironment.java:194) at mgui.interfaces.InterfaceSession.start(InterfaceSession.java:192) at mgui.interfaces.InterfaceSession.start(InterfaceSession.java:169) at mgui.interfaces.exec.MguiStart.main(MguiStart.java:41) ========================================================================================

I have installed mgui 1.0.22-alpha on a Mac OSX 10.8.5, and I have installed java 3D jkd1.8.0.
When I try to run mgui-mac, I got the following error:

mac-5brown:~ lea$ /Applications/MINC/mcgui/mgui-1.0.22-alpha-src/mgui-mac ; exit;
Error: Could not find or load main class mgui.interfaces.exec.MguiStart
logout
[Process completed]

What is the problem and how can I fix it?
Thank you

Unsupported major.minor version 51.0

This basically means the version of Java that runs by default on your system (i.e., the one which is called by typing "java" in the terminal) is outdated. To see what version is currently the default on your system, type:

java -version

You should see something like:

java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

If the version is 1.6.blah, this problem can be solved by updating your Java version to 1.7 or later. If you have already done so and are still getting the error, see below.

To update Java on Ubuntu, type:

sudo apt-get update sudo apt-get install openjdk-7-jdk

This will install OpenJDK. If you prefer Oracle's JDK, follow the instructions here instead.

To update on other systems, go here (preferred) or here and follow the instructions for your particular system.

I've installed 1.7 but it is not the default

If you have already upgraded Java, but you still get the major.minor error, the problem is probably that the default version is not pointing to it.

For Ubuntu, you can fix this with the command below:

sudo update-alternatives --config java

Which will give a list similar to that shown below (but with 1.6 selected), that will allow you to specify which version of Java runs by default:

There are 2 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/lib/jvm/java-7-oracle/jre/bin/java 1062 auto mode 1 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 manual mode 2 /usr/lib/jvm/java-7-oracle/jre/bin/java 1062 manual mode Press enter to keep the current choice[*], or type selection number:

For Windows and Mac, the latest installed version should be set to default. If you have trouble with this, you will need to find the path to the latest version and add this to the front of your PATH environment variable OR in the command line of the ModelGUI executable itself.

C:\Program Files\mgui-1.0.21-alpha>java -Djava.library.path=bin\amd64 -Xmx2000m -classpath .;*;lib;lib\* mgui.interfaces.exec.MguiStart 2014.03.15 06:32:41 EDT: Error initializing ar.model environment from ’C:\Program Files\mgui-1.0.21 -alpha\init\mgui.default.init’ 2014.03.15 06:32:41 EDT: Fatal error: Could not initialize InterfaceEnvironment.

Windows is likely giving a permission error because it is trying to write a log file in Program Files. There are 3 ways to fix this, starting with the most recommended:

1. Move everything to a another folder where there are no permission issues. A folder somewhere in "My Documents" should work without issue.

2. Look in C:\Program Files\mgui-1.0.21-alpha\init for a file called "mgui.default.init." Use a text editor (e.g., Notepad) to edit this file with the two following changes:

a. Put a "#" in front of the line "setLogFileAndConsole mgui_session"
b. Type on the next line "setLogConsole"

This will prevent the program from trying to print a log file.

3. Run the bat file, shortcut, or command prompt as an Administrator.

1. This forum is for both users and developers. Please specify which you are, as it can help in formulating an appropriate response.

2. Always state the ModelGUI version you were using when the issue was encountered. This especially important because the code is constantly being updated (read: improved), and the solution may already have been committed to a newer issue. It is also very useful for developers to identify and track bugs.

3. Exceptions, errors, and warnings are text printed to the console, which give information about program execution and problems encountered therein. In brief:

a. An exception is a Java stack trace, which is distinguished by being a long list of lines which trace back program execution through the Java classes that are being executed. Stack traces are useful mostly for developers, but it is also very useful for users to post these here. It will look something like this:

Exception in thread "main" java.lang.NullPointerException: at SomeClass.thirdMethod(SomeClass.java:15) at SomeClass.secondMethod(SomeClass.java:11) at SomeClass.firstMethod(SomeClass.java:7)

b. Errors and warnings are produced by the ModelGUI to indicate a problem, without burdening the console with long stack traces.

4. There are different levels of logging which determine what gets printed to the console or to a log file (see this description). If something is going wrong but you are not getting an error or exception, you may need to change the init file (typically "init/mgui.{os}.init") to reflect a more verbose level of logging, and ensure it is being sent to the console. The most verbose option is:

# set logging setLogFileAndConsole mgui_session setLoggingType debug

..which will write to both the console and a log file (located in the "logs" subdirectory), and will write everything, including all stack traces.

5. You can use the terminal window used to run your ModelGUI session to retrieve log output, or you can add a Console Window to one of your tabs in the program itself. Errors and exceptions will show up in red in this window, and can be copied using Ctrl-C.

6. Try to use the "code" buttons in the edit window to ensure your exceptions, code, etc. is encapsulated in a code block. This makes your post much more readable. Additionally, Wikidot provides a rich selection of formatting tools; feel free to use these to make your post easier to read, and respond to.