Hey SHC,
You’re using an old build, try the latest nightly (#17) please.
Hey SHC,
You’re using an old build, try the latest nightly (#17) please.
Hey Spasi,
It’s now working, but there is another bug. When I’ve clicked the close button on the window, the window became unresponsive, and I’ve to force quit it. No exceptions, but the return code is 137.
Could you post some details about your environment? Java version, OS/arch, GPU driver. Also, could you run it with [icode]-Dorg.lwjgl.util.Debug=true[/icode] and see if there’s anything interesting?
Nevermind, it is resolved now. I forgot to rebuild after changing the library and natives.
You should clarify the documentation of those methods:
http://javadoc.lwjgl.org/org/lwjgl/BufferUtils.html#createByteBuffer(int)
http://javadoc.lwjgl.org/org/lwjgl/BufferUtils.html#createAlignedByteBufferPage(int)
http://javadoc.lwjgl.org/org/lwjgl/BufferUtils.html#createAlignedByteBufferCacheLine(int)
What is the difference between “Allocates” and “Construct” in this case? Moreover, “Construct” should be replaced by “Constructs” and “Fill” should be replaced by “Fills” in order to be consistent with the good practices of Java documentation writing. There is some useless polysemy, “with the specified capacity” has the same meaning than “with the given capacity”, doesn’t it?
This class was written in 2004 and the aligned versions were added in LWJGL 3. I agree about consistency, it’s an important attribute for any library.
Question: On the lwjgl getting started page it says “Attach the LWJGL javadoc and source archives to the LWJGL library (optional, but hightly recommended)”.
Can anyone explain in more detail how I do this. Im having trouble trying to attach the javadoc.
EDIT:
Nevermind, I think I got all figured out. ;D
So for a project that is starting now, is using lwjgl 3 a good idea? Or is using 2.x and porting later the recommended route.
lwjgl 3, It will be worth it in the future
There are a lot of differences in the windowing API, that would take a lot of time to port old projects. I recommend using the nightlies and update with every nightly to test if yours work with the nightly.
The windowing system init is usually a pretty trivial part of a game’s codebase. It should take a few minutes to move to LWJGL3 from LWJGL2.
Cas
i’m worrying about swing interop >.<
If you need AWT/Swing interop, my advice would be to stick with LWJGL 2.
Technically, you could implement LWJGL 2’s interop behavior using LWJGL 3’s bindings to OS APIs, but that’s such a low priority for 3 that it’ll probably have to be a contribution from someone else.
I’m getting a bug occasionally when I call [icode]glfwCreateWindow()[/icode] with nightly #20. Here’s the stackstrace. http://pastebin.java-gaming.org/2bc5f93331617
It only occurs occasionally, not always, and I’m not sure of the reason. That is the first function I call in my engine, even before the game loop starts.
[quote=“SHC,post:54,topic:51150”]
Does launching the JVM with [icode]-XstartOnFirstThread[/icode] fix the crash?
Using that bought me this stack trace. http://pastebin.java-gaming.org/bc5f303461715
This time, it was not occasional, but it occurred every time, I ran it 10 times, and the same thing is happening. Without the option, it works now, dunno when next crash would occur.
Are you doing anything with AWT/Swing? Also, what JVM and OS X versions are you running it on?
I’m not using any Swing/AWT features in my engine. My OS X version is 10.10.1 (Latest Yosemite). I tried adding [icode]-Dorg.lwjgl.util.Debug=true[/icode], but got no output.
Pardon me if this has already been asked, but how does one access the old javadocs? For example, I had this page open, but it has since become a 404: http://www.lwjgl.org/javadoc/index.html?org/lwjgl/input/Mouse.html