Post

Can we tackle performance before stability?

Micky

@mickeon.bsky.social

github.comFix performance issues when moving the mouse with high polling rate on Windows by Calinou · Pull Request #109639 · godotengine/godotNote Testing needed on various hardware configurations: V-Sync on/off, various refresh rates, pen tablet. Make sure to build with optimizations enabled, or use the Windows release export template l...

Sure

But this doesn't fix GPU rendering on the steam deck, The deck doesn't even use a cursor..

You may need to be more specific about what you're looking for, then, and likely submit bug reports, PRs, etc for the specific perf issues you're running into 😅

I wasn't sure I'd be seeing you around today- Mainly I'm having issues with uncontrollable rendering tasks that Godot takes on for my game's pipeline, which seems to spike up usage for igpu devices and no real desktop hardware, So both the deck and my Linux/windows laptop.. I don't make issues..

github.comIssues · godotengine/godotGodot Engine – Multi-platform 2D and 3D game engine - Issues · godotengine/godot

Submitting bug reports for things you run into on Godot's issue tracker is the best way to get eyes on them and potentially have them fixed: github.com/godotengine/... If you never tell anyone you're having issues, you can't expect them to know about the issues much less fix them 😅

github.comPerformance on 3D games varies on mobile APUS · godotengine godot-proposals · Discussion #13860I ran multiple tests and tweaks on my steam deck and laptop to figure out why the amount of nodes and they're resources bog down their hardware compared to my desktop with it's desktop Ryzen 5 and ...

I did make a post? just not a issue.. Plus unless my project is apart of some Godot advertised programmers for developers to get easy support and validation I still need to submit my project by the time it has to be investigated.. github.com/godotengine/...

You made the post in the proposals repository, which is for adding new features and functionality; issues with performance would probably belong better on the main repo's issue tracker (i.e., they'd get more attention from people poised to address perf problems).

In order for other volunteers to be able to look into the problem more and potentially come up with a solution for it, you'll also likely need to create a minimum reproducible project (MRP) that they can download and run to get the same problems you're hitting, as a baseline for what to improve.

3/8/26, 7:26 pm0 reposts2 likes

Yeah, But after making the MRP and not hitting the same issue exactly I was quick to drop it and come back to it later. Especially because I was considering getting a custom upscaler of sorts just to have my own solution to the issue only I'm supposedly facing for my project..

Yep, I definitely get that it can be time consuming and/or tricky to make an MRP. But without doing it (or even submitting a bug report issue for the problem you're experiencing) you can't blame the Godot contributors for not knowing about it, or expect them to fix it 😅