Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2017.4.X, 2018.3.X, 2019.1.X
Votes
0
Found in
2017.4.10f1
2018.2.20f1
Issue ID
1113175
Regression
No
UNITY_VERSION Shader Macro returns wrong value for two-digit minor version number
How to reproduce:
1. Open attached project with Unity 2018.2.20f1
2. Reimport UnityVersionTest.shader. It checks the current Unity version and emits an error if it's newer than 2018.2
Actual results: since it can hold only one digit value it returns wrong version
Expected results: UNITY_VERSION should return correct Unity version
Reproducible with: 2017.4.18f1, 2018.2.20f1 (any version that contains two digit minor version number)
Not reproducible with: 2018.3.1f1, 2019.1.0a13
Fixed in: 2019.2.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Add comment