Irrlicht Engine

The problem is that it only responds to one key at a time, unless two keys were pressed simultaneously (i.e. pressing A turns left, but pressing W while holding down A stops turning and only moves forward.

I don't have that problem. Just have your event handler set boolean variables and then ...

i also find it crashed when i use remove, but i think it has something to do with perhaps how i attached an animator to the node. i think if you remove a node with no animator attached it might not crash

in the examples folder inside the zipfile that irrlicht comes in

Now I see the problem. The irrlicht documentation simply shows the C# constructor as


public ISceneManager( ISceneManager* manager );


But in reality (as I determined via MS VS.NET's intelisense) it is:

public Irrlicht.Scene.ISceneManager( irr.scene.ISceneManager* manager );


Seeing as how ...

Multiple scene managers are most definitely supported in C++. It looks like you should be able to do it in C#, but I'm no C# programmer. Does the code you've presented not work? Seems like this should work...


The C# constructor for ISceneManager is
public ISceneManager( ISceneManager* manager ...

it appears that maybe this is supported in c++ but not c#.net? is that true?

Ok, refining my question. Why is there not createNewSceneManager() in .net version? OR why is the constructor ISceneManager.ISceneManager(irr.scene.ISceneManager* manager) which requires a pointer to a another ISceneManager and how do I get such a pointer in C#?

This is just some concept code for something that would be cool if irrlicht allowed it. Does anyone know of a way to do this sort of thing with irrlicht as it stands right now? Is this sort of functionality something that could possibly be included in a future release?


int currentScene = 0 ...

Since each device only has one scene manager, what is the easiest way to switch between a menu to gameplay? I know i did this in c++ a long time ago with like 0.6 version of the engine, but i don't have the code handy, and i'm using c# now anyway.

Well, I just tried it, and I don't think I can. The second argument of CreateCollisionResponseAnimator is a scene node, so you must have to make one for every scene node.

the last value in CreateCollisionResponseAnimator() is the slide factor. Maybe that's it. Might help if you post your call to that function.

Currently I have made a class that holds an IAnimatedMeshSceneNode and an ISceneNodeAnimator. In the class I have the following function to attach a new CollisionResponseAnimator to the contained node. My question is, do I really need a separate animator for each node to handle the gravity like I am ...