-
-
Notifications
You must be signed in to change notification settings - Fork 22k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profiler: usability ideas #5682
Comments
Not critical for the upcoming 2.1, so moving to the next milestone. |
Being able to order the functions by time spent would massively improve the usability of the profiler. (As simple as making the click on the header sort decreasing/increasing) |
Bump. Zooming in and ordering are needed. Also in the monitors tab, what is the range of values for fps? It's weirdly difficult to see the difference between 15 and 30 FPS. P.S. Where should I look if I want to improve those things? |
Solves godotengine#25328 and partially godotengine#5682
Note: Ordering functions from most to least expensive has already been implemented in 3.1 and later by #25354. Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated [Godot Improvement Proposals (GIP)](https://github.com/god The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker. If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance! |
After testing a bit the profiler, I have a few ideas to improve its usability:
Could we have zoom or something allowing easy precision?
The text was updated successfully, but these errors were encountered: