08-31-2018, 01:20 AM
Seems to be related to the C# "delegates" (the equivalent of C function pointers).
The correct startup and render the full frame denotes correct matching of .net/native dll. If not, it wouldn' start at all.
The fact that it crashes when the delegate callback is called denotes a delegate managing problem, something that can be tricky.
The error happens only running from the debugger in SharpDevelop? Can you run the executable directly from the command line or double-clicking it? We have to discard the environment itself doing funny things. My test environment is Visual Studio (it's free) and it runs there.
The correct startup and render the full frame denotes correct matching of .net/native dll. If not, it wouldn' start at all.
The fact that it crashes when the delegate callback is called denotes a delegate managing problem, something that can be tricky.
The error happens only running from the debugger in SharpDevelop? Can you run the executable directly from the command line or double-clicking it? We have to discard the environment itself doing funny things. My test environment is Visual Studio (it's free) and it runs there.