You are browsing as a guest. Sign up (or log in) to start making projects!

3h 10m 18s logged

Ok, so BIG news: After a lot of debugging I remembered that I’m actually GOATED, so my code couldn’t POSSIBLY be wrong, so I tried to look online for people experiencing problems with SDL3 using Wayland and I actually found out Wayland doesn’t give access to global screen coordinates to programs (And my pathfinsing uses Global coordinates), so I tried running it using an X11 compatibility layer, AND IT WORKED!!! Kind of…
So basically, it DOES work, but it’s extremely laggy, and I’m trying to figure out if it’s the compatibility layer or just my code (Probably both), so for the next devlog I’ll have to set an FPS cap so that the pathfinding lags less maybe?. And if that doesn’t fix it then I’ll have to reprogram everything to work natively with Wayland (or try to find a way to make the compatibility layer lag less). It’d be cool to find a way to give the program access to global screen coordinates though, since that would make my life a lot easier, and I wouldn’t have to use a compatibility layer.
That’s it for this Devlog, see ya in the next one!

0
31

Comments 2

@gusin9113

a*? what if you run it every alternate frame or every 4 frames?

@kurkiie

If you’re printing the cursor everytime it moves that can cause plenty of slowdown