Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.1.0a1
2018.1.5f1
Issue ID
1050962
Regression
Yes
UNITY_2017_4_OR_NEWER preprocessor is not recognised when using #if UNITY_2017_4_OR_NEWER in a script
To reproduce:
1. Open any script in any project
2. Add preprocessor #if UNITY_2017_4_OR_NEWER
Expected: UNITY_2017_4_OR_NEWER is recognized as preprocessor command
Actual: UNITY_2017_4_OR_NEWER is not recognized (code inside #if is not executed)
Reproduced in: 2018.1.0a1, 2018.1.7f1, 2018.2.0b11, 2018.3.0a3
Not reproduced in: 2017.4.6f1
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
- Caret moves by a character when typing "." and any number into 'Grid and Snap' toolbar's input field
- Missing #pragma directives warnings appear in Inspector when including .hlsl file in Shader
- Fixed Timestep setting gets resets to default when upgrading project
- Console displays "NullReferenceException: Object reference not set to an instance of an object." during Editor Theme change
- Editor interface has low contrast when any theme is used
Ashwink2
Jul 08, 2019 09:12
I am inviting more people and my friends http://mahjongfreegames.online/dark-dimensions here to join and play Mahjong dark dimension games for free.