You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like having the debug overlay enabled so I can open any of the various debugging windows when the situation calls for it. However the FPS Window being open by default feels arbitrary (why does it take precedence over other debugging windows?) and gets in the way of the presentation of my game.
Picture a scenario where I give someone a build of my game for play-testing. If the debug overlay is enabled the play-tester can recognize what it is and just ignore it and play the game normally. If necessary I can ask them "Hey, something's going on that's not intended in this part. Can you open the FPS/Memory/Texture/whatever window so I can take a look at it".
Having the FPS window on by default - even when it's minimized - is really distracting and gets in the way of the game's presentation.
I understand that:
Previously the debug overlay was the FPS counter only.
You can just ask people to close it.
But now that the functionality of the debug overlay has been greatly extended; it doesn't make sense for it to be the default window that's always open. And even though you can just close it, it feels like a weird unnecessary step that shouldn't be there. As the developer of the game I feel I should be in control of what gets presented to the player by default.
Describe the solution you'd like
Setting show_debug_overlay to true should enable the debug overlay with no other windows open.
There should be a command for opening a specific window.
That way, in the create event of an initialization object, you could go:
In this example, the second argument could be repurposed for if you want the top bar of show_debug_overlay to be visible. As opposed to it being for if you want the default FPS window to be minimized.
Ideally, dbg_view_open could also be used for things such as: a clickable button or key bind that opens a specific debugging windows. That way pressing tilde or F1 could bring up the console without necessarily enabling the top bar.
Describe alternatives you've considered
show_debug_overlay(true, true);
The second argument is changed so the FPS window is closed, not minimized, by default.
Additional context
No response
The text was updated successfully, but these errors were encountered:
YYDan
changed the title
Debug View: The FPS Window shouldn't be open by default.
In-Game: debug_view_open() could be extended so the FPS Window can be closed when opening the overlay
Dec 2, 2024
Is your feature request related to a problem?
I like having the debug overlay enabled so I can open any of the various debugging windows when the situation calls for it. However the FPS Window being open by default feels arbitrary (why does it take precedence over other debugging windows?) and gets in the way of the presentation of my game.
Picture a scenario where I give someone a build of my game for play-testing. If the debug overlay is enabled the play-tester can recognize what it is and just ignore it and play the game normally. If necessary I can ask them "Hey, something's going on that's not intended in this part. Can you open the FPS/Memory/Texture/whatever window so I can take a look at it".
Having the FPS window on by default - even when it's minimized - is really distracting and gets in the way of the game's presentation.
I understand that:
But now that the functionality of the debug overlay has been greatly extended; it doesn't make sense for it to be the default window that's always open. And even though you can just close it, it feels like a weird unnecessary step that shouldn't be there. As the developer of the game I feel I should be in control of what gets presented to the player by default.
Describe the solution you'd like
Setting
show_debug_overlay
totrue
should enable the debug overlay with no other windows open.There should be a command for opening a specific window.
That way, in the create event of an initialization object, you could go:
In this example, the second argument could be repurposed for if you want the top bar of show_debug_overlay to be visible. As opposed to it being for if you want the default FPS window to be minimized.
Ideally,
dbg_view_open
could also be used for things such as: a clickable button or key bind that opens a specific debugging windows. That way pressing tilde or F1 could bring up the console without necessarily enabling the top bar.Describe alternatives you've considered
show_debug_overlay(true, true);
The second argument is changed so the FPS window is closed, not minimized, by default.
Additional context
No response
The text was updated successfully, but these errors were encountered: