Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.2.0a5
Issue ID
1016336
Regression
No
Vulkan renderer doesn't handle V Sync quality settings correctly
The Vulkan renderer seems to produce undesired behaviours when V Sync Count is set to anything but Don't Sync. These behaviours don't appear when using other Graphics APIs with the same settings. The attached project contains two examples using 2018.2.0a5.
I've tested this on 2017.3 and the undesired behavior actually always occurs on that version, no matter what v sync setting you use, so this isn't a regression.
Example A: Particles
1. Open the attached project
2. Build the scene "11_Particles" as a Windows Standalone with Vulkan
3. When booting the player, select the quality setting "Fantastic - No V Sync" from the launcher
4. When the scene loads, observe the "Emit over distance" particle system. This is the desired behaviour
5. Restart the player and choose the quality setting "Fantastic - Every V Blank"
6. When the scene loads, observe the "Emit over distance" particle system again
Example B: 3D Physics
1. Open the attached project
2. Build the scene "09_3D physics" as a Windows Standalone with Vulkan
3. When booting the player, select the quality setting "Fantastic - No V Sync" from the launcher
4. When the scene loads, watch the colliders light up in the "Collider Stay" section. This is desired behaviour.
5. Restart the player and choose the quality setting "Fantastic - Every V Blank"
6. When the scene loads, observe the "Collider Stay" section again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment