Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b21
Issue ID
806580
Regression
Yes
[Shaders] Some _Object2World references are not changed to unity_ObjectToWorld in 5.4
Reproduction Steps:
1. Create new project on Unity 5.3.4f1
2. Create new Shader
3. Copy Paste code from edit to the Shader
4. Notice that it compiles
5. Close project
6. Open this project with Unity 5.4.0b21
7. Notice that it does not compile anymore
Expected: All references to "_Object2World" should change to "unity_ObjectToWorld"
Actual: Not all references are changed. It is not renamed if "_Object2World" is followed by a period. (_Object2World.???)
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
QuantumTheory
Jul 14, 2016 21:25
Tested in 5.4.0f1. I have source control enabled and the shaders were not checked out, therefore they were not updated until I checked them out. Just a heads up.