Bug in oFusion display of bounding box

The bounding box, as displayed by oFusion in Max, is actually wrong.
See following screen shot:


I don't know if this is just cosmetic, or actually a symptom of some deeper problem. I'm using the oFusion CE from 1/26/07, and 3ds Max 9 in DX graphics mode.

Thats because ofusion currently supports the 1.2 Dagon version of Ogre. To display correctly in Eihort 1.4 you have to run your meshes through the mesh updater utility first.

See the sticky thread at the top of the Ofusion forums, there's a thread called Sticky: If you have Bounding box and lighting problems...

The updater tool solves a different problem.

Note that this screen shot is from WITHIN 3DS MAX. What version of Ogre I'm using doesn't even come into it. This is oFusion showing the wrong bounding box for a model that I've built within Max, in the oFusion viewport in Max. No Ogre export involved.

Screenshot form jwatte are captured in 3DS Max. Is there any relations with Eihort? The problem are very easy to reproduce.

Create 3 cylinders along three axes.
Convert them to editable mesh.
Reset XForm them, collapse all.
Select one cylinders, in Editable Mesh modifier , attach other two cylinders.
Switch to oFusion viewport.

Actually there is a relation between what the 3dsmax viewport above vs Ogre version.

In Ofusion, there is a special viewport named 'Ofusion Viewport' which essentially is built using Ogre. This viewport is actually an Ogre window embedded within 3dsmax.

Yeah it is rendering using ogre within a Max viewport window, but in the current version of Ofusion it's still Dagon I think and the bounding box should be correct.

However, I tried the test situation a couple of posts above and your right, the 3 axes when attached do produce an incorrect bounding box .

Dagon can tolerate incorrect bounding box, but Eihort is a lot more stricter. That is why objects with incorrect bounding box display perfectly in Dagon, but not so in Eihort. I made to understood that this is to enhance performance, and it is pretty much reasonable.

Honestly, I think it is a bug within Ofusion which generate incorrect bounding box which is fed into Ofusion viewport.

Honestly, I think it is a bug within Ofusion which generate incorrect bounding box which is fed into Ofusion viewport.

That's my feeling as well, which is why I reported it.