Irrlicht Engine

Yes, it's true, because when you create your own scene node and want it to render, you won't succede, until you set it as a child of an other scene node. I usually call smgr->getRootSceneNode() and set my node as a child of the root node.

I think that you shouldn't drop() them before calling grab() on them in your list, which takes care of them. Calling drop() on them before any other class called grab() causes them to cease to exist, which causes problems, when you try to access their formal memory location.

I think you must do a tutorial about how it is used. Example of put nodes, joint nodes, in a any level , and the most important , how is the fomat of the data save (net.txt) I will do a simple tut soon. But I can describe the data format immediately for you. It is not very neat and I should change ...

For those who wanted the counter tutorial - here it is: http://czestmyr.wz.cz/other/dvtut/dvtutorial.html The class itself changed a bit, so it won't function with the FPS demo project, but it's coded in a better way now. 2 elander: Of course I know that timing related to frames is really a bad idea...

Wow! Thanks for your feedback, people. Now to some questions and comments: In main.cpp change map-20kdm2.zip by map-20kdm2.pk3 Yes, I've changed that even before uploading it, but I must have uploaded the old version. It's corrected now. plz put a tutorial like counter , how put a new node, how conn...

Hi everyone, I've been to other sorts of things recently, but I decided to do what I've promised and post the demo project of my pathfinding class here. So here it is :wink: You can download it here: http://czestmyr.wz.cz/other/PFProject.zip . (188kB) I didn't include the project file in the archive...

Ever heard about parenting objects? Every scene node in the scene can be made a parent of an other node. Try putting following code before creation of the animator: camera->setParent(rydzyk); The camera target is relative to the translation of the camera, so i guess it should move with the camera.

And what about the other pointer - Meta? Have you not initialized it with zero yourself in this line:

scene::IMetaTriangleSelector *Meta = 0;

I'm not sure that I understand why you parent the nodes everytime you want to
rotate a part of the body. And why do you change position of the nodes, when you only want to rotate them?

And why do you calculate the angles through matrices? Wouldn't vectors be sufficient?

As the Subject of this thread says: I'd like to know how you post user events to the Irrlicht Device. I tried the method postEventFromUser(SEvent event) of the scene manager, but it doesn't work.

Good work man! I may have a need for your class. I will definitely take a look at it.

2 omaremad: I don't get it. What's the point in dividing the line into four parts and creating three flares instead of one??

2 etcaptor: Will post a simplified project soon, with the bot animator as well 2 Electron: Hey man! You were partially right! I read another article on the A* pathfinding recently and it really talked about the open and close lists. I found out that my algo does the work of the lists by discarding a...

How did you do the collision checking between two nodes, when you say you implemented it yourself?

When you create a SceneNode, you specify the parent scene node in the constructor as the second parameter.

And there should also be some setParent functions or something like that in The ISceneNode interface. Just take a look into the reference manual, It's useful.