Search Issue Tracker
Won't Fix
Votes
2
Found in
Issue ID
1111622
Regression
No
[Windows][DX12] When Gsync option is enabled in nVidia control, Player crashes on non-Gsync monitor when refresh rate is changed
This crash happens in a very specific condition:
- multiple monitor setup with one of them a Gsync monitor
- nVidia Gsync option is enabled
- Unity Player uses DX12, and runs in Exclusive FullScreen mode on the NON-Gsync monitor
- User changes the refresh rate
Repro:
1. Download and build the Windows Standalone Player
2. Make sure the nVidia G-sync option is enabled.
3. Launch the Player
4. Move the Player onto the Non-Gsync monitor if it is not on it.
5. Switch to Exclusive FullScreen mode
6. In the Resolution Dropdown menu, pick the option with current resolution but different refresh rate
7. Observe
Expected: The Player can change refresh rate without crashing.
Happens to: 2019.1.0a12, 2018.3.2f1
-
Tautvydas-Zilys
Jan 03, 2019 09:07
@TITAN_HUNTER you are NOT facing the same issue. This specific issue only affects Windows Standalone player with DX12 when going into exclusive fullscreen mode on a monitor that isn't a gsync monitor while a gsync monitor is connected.
Please report a separate bug.
-
Titan_Hunter
Jan 03, 2019 06:44
I am having the same issue. If I have G-SYNC enabled on my monitor the Unity editor will crash under small loads. If I open a new project in Unity it will lag and stutter but not crash until I start working on my project. If I activate play mode the lag immediately stops and everything goes full speed like it should, therefore it appears to be affecting the editor only.
My monitor is an Acer predator with G-SYNC
Current Unity version is 2018.3.0f2 but this has happened to me on previous versions of Unity as well.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.2.X):
Won't Fix