Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0b10
Issue ID
969340
Regression
Yes
Standard shader MeshRenderer invisible on Android Vulkan
Simple scene with just a MeshRenderer with Standard shader and a Camera. Object not rendering on device.
Repro steps:
1. Open scene.unity
2. Build and Run to Android
3. Result: Solid camera color, no visible sphere
Notes:
Bug behavior consistent if material is Standard or Default/Diffuse shader.
Does not manifest if material is Unlit/Color or Unlit/Texture.
To isolate the bug, this test scene has the Camera in Forward mode, HDR is disabled, all shadows are disabled, MSAA is disabled, no objects are in scene other than the MeshRenderer and Camera (not even a light).
Device:
Samsung S8 (SM-G950U), Adreno 540, Android 7.0, firmware version G950USQU1AQJ8 (latest)
Confirmed in:
2018.2.0a1
2018.1.0b2
2018.1.0a5
2017.3.0b10
Not reproducible in:
Version 2017.2.0f3
License type: Pro
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
- Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
This is a duplicate of issue #963224