   ODE for ".NET2.0"
  Hi all,I converted ODE.NET to be compatible with ".NET 2.0" and DirectX 9.0c Whidbey (Beta).I'm the only one who tested it so I could use some feedback.ODE.NET2
  Very, very, cool.  The sad thing about the living .NET binding(s) to ODE is that they arn't compatible with Mono (Linux/Mac) because they're writen in C++/CLI.  There is the Tao Framework's Tao.Ode, but it's a bit buggy and very low level.I started up OdeDotNet with the current maintainer of Tao.Ode (C0d3g33k) which provides an object oriented interface ontop of Tao.Ode (much like SDL.NET does for Tao.Sdl).  This is Mono compatible and should beable to compile in .NET 2.0, but it's not really functional and the collision system doesn't work because of the bugs in Tao.Ode.  Terry and I are still trying to find the problems.  Part of the problem is a lack of time [wink].   ;  Hm... Rob, I'd suggest you to take a look at what is done in ODE.NET to handle TriMesh Geoms. I refused using OdeDotNet because of actually stubing TriMesh functionality as undiscovered (check out comment nearby TriMesh-code). Also I found that it's quite tricky to build TaoOde. PostProcess needs aspirin for unprepared builders to execute it at last :)And a question in the end: did anyone thought of totaly rewriting ODE in Managed Code? It could look nice :) also it might bring back programming interest to make it better. And off course you feel more safe and comfortable when your code is less unsafe and nonportable.   ;Quote:Original post by Anonymous PosterHm... Rob, I'd suggest you to take a look at what is done in ODE.NET to handle TriMesh Geoms. I refused using OdeDotNet because of actually stubing TriMesh functionality as undiscovered (check out comment nearby TriMesh-code). Also I found that it's quite tricky to build TaoOde. PostProcess needs aspirin for unprepared builders to execute it at last :)The Tao Framework needs to have a little talk about .NET 2.0 builds.  Continuing support for .NET 1.1 is also debatable, so we'll see.  Also, ODE 0.6 final is apparently right around the corner so I think we're going to wait a bit before we do anything with it.  The only problem is that the post processing for .NET 1.1 is a major pain...Quote:Original post by Anonymous PosterAnd a question in the end: did anyone thought of totaly rewriting ODE in Managed Code? It could look nice :) also it might bring back programming interest to make it better. And off course you feel more safe and comfortable when your code is less unsafe and nonportable.Terry mentioned a complete C# port of ODE, but always daunted on the task.  I completely agree that it would be so much nicer to have, but considering the amount of work and maintenance that would be required....... [wink]   ;  Hm... I shall take a look at what can be done next month. I think it's quite dumb but time consuming work... I'll let you know here. (BTW: ODE 0.6 is already here ;) as you know I think :) )   ;  Far as I can tell, ODE 0.6 is in the bag (RC3 was the last RC).By the way: there once was a simple P/Invoke wrapper for ODE. I think that's the right way to do it -- adding a new function is really simple, and it's all in a single source file. No additional classes or overhead needed.In fact, I think anyone could wrap the functions they need out of ODE using P/Invoke in an hour or so...   ;Quote:Original post by hplus0603Far as I can tell, ODE 0.6 is in the bag (RC3 was the last RC).By the way: there once was a simple P/Invoke wrapper for ODE. I think that's the right way to do it -- adding a new function is really simple, and it's all in a single source file. No additional classes or overhead needed.In fact, I think anyone could wrap the functions they need out of ODE using P/Invoke in an hour or so...I think that is what is done with Tao.   ;Quote:Original post by jflangloisQuote:Original post by hplus0603By the way: there once was a simple P/Invoke wrapper for ODE. I think that's the right way to do it -- adding a new function is really simple, and it's all in a single source file. No additional classes or overhead needed.I think that is what is done with Tao.Yup, Terry (current maintainer of Tao.Ode) mentioned that although ODE 0.6 is pretty much done, a lot of work is queued up for Tao.Ode to get it back on track.   