Glfw frameBufferSize is messed up at start

support
1

Hello. I am using arch linux and hyprland and i am having issues with glfw specifically the frame buffer size, at the start i have it where it will renderer an texture quad across the image, and if i use the set height and width the height is to small but when i use frame buffer size the height is way to big
the size it should be is 960x540, the frame buffer size 960x1044, and the size it is after a couple frames: 960x588 and for some reason after calling glfwSwapBuffers 3 times and glfwPollEvents it updates to 960x588. Any help will be usefull, thank you.

computer specs if needed:

OS: Arch Linux x86_64
Host: Latitude 5480
Kernel: 6.14.6-arch1-1
CPU: Intel i5-7300U (4) @ 3.500GHz
GPU: Intel HD Graphics 620
2

Hi @levi73159,

What version of GLFW does this occur with? GLFW 3.4 has some fixes for frame buffer size on Wayland.

3

The version is: GLFW version: 3.4.0
but if you want the version string return by glfw:
3.4.0 Wayland X11 GLX Null EGL OSMesa monotonic shared

4

I believe the Wayland protocol (as well as X11) is asynchronous, so it’s possible that this is simply a consequence of that design. Does the frame buffer size settle down to the correct one - in your text you mention it should be 960x540 but settles to 960x588 however I want to check this is not a typo as you mention that value twice.

You might want to see if using the GLFW_SCALE_FRAMEBUFFER hint helps.

5

yes it is not a type, i putted the size at 960x540 but after a bit it settles to 960x588, i try to set the min and max size, and even the aspect ratio but to no avail

6

and @dougbinks i try to set the window hint, to false or true but none works, it still settles at 960x588

7

It would be worth opening an issue on GLFW Github. If you’re not sure how to do this then I can file the issue.

It would also be useful to run the GLFW test events.c program included with the source, and resize the window and copy the log output. You should see something like:

000002a3 to 1 at 5.077: Framebuffer size: 710 553
000002a4 to 1 at 5.077: Window size: 710 553
000002a5 to 1 at 5.077: Window refresh
000002a6 to 1 at 5.080: Framebuffer size: 711 554
000002a7 to 1 at 5.080: Window size: 711 554
000002a8 to 1 at 5.080: Window refresh
000002a9 to 1 at 5.085: Framebuffer size: 711 555
000002aa to 1 at 5.085: Window size: 711 555
000002ab to 1 at 5.085: Window refresh
000002ac to 1 at 5.162: Framebuffer size: 712 556
000002ad to 1 at 5.163: Window size: 712 556
000002ae to 1 at 5.163: Window refresh

If you’re able to copy any of the initial text from the start of the program’s log output to see if there are any size callbacks triggered then that would be very useful.

8

Yes, ill open the issue on the github page right away but as for the program’s log message is as follows:

Library initialized
Creating windowed mode window 1 (960x540)
Main loop starting
00000000 to 1 at 0.405: Window content scale: 1.000 1.000
00000001 to 1 at 0.406: Framebuffer size: 960 1044
00000002 to 1 at 0.406: Window refresh
00000003 to 1 at 0.414: Window focused
00000004 to 1 at 0.414: Cursor entered window
00000005 to 1 at 0.414: Window was maximized
00000006 to 1 at 0.418: Framebuffer size: 960 588
00000007 to 1 at 0.418: Window size: 960 588
00000008 to 1 at 0.418: Window refresh