Skip to content
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

Display the editor viewport resolution in the View Information pane #2205

Closed
mrjustaguy opened this issue Jan 30, 2021 · 0 comments · Fixed by godotengine/godot#45596
Closed

Comments

@mrjustaguy
Copy link

Describe the project you are working on

Not Related to any specific project

Describe the problem or limitation you are having in your project

Currently, the editor preview doesn't have anyway of finding the resolution it is rendering at, just the FPS (GPU/CPU times in G4.0) and things like camera position and rotation, number of draw calls, and Vertices and the like (of which only the camera position currently works on G4.0)

Without this information, you don't really know if your editor viewport is pumping 1mpx, 2mpx, or like 4-6 mpx picture depending on the viewport size on the monitor and it's resolution which also somewhat renders the FPS counter somewhat useless, as on a 4k display, you could be pumping a 1080p viewport and have good FPS but then when you run at 4k have a terrible frame rate and not know why.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Add Editor Viewport(s) resolution(s), and maybe even the total pixel count to View Information. This would give the user a sense of how taxing the Game World is (graphically) without actually running it, help with viewport customization and things like that..

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

When Viewport is initialized, Get it's resolution and put it in View Information with the other data, if the Viewport gets scaled, update the information, For multiple viewports say something like:
Viewport 1 Resolution XXXX YYYY
Viewport 2 Resulution XXXX YYYY

If this enhancement will not be used often, can it be worked around with a few lines of script?

You can run the project and specify the resolution it runs at, aside from that no.

Is there a reason why this should be core and not an add-on in the asset library?

It's a part of a core functionality, also Could be useful along side something like #2125

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants