Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.1f1
Issue ID
843277
Regression
No
Calling to MF .Net created objects during runtime results in a crash
Steps to reproduce:
1. Download and open the attached project (case_843277-MFTest\MFTest\Unity\MFTest)
2. Press play
Result: crash
Reproduced on 5.2.3f1. 5.3.6f1, 5.4.2f1, 5.5.0b9, 5.6.0a1
Note: There are 3 projects attached within - a C++ version, a C# version and a Unity version
Note: User is trying to integrate MF .Net into Unity. This C# set-up works in VS/Monodevelop (even if in it's current state it does not do much besides call), but results in a crash when ported into Unity
Note: Crashes when getting to the first call in Main.cs, line 22
----------------------------------------------------------------------
COM Interop is not a supported technology within Unity and MF .Net seems to make extensive use of it.
The recommended way to access these Win32 APIs would be to expose simple C APIs to managed code via PInvoke and handle the COM logic in a native library
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment