-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
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
No way to start Profiler before starting game #72524
Comments
|
As this is the 4.0 build (# 71111 is still on 3.x) and the Profiler does work once the game is running, I'm not sure the two issues are related. |
Whoops, didn't notice THAT. Right. |
The lack of autostart functionality is being tracked in godotengine/godot-proposals#6017. cc @Faless, as they rewrote the editor debugger for 4.0. |
I think this was changed in #70151 which fixed some other inconsistencies with the profiler Start/Stop buttons. |
@lostminds There is a autostart PR for this feature. I am waiting for review. |
This was implemented by #96759 (with slightly different UX), closing. |
Godot version
4.0 Beta 16
System information
Windows 11 Vulkan
Issue description
In the online manual, it states:
I want to be able to profile my game's startup time to suss out any bottlenecks during startup.
However, the option to start profiling before the game as it starts is not possible in the current 4.0 build. In 3.x, this option is available.
Steps to reproduce
Click on the Debugger tab at the bottom of the screen.
Click on the Profiler tab in the Debugger window.
Notice that you cannot press "Start".
Start any scene.
Notice that you can now press "Start"
Stop the scene.
Notice that you can no longer press "Start" on the profiler.
Minimal reproduction project
This issue is apparent regardless of the project.
The text was updated successfully, but these errors were encountered: