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
- VR build is not displayed when headset is in standby upon initial launch
- Subasset references are incorrectly redirected when editing prefabs in Prefab Mode
- [macOS] KeyDownEvent.originalMousePosition returns incorrect coordinates when last focused element was a TextField in text editing mode
- Some HDRP Wizard tooltips are rendered outside the window
- Shader error is thrown when using a Compute Shader with a second kernel
Add comment