[fixed]Problem with "closest node" order in getSce

[Pan]

I think I just stumbled over the same issue, and I'm not really sure whether the problem is now actually solved or not?

In my program, I sometimes have problems picking the nearest node to the camera, as can be seen in this picture.
The Mouse cursor shows the spot where I click, and the croshair-style marker shows which object actually has been picked by Irrlicht. As you can see, I try to pick the small cube both times, but when I'm also above the plane, Irrlicht picks the plane, despite it not being the nearest colliding node with a ray from the camera into the world.

So, this should be the same problem which was discussed here, right?

Now I'm not working with the current version of the Irrlicht engine (I'm on 1.4.2), but this statement somewhat confuses me:

Since this is a significant functional change, I've only put it on the trunk, not the 1.5 branch.

Does this mean that simply upgrading to the current Irrlicht version will not contain the changes that (may) solve the problem?
And where then can I grab the updated version, if it's not contained in the "real" current Irrlicht engine..?
And is the problem actually solved now? Above me, Yoran seems to have the same problems with flat nodes (like my plane node).

[hybrid]

The changes are only in the SVN/trunk version, which will become Irrlicht 1.6 in the future. So you have to wait until that version is released. This happens if the bugfix has too many side effects on other modules where we cannot guarantee that the engine would still work as the previous minor release. That's why this bug might still show up in 1.5.1 once it is released.

[Pan]

I see, thanks for the info.

Is there some sort of timetable, when upcoming versions are about to be released, or does it simply come out when the coders think it's ready for release?

[hybrid]

We have some loose time schedules, but these are often subject to change. 1.6 should be released within the next 3 month or so.