I have a weird issue with Debian 13 in my new computer: if I compile a program that uses Allegro's mouse input in debug mode then the mouse input of such program is laggy. But HUGE laggy. I've found that raising the optimization level from 1 to 2 (i.e. "-O2") the lag disappears and the debugging information still works (both breakpoints and variable checking).
No signature provided yet.
I must admit to never having tried adjusting the optimization level. I always use the pre set value. I think it's 1 as standard.
I guess I can try the GTK3 option.
No luck with GTK3. So GTK2 it is for now.
Updated my system requirements with a line about the GTK2.
Will keep using Lazarus-IDE with default settings. Maybe one day there will be some FPC update when the Wayland mess is tidied up.
Update: finally managed to compile for Qt5 and for GTK3(alpha).
The good news is that my old programs compiles for those. The bad news is that the graphics didn't survive the transition well.
Qt5 seems more stable but the complied GTK3 -programs seems to run out of the box on Debian 13. No such luck with openSUSE.
Current plan it to continue with HelloGTK3 and see how far that can go.
Not much gameplay expected.
I saw an x post today by Castle Engine mentioning they are going the GTK3 path. If I understood them right.
Yes you are correct. You can read more detailed information at Upgrade to GTK 3 news article on Castle Game Engine website.Originally Posted by Jonax
And the reason why they are also going to GTK3 is the fact that on Linux their Game Engine Editor is compiled using Lazarus and LCL for UI. So they have been probably experiencing similar problems as you have.
Posting Permissions
Reply With Quote
Bookmarks