Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
[Windows] NullReferenceException calling into native plugin on Windows in Editor with .NET 4.x runtime
How to reproduce:
1. Download attached project file and open this TestInputManager scene.
2. Enter Play mode (notice the Exception below in the console)
Actual result: When running in the editor on Windows with the 4.x runtime, it'll throw a NullReferenceException calling into a static method on the native plugin (Native.Init() in InControl/Source/Native/Native.cs). This is the first plugin method called (during OnEnable() as I recall) so no other plugin methods get a chance to be called, but I'd assume they'd all throw exceptions.
Reproduced with: 2017.1.3p1, 2017.2.1p3, 2017.3.1p1, 2018.1.0b8, 2018.2.0a1
Note: If you switch the runtime back to the default, it will work fine, and it also works fine in builds with the experimental runtime leading me to believe it's a bug with experimental runtime in the editor.
Fixed in: 2018.1.0f1, 2018.2.0a8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset