Load an Matrix4f into a FloatBuffer, so my shader can use it
I created a Matrix4f which is a orthogonal perspective for my shader. To store upload the matrix for the shader, it needs to be stored in a FloatBuffer. When I want to put the matrix into the FloatBuffer, I get a error from JOML, my maths library. (I use LWJGL3)
Here are the errors:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.joml.MemUtil$MemUtilUnsafe
(file:/C:/Dev/Java/Learn%20OpenGL/lib/joml-1.9.6.jar) to field
java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.joml.MemUtil$MemUtilUnsafe
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
That's my code:
matrix4f = new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, 1.0f, 1.0f);
FloatBuffer matrixBuffer = BufferUtils.createFloatBuffer(16);
matrix4f.get(matrixBuffer);
GL20.glUniformMatrix4fv(Shader.getLocation(shader, "transformationMatrix"), false, matrixBuffer);
java lwjgl
add a comment |
I created a Matrix4f which is a orthogonal perspective for my shader. To store upload the matrix for the shader, it needs to be stored in a FloatBuffer. When I want to put the matrix into the FloatBuffer, I get a error from JOML, my maths library. (I use LWJGL3)
Here are the errors:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.joml.MemUtil$MemUtilUnsafe
(file:/C:/Dev/Java/Learn%20OpenGL/lib/joml-1.9.6.jar) to field
java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.joml.MemUtil$MemUtilUnsafe
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
That's my code:
matrix4f = new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, 1.0f, 1.0f);
FloatBuffer matrixBuffer = BufferUtils.createFloatBuffer(16);
matrix4f.get(matrixBuffer);
GL20.glUniformMatrix4fv(Shader.getLocation(shader, "transformationMatrix"), false, matrixBuffer);
java lwjgl
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59
add a comment |
I created a Matrix4f which is a orthogonal perspective for my shader. To store upload the matrix for the shader, it needs to be stored in a FloatBuffer. When I want to put the matrix into the FloatBuffer, I get a error from JOML, my maths library. (I use LWJGL3)
Here are the errors:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.joml.MemUtil$MemUtilUnsafe
(file:/C:/Dev/Java/Learn%20OpenGL/lib/joml-1.9.6.jar) to field
java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.joml.MemUtil$MemUtilUnsafe
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
That's my code:
matrix4f = new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, 1.0f, 1.0f);
FloatBuffer matrixBuffer = BufferUtils.createFloatBuffer(16);
matrix4f.get(matrixBuffer);
GL20.glUniformMatrix4fv(Shader.getLocation(shader, "transformationMatrix"), false, matrixBuffer);
java lwjgl
I created a Matrix4f which is a orthogonal perspective for my shader. To store upload the matrix for the shader, it needs to be stored in a FloatBuffer. When I want to put the matrix into the FloatBuffer, I get a error from JOML, my maths library. (I use LWJGL3)
Here are the errors:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.joml.MemUtil$MemUtilUnsafe
(file:/C:/Dev/Java/Learn%20OpenGL/lib/joml-1.9.6.jar) to field
java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.joml.MemUtil$MemUtilUnsafe
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
That's my code:
matrix4f = new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, 1.0f, 1.0f);
FloatBuffer matrixBuffer = BufferUtils.createFloatBuffer(16);
matrix4f.get(matrixBuffer);
GL20.glUniformMatrix4fv(Shader.getLocation(shader, "transformationMatrix"), false, matrixBuffer);
java lwjgl
java lwjgl
asked Dec 29 '18 at 15:45
maniel34maniel34
62
62
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59
add a comment |
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59
add a comment |
1 Answer
1
active
oldest
votes
Updated based on the comment:
The error was caused by making the address field of the java.nio.Buffer class accessible, in order to use it for filling the buffer using the Unsafe class.
This was fixed via this commit, and thus, should be resolved in the latest versions of JOML. So you should update to the latest version, if possible.
Two workarounds for the old version:
There is a startup option for JOML that disables the use of the
Unsafeclass. So you could passjoml.nounsafe=trueto your application. But the flag is largely undocumented, and it's not entirely clear which implications this will have.
Another workaround would be to manually move the data from the matrix to the buffer:
import java.nio.ByteBuffer;
import java.nio.ByteOrder;
import java.nio.FloatBuffer;
import org.joml.Matrix4f;
public class JomlMatrixToBuffer
{
public static void main(String args)
{
Matrix4f matrix4f =
new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, -1.0f, 1.0f);
FloatBuffer matrixBuffer = createFloatBuffer(16);
matrix4f.get(matrixBuffer);
System.out.println("Result:");
for (int i = 0; i < matrixBuffer.capacity(); i++)
{
System.out.println(matrixBuffer.get(i));
}
}
private static void matrixToBuffer(Matrix4f m, FloatBuffer dest)
{
matrixToBuffer(m, 0, dest);
}
private static void matrixToBuffer(Matrix4f m, int offset, FloatBuffer dest)
{
dest.put(offset, m.m00());
dest.put(offset + 1, m.m01());
dest.put(offset + 2, m.m02());
dest.put(offset + 3, m.m03());
dest.put(offset + 4, m.m10());
dest.put(offset + 5, m.m11());
dest.put(offset + 6, m.m12());
dest.put(offset + 7, m.m13());
dest.put(offset + 8, m.m20());
dest.put(offset + 9, m.m21());
dest.put(offset + 10, m.m22());
dest.put(offset + 11, m.m23());
dest.put(offset + 12, m.m30());
dest.put(offset + 13, m.m31());
dest.put(offset + 14, m.m32());
dest.put(offset + 15, m.m33());
}
private static FloatBuffer createFloatBuffer(int size)
{
return ByteBuffer.allocateDirect(size << 2)
.order(ByteOrder.nativeOrder())
.asFloatBuffer();
}
}
But that's not so nice, because you're doing manually what JOML is already doing internally when not using
Unsafe.
The warning about illegal reflective access is not directly related to usingsun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Fieldaddressin the classjava.nio.Bufferaccessible viaAccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.
– httpdigest
Dec 29 '18 at 18:06
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53970962%2fload-an-matrix4f-into-a-floatbuffer-so-my-shader-can-use-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Updated based on the comment:
The error was caused by making the address field of the java.nio.Buffer class accessible, in order to use it for filling the buffer using the Unsafe class.
This was fixed via this commit, and thus, should be resolved in the latest versions of JOML. So you should update to the latest version, if possible.
Two workarounds for the old version:
There is a startup option for JOML that disables the use of the
Unsafeclass. So you could passjoml.nounsafe=trueto your application. But the flag is largely undocumented, and it's not entirely clear which implications this will have.
Another workaround would be to manually move the data from the matrix to the buffer:
import java.nio.ByteBuffer;
import java.nio.ByteOrder;
import java.nio.FloatBuffer;
import org.joml.Matrix4f;
public class JomlMatrixToBuffer
{
public static void main(String args)
{
Matrix4f matrix4f =
new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, -1.0f, 1.0f);
FloatBuffer matrixBuffer = createFloatBuffer(16);
matrix4f.get(matrixBuffer);
System.out.println("Result:");
for (int i = 0; i < matrixBuffer.capacity(); i++)
{
System.out.println(matrixBuffer.get(i));
}
}
private static void matrixToBuffer(Matrix4f m, FloatBuffer dest)
{
matrixToBuffer(m, 0, dest);
}
private static void matrixToBuffer(Matrix4f m, int offset, FloatBuffer dest)
{
dest.put(offset, m.m00());
dest.put(offset + 1, m.m01());
dest.put(offset + 2, m.m02());
dest.put(offset + 3, m.m03());
dest.put(offset + 4, m.m10());
dest.put(offset + 5, m.m11());
dest.put(offset + 6, m.m12());
dest.put(offset + 7, m.m13());
dest.put(offset + 8, m.m20());
dest.put(offset + 9, m.m21());
dest.put(offset + 10, m.m22());
dest.put(offset + 11, m.m23());
dest.put(offset + 12, m.m30());
dest.put(offset + 13, m.m31());
dest.put(offset + 14, m.m32());
dest.put(offset + 15, m.m33());
}
private static FloatBuffer createFloatBuffer(int size)
{
return ByteBuffer.allocateDirect(size << 2)
.order(ByteOrder.nativeOrder())
.asFloatBuffer();
}
}
But that's not so nice, because you're doing manually what JOML is already doing internally when not using
Unsafe.
The warning about illegal reflective access is not directly related to usingsun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Fieldaddressin the classjava.nio.Bufferaccessible viaAccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.
– httpdigest
Dec 29 '18 at 18:06
add a comment |
Updated based on the comment:
The error was caused by making the address field of the java.nio.Buffer class accessible, in order to use it for filling the buffer using the Unsafe class.
This was fixed via this commit, and thus, should be resolved in the latest versions of JOML. So you should update to the latest version, if possible.
Two workarounds for the old version:
There is a startup option for JOML that disables the use of the
Unsafeclass. So you could passjoml.nounsafe=trueto your application. But the flag is largely undocumented, and it's not entirely clear which implications this will have.
Another workaround would be to manually move the data from the matrix to the buffer:
import java.nio.ByteBuffer;
import java.nio.ByteOrder;
import java.nio.FloatBuffer;
import org.joml.Matrix4f;
public class JomlMatrixToBuffer
{
public static void main(String args)
{
Matrix4f matrix4f =
new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, -1.0f, 1.0f);
FloatBuffer matrixBuffer = createFloatBuffer(16);
matrix4f.get(matrixBuffer);
System.out.println("Result:");
for (int i = 0; i < matrixBuffer.capacity(); i++)
{
System.out.println(matrixBuffer.get(i));
}
}
private static void matrixToBuffer(Matrix4f m, FloatBuffer dest)
{
matrixToBuffer(m, 0, dest);
}
private static void matrixToBuffer(Matrix4f m, int offset, FloatBuffer dest)
{
dest.put(offset, m.m00());
dest.put(offset + 1, m.m01());
dest.put(offset + 2, m.m02());
dest.put(offset + 3, m.m03());
dest.put(offset + 4, m.m10());
dest.put(offset + 5, m.m11());
dest.put(offset + 6, m.m12());
dest.put(offset + 7, m.m13());
dest.put(offset + 8, m.m20());
dest.put(offset + 9, m.m21());
dest.put(offset + 10, m.m22());
dest.put(offset + 11, m.m23());
dest.put(offset + 12, m.m30());
dest.put(offset + 13, m.m31());
dest.put(offset + 14, m.m32());
dest.put(offset + 15, m.m33());
}
private static FloatBuffer createFloatBuffer(int size)
{
return ByteBuffer.allocateDirect(size << 2)
.order(ByteOrder.nativeOrder())
.asFloatBuffer();
}
}
But that's not so nice, because you're doing manually what JOML is already doing internally when not using
Unsafe.
The warning about illegal reflective access is not directly related to usingsun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Fieldaddressin the classjava.nio.Bufferaccessible viaAccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.
– httpdigest
Dec 29 '18 at 18:06
add a comment |
Updated based on the comment:
The error was caused by making the address field of the java.nio.Buffer class accessible, in order to use it for filling the buffer using the Unsafe class.
This was fixed via this commit, and thus, should be resolved in the latest versions of JOML. So you should update to the latest version, if possible.
Two workarounds for the old version:
There is a startup option for JOML that disables the use of the
Unsafeclass. So you could passjoml.nounsafe=trueto your application. But the flag is largely undocumented, and it's not entirely clear which implications this will have.
Another workaround would be to manually move the data from the matrix to the buffer:
import java.nio.ByteBuffer;
import java.nio.ByteOrder;
import java.nio.FloatBuffer;
import org.joml.Matrix4f;
public class JomlMatrixToBuffer
{
public static void main(String args)
{
Matrix4f matrix4f =
new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, -1.0f, 1.0f);
FloatBuffer matrixBuffer = createFloatBuffer(16);
matrix4f.get(matrixBuffer);
System.out.println("Result:");
for (int i = 0; i < matrixBuffer.capacity(); i++)
{
System.out.println(matrixBuffer.get(i));
}
}
private static void matrixToBuffer(Matrix4f m, FloatBuffer dest)
{
matrixToBuffer(m, 0, dest);
}
private static void matrixToBuffer(Matrix4f m, int offset, FloatBuffer dest)
{
dest.put(offset, m.m00());
dest.put(offset + 1, m.m01());
dest.put(offset + 2, m.m02());
dest.put(offset + 3, m.m03());
dest.put(offset + 4, m.m10());
dest.put(offset + 5, m.m11());
dest.put(offset + 6, m.m12());
dest.put(offset + 7, m.m13());
dest.put(offset + 8, m.m20());
dest.put(offset + 9, m.m21());
dest.put(offset + 10, m.m22());
dest.put(offset + 11, m.m23());
dest.put(offset + 12, m.m30());
dest.put(offset + 13, m.m31());
dest.put(offset + 14, m.m32());
dest.put(offset + 15, m.m33());
}
private static FloatBuffer createFloatBuffer(int size)
{
return ByteBuffer.allocateDirect(size << 2)
.order(ByteOrder.nativeOrder())
.asFloatBuffer();
}
}
But that's not so nice, because you're doing manually what JOML is already doing internally when not using
Unsafe.
Updated based on the comment:
The error was caused by making the address field of the java.nio.Buffer class accessible, in order to use it for filling the buffer using the Unsafe class.
This was fixed via this commit, and thus, should be resolved in the latest versions of JOML. So you should update to the latest version, if possible.
Two workarounds for the old version:
There is a startup option for JOML that disables the use of the
Unsafeclass. So you could passjoml.nounsafe=trueto your application. But the flag is largely undocumented, and it's not entirely clear which implications this will have.
Another workaround would be to manually move the data from the matrix to the buffer:
import java.nio.ByteBuffer;
import java.nio.ByteOrder;
import java.nio.FloatBuffer;
import org.joml.Matrix4f;
public class JomlMatrixToBuffer
{
public static void main(String args)
{
Matrix4f matrix4f =
new Matrix4f().ortho(-2.0f, 2.0f, -1.5f, 1.5f, -1.0f, 1.0f);
FloatBuffer matrixBuffer = createFloatBuffer(16);
matrix4f.get(matrixBuffer);
System.out.println("Result:");
for (int i = 0; i < matrixBuffer.capacity(); i++)
{
System.out.println(matrixBuffer.get(i));
}
}
private static void matrixToBuffer(Matrix4f m, FloatBuffer dest)
{
matrixToBuffer(m, 0, dest);
}
private static void matrixToBuffer(Matrix4f m, int offset, FloatBuffer dest)
{
dest.put(offset, m.m00());
dest.put(offset + 1, m.m01());
dest.put(offset + 2, m.m02());
dest.put(offset + 3, m.m03());
dest.put(offset + 4, m.m10());
dest.put(offset + 5, m.m11());
dest.put(offset + 6, m.m12());
dest.put(offset + 7, m.m13());
dest.put(offset + 8, m.m20());
dest.put(offset + 9, m.m21());
dest.put(offset + 10, m.m22());
dest.put(offset + 11, m.m23());
dest.put(offset + 12, m.m30());
dest.put(offset + 13, m.m31());
dest.put(offset + 14, m.m32());
dest.put(offset + 15, m.m33());
}
private static FloatBuffer createFloatBuffer(int size)
{
return ByteBuffer.allocateDirect(size << 2)
.order(ByteOrder.nativeOrder())
.asFloatBuffer();
}
}
But that's not so nice, because you're doing manually what JOML is already doing internally when not using
Unsafe.
edited Dec 30 '18 at 14:32
answered Dec 29 '18 at 16:41
Marco13Marco13
42.1k856108
42.1k856108
The warning about illegal reflective access is not directly related to usingsun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Fieldaddressin the classjava.nio.Bufferaccessible viaAccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.
– httpdigest
Dec 29 '18 at 18:06
add a comment |
The warning about illegal reflective access is not directly related to usingsun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Fieldaddressin the classjava.nio.Bufferaccessible viaAccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.
– httpdigest
Dec 29 '18 at 18:06
The warning about illegal reflective access is not directly related to using
sun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Field address in the class java.nio.Buffer accessible via AccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.– httpdigest
Dec 29 '18 at 18:06
The warning about illegal reflective access is not directly related to using
sun.misc.Unsafe. It is related to using the Java Core Reflection API to make the Field address in the class java.nio.Buffer accessible via AccessibleObject.setAccessible(true). This, in fact, did not have to be done just to use Unsafe to obtain the address of that field. This is why commit github.com/JOML-CI/JOML/commit/… changed the way how this was done.– httpdigest
Dec 29 '18 at 18:06
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53970962%2fload-an-matrix4f-into-a-floatbuffer-so-my-shader-can-use-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It would be good to know your Java version. I assume that it is 10 or 11 (but not 9, right?)
– Marco13
Dec 29 '18 at 16:43
Simply use at least JOML 1.9.10. That works without any such errors/warnings with JDK 9, 10, 11, 12-ea and 13-ea.
– httpdigest
Dec 29 '18 at 17:59