Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b13
Issue ID
1045450
Regression
No
Not using "unity_ObjectToWorld" causes calculation error in shader
Reproduction steps:
1. Open "instanceShaderBug.zip" project
2. Open "SampleScene" scene
3. Enter Play mode
4. See that a Red Cube is rendered
5. Exit Play mode
6. Edit "ErrorInstance" shader
7. Comment line 43
8. Uncomment line 46
9. Enter Play mode
Expected Result: With or without "unity_ObjectToWorld", no calculation error should occur
Actual Result: Not using "unity_ObjectToWorld" causes calculation error
Reproduced with: 2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2017.3.2f1, 2017.2.3f1, 2017.1.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment