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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
- Video framerate is not restored when trying to raise it after lowering it to 10 FPS
- WebGPU: CreateRenderPipeline errors with ShaderVariantCollection warmup
Add comment