-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Canvas Layer size not updating after changing Viewport Size in Project Settings #69208
Comments
Can you still reproduce this in 4.0.3 and 4.1-beta3 or later? |
Yes, I could still reproduce this issue in Godot 4.0.3 |
Not reproducable in Godot v4.3.dev (f8a2a91) - Windows 10.0.22621 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 Ti (NVIDIA; 31.0.15.4601) - 12th Gen Intel(R) Core(TM) i7-12700F (20 Threads) |
Can someone confirm this on 4.1.3 or 4.2.1? Otherwise this can be closed as fixed (otherwise the specific PR solving this should be identified and possibly cherry picked) |
Tested on Windows 10 on 4.2.1; experienced inconsistent latency in a brand new project. It ranged from being instant, to taking 15 seconds, to taking an indefinite amount of time. Toggling visibility instantly changes canvas, as well as zooming in/out. |
Reproducible on v4.3.beta.custom_build [93fc9b8] (on Windows 10). record_2024-06-26_21-39-37.mp4 |
I wanted to report this problem too, but I forgot... |
Godot version
v4.0.beta6.official [7f8ecff]
System information
Windows 10
Issue description
The Canvas Layer does not update it's size after changing the Viewport Size in the Project Settings.
To update the Canvas Layer size you need to uncheck visibility and check it again.
Issue.mp4
Steps to reproduce
Create a scene -> Add Canvas Layer -> Add any UI Element -> Change the viewport size
The Canvas Layer Size does not update accordingly.
It needs to be manually updated by toggling the visibility.
Edit: Resizing the Inspector Window or restarting the Project also updates the Canvas Layer
Minimal reproduction project
N/A
The text was updated successfully, but these errors were encountered: