Search Issue Tracker
Fixed in 5.3.2
Votes
0
Found in
5.2.1f1
Issue ID
730289
Regression
No
[UWP] x64 platform application throws exceptions in the output
On UWP x64 platform project throws exceptions:
NullReferenceException: Object reference not set to an instance of an object.
at EVP.VehicleController.FixedUpdate()
at EVP.VehicleController.$Invoke11(Int64 instance, Int64* args)
at UnityEngine.Internal.$MethodUtility.InvokeMethod(Int64 instance, Int64* args, IntPtr method)
(Filename: <Unknown> Line: 0)
NullReferenceException: Object reference not set to an instance of an object.
at EVP.VehicleTireEffects.UpdateTireMarks(WheelData wheelData, TireFxData fxData)
at EVP.VehicleTireEffects.Update()
at EVP.VehicleTireEffects.$Invoke7(Int64 instance, Int64* args)
at UnityEngine.Internal.$MethodUtility.InvokeMethod(Int64 instance, Int64* args, IntPtr method)
(Filename: <Unknown> Line: 0)
Reproducible on 5.2, 5.3 versions.
Repro steps:
1. open project "case_730289-repro".
2. build to Universal 10 platform.
3. build and run generated solution on x86 platform. No errors in the output.
4. build on x64 platform. Errors are spammed in the output.
Workaround: use x86 platform.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment