Helios(2) revisited

[Patrice Terrier]

I have reworked all the meshes for compatibility with OR version #2.52, and the latest mtxRotate function.

I hope to have fixed everything.   

[Michael Lobko-Lobanovsky]

What do you think was causing improper rotating mesh behavior in the preceding version of the model?

I think the blue jets could be made glowing in the dark. Currently, there isn't a single spot in the entire model that would glow when the scene lighting is dimmed.

Otherwise, the model looks flawless.

[Patrice Terrier]

There was a material missing, and i was forced to use a Y offset of 5.663 for all static meshes, to have a perfect rotation with the rotating group.
And i changed the loading order of the meshes, all these changes seem to have cured the problem.

Stay tune, i shall post soon another model with rotating meshes for test purpose…

[Michael Lobko-Lobanovsky]

There was a material missing ...

This shouldn't affect anything because in this case, ObjReader would simply use its default material to depict the mesh.

... i was forced to use a Y offset of 5.663 for all static meshes ...

Yes, you have to ensure your model is perfect if you want to rotate some of its meshes synchronously.

And i changed the loading order of the meshes ...

... which makes me think there are still some parameters somewhere that don't get re-initialized from material to material when reading the MAT file. I'm wondering if the existing "material cache" is compatible with the new functionalities we're adding to our meshes...

[Patrice Terrier]

Yes, you have to ensure your model is perfect if you want to rotate some of its meshes synchronously.

i didn't change anything into the rotating group, but i had to change slightly the Y offset of the other meshes to make sure that they match exactly the center of the Y rotation axis.

The missing material was causing the rotation of the matching mesh, that was indeed a static one that shouldn't rotate.

To check everything, i started from the rotation group alone, then adding one by one all other meshes, to detect what could be the problem, boring job to say the least… 

[Michael Lobko-Lobanovsky]

The missing material was causing the rotation of the matching mesh, that was indeed a static one that shouldn't rotate. ... boring job to say the least… 

Thanks for walking that extra mile, Patrice! Your description will probably help isolate the bug.