So, we still have the Vsync option in the Display settings. Isn’t that a bit confusing, or am I getting this wrong? What’s the difference then?
This is very very new, just start to happened after the latest update.
After this one I believe: https://github.com/defold/defold/pull/9368
1.9.3 → 771fd31725d1968b216debb338d8eefbc46ea254 using Vulkan
ERROR:PLATFORM: GLFW Error: Cannot swap buffers of a window that has no OpenGL or OpenGL ES context
A pr is ready to be reviewed at least…
window.get_mouse_lock() returns true upon starting with the cursor visible and not locked.
window.set_mouse_lock(true) hides the cursor but can still leave the window area.
The beta should be updated with a fix for this.
Thank you very much.
I’m on Alpha so I guess there is a build issue?https://github.com/defold/defold/actions/runs/10672254905
Lol, yes. Apparently the Apple notarization server borked a bit
I pressed the button again, so should n’t take more than 5-60 minutes for Apple to sign it.
Fixed, thanks again
The beta has been updated with a fix for:
- gamepads having changed names (and consequentially not working)
- mouse locks not locking to window
Please try it out and let us know if there are more issues!
EDIT: There is apparently still issues on windows with L and R pads and some console spam, but the controllers should work otherwise. Working on a fix for this.
Another fix has been pushed to beta that adjusts the L/R pad values on the Y axis (i.e inverts them). Gamepads should now work exactly as before on windows!
Hello, thank you for the new beta version.
I’ve been creating some 3D prototypes, and when researching how to lock the mouse pointer
I found this example, though:
I usually work on Linux and everything goes fine with Defold.
When you test on Windows 11 everything changes!
The mouse pointer in Windows is limited to the edges of the screen, the opposite of Linux!
Why?
When recording on Windows 11 with Action4 Screen Recorder the render crashed and those warnings occurred!
Did you test on the latest Defold 1.9.3 BETA, right? Because I launched the project on my Windows 10 and it works ok. But… window.get_mouse_lock()
it always returns true
, even if mouse is not locked. @jhonny.goransson should I fill the issue?
On both systems it’s this version!
Pushed a fix for this into the beta channel, it’ll be available in an hour or so. Excellent example!
These issues have been fixed on the 1.9.3 BETA, the version you are using will not get the fix.
Thank you!