Crash on scripting_method_invoke when entering the Play Mode

Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

This is not a Unity bug. There are multiple issues with the repro project, specifically related to the attempt to use the myS7ProSimLib.dll which is a native wrapper (generated by Tlbimp.exe) for the native COM DLL s7wspsmx.dll (which comes from Siemens originally): Firstly, the 32 bit native COM DLL s7wspsmx.dll cannot work on MacOS - it's a native Windows DLL. This is the cause of the crash on that platform when we try to interop. Secondly, the essence of the code (myS7ProSimLib.dll wrapping s7wspsmx.dll) appears to be from https://github.com/TheFern2/myS7ProSimLib and as the author mentions there, this will only work in a 32 bit Unity Editor, where we no longer have a supported 32 bit Editor. Thirdly, according to DependencyWalker s7wspsmx.dll depends on MFC71.DLL and msvcr71.dll. These are very old Microsoft DLLs and are not easily obtainable anymore, are not likely to be present on modern Windows machines and are not present in the repro project. The DLL could not be used (even in a 32 bit Unity Editor) without these.

This is not a Unity bug. There are multiple issues with the repro project, specifically related to the attempt to use the myS7ProSimLib.dll which is a native wrapper (generated by Tlbimp.exe) for the native COM DLL s7wspsmx.dll (which comes from Siemens originally): Firstly, the 32 bit native COM DLL s7wspsmx.dll cannot work on MacOS - it's a native Windows DLL. This is the cause of the crash on that platform when we try to interop. Secondly, the essence of the code (myS7ProSimLib.dll wrapping s7wspsmx.dll) appears to be from https://github.com/TheFern2/myS7ProSimLib and as the author mentions there, this will only work in a 32 bit Unity Editor, where we no longer have a supported 32 bit Editor. Thirdly, according to DependencyWalker s7wspsmx.dll depends on MFC71.DLL and msvcr71.dll. These are very old Microsoft DLLs and are not easily obtainable anymore, are not likely to be present on modern Windows machines and are not present in the repro project. The DLL could not be used (even in a 32 bit Unity Editor) without these.

This is not a Unity bug. There are multiple issues with the repro project, specifically related to the attempt to use the myS7ProSimLib.dll which is a native wrapper (generated by Tlbimp.exe) for the native COM DLL s7wspsmx.dll (which comes from Siemens originally): Firstly, the 32 bit native COM DLL s7wspsmx.dll cannot work on MacOS - it's a native Windows DLL. This is the cause of the crash on that platform when we try to interop. Secondly, the essence of the code (myS7ProSimLib.dll wrapping s7wspsmx.dll) appears to be from https://github.com/TheFern2/myS7ProSimLib and as the author mentions there, this will only work in a 32 bit Unity Editor, where we no longer have a supported 32 bit Editor. Thirdly, according to DependencyWalker s7wspsmx.dll depends on MFC71.DLL and msvcr71.dll. These are very old Microsoft DLLs and are not easily obtainable anymore, are not likely to be present on modern Windows machines and are not present in the repro project. The DLL could not be used (even in a 32 bit Unity Editor) without these.