Thread: Command line HD mode & Java 11 reflection fix

Originally Posted by mikan

java 7 should work

On Windows/Linux, Java 7 is fine, yeah. But, on macOS, you need to use Java 6. Some things changed when Apple stopped distributing their own JDK.

Originally Posted by mikan

java 7 should work

Java 6/7 whatever. I don't understand why you would implement the OP.

Originally Posted by Displee

Java 6/7 whatever. I don't understand why you would implement the OP.

The idea was using this you can switch to opengl/directx when running from ide or terminal, however I won't recommend this change today especially since the reason for the issue is not being able to find the correct path not a direct problem with the code; that's what happens when people gravedig 2 year old posts.

I would recommend taking out the unnecessary reflection though, especially for refactoring.

Code:

Method method_3_ = Runtime.class.getDeclaredMethod("load0", Class.class, String.class);
method_3_.setAccessible(true);
method_3_.invoke(Runtime.getRuntime(), var_class, file.getPath());
method_3_.setAccessible(false);

[Only registered and activated users can see links. ]

GPU rendering works on any jre on windows at least for now, don't know if it's the same for mac/linux.

Originally Posted by Omar

On Windows/Linux, Java 7 is fine, yeah. But, on macOS, you need to use Java 6. Some things changed when Apple stopped distributing their own JDK.

To be more precise, in Java 6 AWT components could be backed by an NSView or a CALayer. The NSView -> CALayer migration actually started before the Java 6 -> 7 transition, so I don't think this was related to Applet stopping their own JDK builds - it was already in the works before that. However, Jagex's old OpenGL bindings only supported making an OpenGL context with NSOpenGLContext.

In Java 7, the migration was finished and AWT components could only be backed by a CALayer. Jagex's old OpenGL bindings do not support CAOpenGLLayer, and it's relatively tricky to retrofit it because it works in a completely different way to the NSOpenGLContext. With an NSOpenGLContext your own application is in charge of rendering, but with CAOpenGLLayer the Core Animation library is in charge of rendering and calls back into your application. The jaggl interface wasn't designed to support the latter approach, but you can use frame buffers to work around that.

[Only registered and activated users can see links. ] is a clean room implementation of the 550 native libraries that supports both NSView and CALayer (and also means we can compile it for new architectures, like ARM). It probably wouldn't be too much effort to do something similar for 667, but the 550 natives aren't compatible out of the box.

Originally Posted by Graham

[Only registered and activated users can see links. ] is a clean room implementation of the 550 native libraries that supports both NSView and CALayer (and also means we can compile it for new architectures, like ARM). It probably wouldn't be too much effort to do something similar for 667, but the 550 natives aren't compatible out of the box.

There's so many things I want to look into this year! So little time...