Why don't you 'keep the doors open' yourself? Let Niko do the Engine development while you are writing the Interop / PInvoke wrapper or is there any reason why you want Niko to do that and not writing the wrapper yourself?Guesty wrote:For my last evaluation of Axiom I found its performance easily compariable to OGRE3D; it also easily ran out of the box under Linux, apparently, as evidenced by the now defunct Axiom forums and several posts on the RealmForge forums (who have currently forked Axiom due to the lead developer of Axiom suffering rock-star syndrome followed closely by 'nobody's home' syndrome).
I will agree that the .NET wrapper has advanced with significant progress thanks to niko and programming it in mixed mode C++.NET, but I would still like to "keep the doors open" as it were to run applications under Mono. Irrlicht has the most promising potential; of all the engines that had managed interfaces I would rate it second best only to TV3D, which is also, unfortunately, Windows-only. 6.5 promises an incrediblyh nice managed api, though, instead of ugly COM-interop.
Can't fault me for pushing my own interests above yours, can you?
Its the way most humans work.
...and 'no', you do not push your interests above mine ! Irrlicht has all the features we need for our Projects and if there were no wrapper at all, we would code our own, so it doesn't affect our 'interests' if Niko would code the Interop / PInvoke wrapper for you. But it would affect the upcoming Irrlicht C# Community who will have to wait much longer til they can use all the features of Irrlicht using C#. And it would affect the bug-fixing process on Irrlicht, cause there is ONLY ONE developer for all the tasks.
So plz don't demand such features - help the Community and start coding the wrapper yourself - I have also posted that we would support (if time permits) any developer or team who wants to do the Interop / PInvoke wrapper!
Duncan
--
Tucan Entertainment