Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.18f1
2021.1
2021.2
2022.1
Issue ID
1364970
Regression
No
Editor windows become inaccesible when disabling additional monitors
Steps to reproduce:
1. Set up two monitors and extend screen across them
2. (In case a laptop is used) Set the external monitor as your main display
3. Create an empty project and place the Editor on your main display
4. Drag the Game view onto the secondary monitor
5. Unplug the main monitor
Expected result: the Game view is present on the screen
Actual result: the Game view is not present on the screen
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a13
Notes:
- user reports, that VFX Graph window automatically opens on switched off Wacom One tablet (connected to the computer), thus preventing the user from interacting with this window
- this issue affects many (if not all) windows in Unity: Inspector, Visual Effect Graph, Shader Graph windows, etc.
- there are multiple ways to reproduce the issue: you can switch screen projection to a single monitor, in which the Game view is present, instead of unplugging the monitor
- tested with Windows 10 only
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1