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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Add comment