Main Menu

Recent posts

#1
LWJGL Documentation / The HelloWorld sample at https...
Last post by blob - October 29, 2024, 20:13:47
The HelloWorld sample at https://www.lwjgl.org/guide tries to set the global window position.

// Center the window
			glfwSetWindowPos(on
				window,
				(vidmode.width() - pWidth.get(0)) / 2,
				(vidmode.height() - pHeight.get(0)) / 2
			);

This is incompatible with Wayland as per GLFW documentation

glfwSetWindowPos docs

#2
Lightweight Java Gaming Library / JDBC to ODBC bridge using LWJG...
Last post by teambob - October 29, 2024, 09:18:11
Hi everyone,

I had a few weeks between contracts, so I wrote a JDBC to ODBC bridge using your library's ODBC binding.

You can check out the alpha release here: https://github.com/teambob/jdbc2odbc/releases/tag/v0.1-ALPHA

The biggest challenge was dealing with the different library names on Linux and Windows.

Cheers
Andrew
#3
Lightweight Java Gaming Library / Re: Indie Fighting Game using ...
Last post by cpope9141 - September 19, 2024, 20:08:15
The September release of Area Zero (v0.17.0) is now available: https://ephemeraltechnicalarts.com/area-zero

Release notes are available on the website.
#4
Bug Reports / RFE / Re: [RFE] Metal API Bindings?
Last post by spasi - September 06, 2024, 09:29:42
Hey jackd5011,

No, LWJGL provides C bindings only. There are a few options for Metal:

1. Vulkan over MoltenVK (indirect)
2. bgfx with the Metal backend (indirect)
3. Use the Objective-C Runtime bindings to call the Metal API (direct).

The third option is what C++ wrappers do to expose Metal. Performance-wise it's equivalent to using Metal directly via Obj-C/Swift.

A final option would be writing a renderer using native Metal, wrapping it in a shared library, then use that from Java (with a custom, application-specific API).
#5
Bug Reports / RFE / [RFE] Metal API Bindings?
Last post by jackd5011 - September 06, 2024, 07:20:50
Has there been any consideration to add native bindings for Metal on Apple devices?

I know we have Vulkan bindings which uses MoltenVK under the hood, but in my experience the compatibility with M2 macs isn't great and I came across a lot of issues following a standard Vulkan tutorial, and the MoltenVK docs specifically say that it doesn't have perfect compatibility with the standard Vulkan API.

So until Apple adds proper support for Vulkan (which they never would), is there any consideration for LWJGL to create Metal bindings?
#6
Bug Reports / RFE / Re: unsatisfiedLinkError
Last post by jakethesnake - September 02, 2024, 11:43:17
Quote from: spasi on September 02, 2024, 08:35:24I just tested it again and the fallback appears to be working fine.

I tested as well just now, and it does work for me. Very strange. I asked the user to remove the temporary lwjgl.dll There's no 32-bit lwjgl version anymore, right? So It can't be an outdated version.




https://imgur.com/a/7GvpXqt

It claims it's x64 3.3.3 here.

A mystery then, or error on our side. Thank for the help.
#7
Bug Reports / RFE / Re: unsatisfiedLinkError
Last post by spasi - September 02, 2024, 08:35:24
I just tested it again and the fallback appears to be working fine.
#8
Bug Reports / RFE / Re: unsatisfiedLinkError
Last post by jakethesnake - September 02, 2024, 06:37:08
Thank you,

No, alas, the version is 3.3.3

The username was reported to be: пользователь
When the user changed to something latin, the error disappeared.

Let me know if it's something you can reproduce, or else I'll break my windows install and try it.
#9
Bug Reports / RFE / Re: unsatisfiedLinkError
Last post by spasi - September 01, 2024, 10:36:51
Hey jakethesnake,

How old is the LWJGL version? This should be fixed with https://github.com/LWJGL/lwjgl3/commit/dedb44e0ab364ceab1f452daa825930052b1829c, available since version 3.2.2.
#10
Bug Reports / RFE / unsatisfiedLinkError
Last post by jakethesnake - September 01, 2024, 06:59:32
Hello. I have a a distributed app, and one of the users is getting a java.lang.unsatisfiedLinkError when loading lwjgl.dll

From googling, I found this:
https://github.com/libgdx/libgdx/issues/5524

And indeed, the problem resolved when the user changed his name from something cryllic to ascii.

This is with the previous version of lwjgl. I'm not sure if something has been fixed in the latest release. I can't make sense of the patch notes. It would be strange though, as this bug would have been noticed from day 1.