Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b8
2018.2.0a1
Issue ID
1005138
Regression
Yes
[Regression] "Unsafe code requires the `unsafe' command line option to be specified" appears in console
How to reproduce:
1. Download and open attached project file
2. Notice the errors in the Console Window
Actual result: In 2018.1.0b7 script works fine, from 2018.1.0b8 error "Assets/LeapMotion/Core/Scripts/Utils/BitConverterNonAlloc.cs(17,7): error CS0227: Unsafe code requires the `unsafe' command line option to be specified" Appears
Reproduced with: 2018.1.0b8, 2018.1.0b9, 2018.2.0a1
Not reproduced with: 2017.3.1p2, 2018.1.0b7
Regression since: 2018.1.0b8, 2018.2.0a1
--------------------------------------------
Solution: This is a change in behaviour. Allow unsafe code option now has to be enabled in player settings for Assembly-CSharp.dll and in the .asmdef inspector for .asmdef assemblies.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment