Search Issue Tracker
Won't Fix
Votes
3
Found in
2023.1.0a6
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-1567
Regression
No
[Linux] Frame rate gets capped in Player when two high refresh rate monitors are used
Reproduction steps:
1. Download and open the attached project: "LinuxBug-MultiScreen.zip"
2. Make sure you have two high refresh rate monitors connected (e.g. 120Hz)
3. Build the project
4. Run the built Player
5. Press the "Activate second screen" button in the Player
Expected result: The frame rate displayed in the top right corner does not change
Actual result: The frame rate gets capped at 60
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.2f1, 2021.2.0a12
Could not test with: 2018.4.34f1
Notes:
- Not reproducible on Windows
- Reproduced on Ubuntu 18.04 and 20.04
- If the Build and Run option is used, the frame rate will not get capped at first, but if the same executable is opened manually the problem still occurs
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This issue has been open a very long time and I'm afraid at this time we have to admit we're probably not going to fix this issue based on the configuration is not common and higher priority issues will always get fixed before this.