Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
2021.2.0a10
Issue ID
1323970
Regression
No
Player Development Console doesn't scale with Display Scaling
Reproduction steps:
1. Open windows Display Settings and set scaling to 100%
2. Open attached Project "ConsoleScaling"
3. Build a Development Build with Script Debugging enabled
4. Run the Built Game
5. Take a note of how console looks like and close the application
6. In display settings, set scaling to 200%
7. Build and Run a Development Build again
Expected result: The Console Scales to the % set in Display Scaling (is twice as big in this case)
Actual result: The Console Scale is at 100%
Reproducible with: 2018.4.33f1, 2019.4.24f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a10, 2021.2.0a18
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
- Low FPS in the Game View when the Editor window loses focus
- Memory leak when a domain is reloaded on a Scene that uses HDRP's water simulation resources
Resolution Note:
Currently we dont have a proper support for high dpi scaling in IMGUI to fix this issue with small changes. This case requires an overhaul of DeveloperConsole to support the High dpi scaling which will be taken care by UITK team later.