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
Comments (1)
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
- Buttons in the Overlay Menu in the Scene View are all gray even if they're activated when Game View is maximized and minimized
- NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
- Editor crashes on PrepareSpriteTilingData when exiting Play mode
LouisElliott
Aug 18, 2020 08:36
This is a minor level mistake but I cannot compromise on it since I am using the premium version of this tool. I do not want to encounter any single problem after spending so much money on this tool. A reasonable solution must be provided. To avoid mistakes in the assignments students trust to read edubirdie reviews on https://top5writingservices.com/is-edubirdie-legit-and-safe-to-use/ website so that they can track excellent writers for their essays.