Search Issue Tracker
By Design
Votes
0
Found in
2018.4.0f1
2019.1.14f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1189496
Regression
No
Texture Streaming is not applied to GameObject when using custom shader
How to reproduce:
1. Open the attached 'TextureStreamingDebug.zip' project
2. Open 'SampleScene' Scene
3. Enter Play Mode
4. Press 'Space' key
5. Press 'P' key when GameObjects are clearly seen in the Scene
Expected result: 'BROKEN TEXTURE STREAMING GO' GameObject is green
Actual result: 'BROKEN TEXTURE STREAMING GO' GameObject is blue
Reproducible with: 2018.4.11f1, 2019.2.8f1, 2019.3.0b7, 2020.1.0a8
Could not test: 2017.4.33f1 Cinemachine is not introduced
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note:
To know which texture to choose for the streaming debug visualization, it always uses the _MainTex texture parameter of the material. The shader used here has no _MainTex so the visualization does not know which of the textures in the shader to choose. You should ensure your material always has a _MainTex texture parameter (and assigned a texture to it) for the debug visualization to work correctly. If not, streaming will still work but the visualization will show incorrect results as you are currently experiencing.