Irrlicht Engine

As a current example - if someone could update the outdated b3d Blender exporters
Actually, that's already done: https://github.com/GreenXenith/io_scene_b3d/tree/master
This revamped exporter works with any Blender version since 2.80
I was writing it myself and found out while looking for ...

CuteAlien wrote: Tue Mar 18, 2025 11:17 am I'd recommend mostly to just use Irrlicht.
...

Use either the sourceforge bug reporting tool
...

You can improve a bug report in several ways:
...

If you want to write patches:
...

Thank you

Instructions for bug reporting and how to help Irrlicht are quite old, could anyone refresh them?
I'm interested in helping the Irrlicht project...

Not sure if it's still relevant, but next step is IME (input method) support...

seems the link from Irrlicht's home is broken... or someone put it away?
I can't see the irrlicht wiki anymore...

Thank you CuteAlien

Workarounds: do we need to adopt all three or just implement one of them?

Next Irrlicht version release date?

If you have really fixed that, could you please share the patch or apply it in the trunk ASAP? I'm going to need it soon... thanks

Irrlicht does just 3D, it does not mess with networking (or physics). To implement a game server, either use a proper framework/library along with Irrlicht or write your own

Of course. But the ray (the line3df) is calculated by X/Xmax Y/Ymax ratios, so it SHOULD remain the same no matter the frustum length. If setting a farValue too big hinders the ray calculation, there is something wrong...

No, it does not. The ray is calculated from mouse position and far frustum corners. The farValue is not taken into account, at least not directly. It's used to calculate the transform matrix...

This is interesting. The camera's FarValue shouldn't matter at all for ray calculations... hmmm... maybe the FOV comes in the way?

lumlum wrote:the farValue of my camera was too big

How big was "too big"? How much did you set it? (default = 2000)

I just modified the example win32window, stopping the cam, adding a triangle selector to the cube and trying to select & rotate the cube itself by clicking on it: nothing. Can't select the cube...

Hmm... if it's not a problem of tiny triangles, why alexazazel had troubles with selection until he changed function?
Doesn't this means there is a bug lurking somewhere in the get... function?

Hmm... mesh triangles too small to be collided? Good to know however