Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
31
Found in
2018.3.0b4
2018.3.0b11
2019.1.0a1
Issue ID
1107819
Regression
Yes
Unity outputs a warning in a Windows 64bit Standalone Player when using built-in Shaders
To reproduce:
1. Open attached project
2. Build & Run a Windows 64bit Standalone Player
3. Open player log file "C:\Users\%UserName%\AppData\LocalLow\DefaultCompany\Wolf\output_log.txt"
4. Check that it contains a "Shader Unsupported" warning
Actual results: "Shader Unsupported" warning
Expected results: Unity built-in shaders should not contain any warnings and errors
Reproducible with: 2018.3.0b4, 2018.3.0f1, 2019.1.0a11
Not reproducible with: 2017.4.17f1, 2018.3.0b3
Regressed version: 2018.3.0b4
Fixed in: 2018.3.13f1, 2019.2.0a10
Notes: WARNING: Shader Unsupported: 'Legacy Shaders/Diffuse' - Pass 'Meta' has no vertex shader
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment