Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b12
Issue ID
1017103
Regression
No
[Graphics General] Textures are not rendered with ScriptableRenderPipeline when build created with WebGL/Facebook WebGL player.
Textures are not rendered with ScriptableRenderPipeline when build created with WebGL/Facebook WebGL player using OpenGLES3 Graphics API.
Steps to repro:
1. Open attached project.(ScriptableRenderPipeline scene from Shinai project)
2. File > Build Settings > Select WebGL/Facebook WebGL > Switch Platform.
3. Player Settings > Other Settings > Uncheck Auto-Graphics API.
4. Select OpenGLES3 in Graphics APIs list.
5. Click on Build And Run
Observe that Textures are not rendered.
Reproducible on: 2018.1.b12, 2018.1.b1, 2017.3.0f3 , 2017.2.0f3, 2017.1.0f3.
Environment:
Windows 10, Windows7, Mac 10.13, Mac 10.12.
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
This is a duplicate of issue #1017374