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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
This is a duplicate of issue #1017374