Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
Issue ID
1104680
Regression
No
[Oculus GO] Using GPU Instancing takes excessive time to load shaders when calling Warmup() on Shader Variant Collection
To reproduce:
1. Build attached project "Instance Leak Files.zip" to Oculus GO
2. While in built app, press Button One on Oculus controller
3. Observe the screen and Logcat output
Expected: Shader WarmUp() takes excessive time to warm up (~45 seconds)
Actual: Shader WarmUp() takes several seconds to load at max
Reproduced in: 2018.2.20f1
Not reproduced in: 2018.3.3f1, 2019.1.0b1, 2019.2.0a3
Note1: issue is also reportedly consuming sizeable amounts of memory
Note2: does not reproduce if GPU instancing is disabled
Note3; project freezes on launch in 2017.4.19f1, likely an issue of backwards incompatibility
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