Found out that when using class destructor for cleaning up lite-c structs is just like miracle wand. Now i never want to leave C#.

And by the way layer property should be double as it can be 3.01 too not only int. Even in PANEL class it gets converted as double.

And why here isnt implemented randomize() function, but random() and random_seed() is? Without that function all others is useless.

And i hope MULTIMEDIA gets managed by C# as there is no such object in lite-c.

And could it be when closing 3DGS window C# is running for some frames after? Im saying because im getting corrupt memory message then, but when closing console window first it didnt happens. Ahh. Found out it is destructor. Seems when i said it to remove unmanaged resources it cant do it when 3DGS is already closed. It was easely fixable by adding static variable which on engine exit lets C# know it.

Also you could tell how to get rid of that console at final version.

How does your wrapper handles TEXT object strings?
As i saw it uses string copying to native TEXT structs.
But that way copying makes string still managed or is it copied through lite-c function and gets unmanaged?
I say this because TEXT strings need to be manually removed from TEXT before you remove that itself. It is even said in manual.
But if this is true that strings will stay in memory.

Also i dont like TEXT.strings property as it now allows only to set and get whole array. it could even stay so, but you should warn users. Cant get out one element so i need to use getString.

I haven't used the acknex engine for some time now and currently am not planning to - unfortunately I can't help you with most of them as it's very rare that I visit this site anymore... and don't remember that much about the wrapper anymore to help you without digging into the materia myself - I'm sorry !

>>Also you could tell how to get rid of that console at final version.
change the type of your application from console to I think Application in the project properties

Pity you here left your project, this wrapper is best thing what ever happened with this engine.

Yes. C# together with proper tooling (editors!) would help the engine a lot.
Anyway I remember looking at some code of the wrapper and it really helped me to get the engine running in an managed Winforms environment and dealing with marshalling. I used C++/CLI, but the methods were pretty much the same.

Very useful project