Horde3D

Ive just discovered a bug with Horde3DUtils::pickNode. The value returned returned by this function when a node is slectioned is always a unity higher than it supposed to be.

For example, if I create a Node in wich the NodeHandle value is equal to 75, the value returned by the pickNode function will be 76 if I click on it.

Strange, we are using this function in the HordeEditor and and didn't notice any problems so far. Nevertheless I will check it again.

I couldn't find any problem, but I only did a quick test. Are you sure there is a bug?

Please be aware of the fact the pickNode function returns handles to meshes and not to models.

I'm using this to get the right nodeHandle. Maybe I could send you the source code? The comment are in french, but every classes and variable names are in english. It's my attemp to make a little map editor.

A sample with source would really help.

And no worries about the French, I used to speak it quite well (a plenty of years ago, when I was still in school )

Hi!

I did not knew the difference between model and mesh in horde, but I have looked more carefully at knight material and ive seen that a model can be composed by many mesh. So, its surely not a bug. My error is that I was trying to compare a model and a mesh.

Is there a way to get an NodeHandle from a mesh wich is in a model? Ive tried with Horde3D::getNodeChild but it did not work.

Getting the model to which a mesh belongs is easy. Just call getParent starting at that mesh in a while loop until you get a node of the type model.

Thanks, it work well now