Irrlicht Engine

if you want a 4 dim representation you could take several such 3d blocks and put them next to each other, that shouldn't be much of a problem

Yeah XNA doesn't feel right in a sense that i don't feel comfortable when using it and this gives a more or less huge impact on development speed. I simply don't like the way XNA is structured, but to be honest i havent looked into it since 1.x as far as i can remember.

Thanks for the link

I somehow don't like XNA coding XNA just doesn't feel right ^^ Someone who continued developing the Irrlicht .NET bindings? That sounds awesome Does someone know how far the new bindings have allready proceeded?

Since the Irrlicht .NET bindings are currently not being worked on i started to look for a new engine with .NET bindings cause developing with .NET is quite important for me. The only problem is that i haven't found something suitable yet. I don't like Ogre. Horde3D is perhaps a tiny little bit too ...

I played around with Irrlichts collisiondetection and noticed that creating CollisionResponseAnimators for every single SceneNode ist definitely not a good way for doing collision detection on many SceneNodes (100-200). Currently i just want to test wether the nodes collided with the world (Q3 Octre...

@Steel Style: i am suggesting creating a class for bone based animations and a new scenenode which is specialised on bone based animations. If you use vertex animated models (e.g. MD2 ones) you won't be able to separate the animations from the model. Sure the index buffer will disposed the same way ...

I am not sure if you perhapts misunderstood me, especially this sentences: I would completely rewrite the CSkinnedMesh as it uses an old bone animation format. A vertex can only be affected by one bone/joint (i think that has been discussed in the MD5 Loader thread) The second one is directly relate...

It is ok to separate the different mesh types from each other and thats perfectly fine having a CSkinnedMesh and all the other CMesh classes. I would completely rewrite the CSkinnedMesh as it uses an old bone animation format. A vertex can only be affected by one bone/joint (i think that has been di...

Ok, so here are some ideas i have thought of. First of all i think, that it is really needed to separate vertex based animations and bone based animations. Trying to fit both into one interface would create a huge overhead. Vertex based animations (will be called VBA during the following text) mainl...

Ok guys i just thought: "why the hell should i start my own project? That's crazy and not really the spirit of open source." I could slap myself for thinking of movin' back to my old abandoned project. Ok here 's the plan. I will sit down and work out some possibilities how we could handle...

First of all: i misused the word keyframe animations, what i was talking about was vertex animation. So please replace the word keyframe animation everytime i used it with vertex animation. I never said that one would have to rewrite the engine in order to get Doom 3 models to work (i haven't rewrit...

Well, i need an animation system, which primarily focuses on bone animation. The one Irrlicht currently uses definitely doesn't focus on bone animation, it still sticks to keyframe animations. Sure there are structures to use bone animation, but they are not very good. I think that one would have to...

Yeah, totally forgot to mention, this is a known problem i am also encountering this problem, not yet sure why. I don't think that i will ever fix this problem. After toying around with Irrlicht again i noticed that the animation system Irrlicht currently uses doesn't fit my needs, so i will start w...

Looking forward to it

Ok here is the first sourcecode release of my MD5loader. Instructions how to use it can be found inside the readme. It's still in a very early alpha stage as you can see. We still have a long way to go. We have to especially look at the AnimatedMeshSceneNode and the current SkinnedMesh and decide wh...