Search Issue Tracker
By Design
Votes
3
Found in
5.4.1f1
Issue ID
833092
Regression
No
Unity Standalone build stutters on 59 hertz monitors with vSync enabled
Reproduction steps:
1. Open the "StutterTest2.zip" project
2. Build "Test" scene with Autoconnected Profiler setting enabled
3. Play the build
4. Wait for the game to stutter
5. Notice the "Gfx.WaitForPresent" spike in the CPU Profiler
Actual result: Standalone build stutters.
Expected result: Standalone runs smoothly on 59-hertz monitor with vSync enabled.
Note: Issue is only present on 59-hertz monitors with vSync count set to "Every V Blank"
Note: Issue is reproducible on all DirectX and OpenGL graphics APIs
Reproduced on: 5.5.0b5, 5.4.1p1, 5.3.6p4, 5.2.5f1
Comments (1)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
touzov
Feb 19, 2017 19:27
the issue still present in 5.5.1
QualitySettings.vSyncCount =0