You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ogre mesh loader only loads the default material, which is the one with the same file name as the mesh itself. Even if the ogre exporter exports multiple materials correctly, jme3 will fail to load them.
Whilst debugging, I found out where I think the bug is : DesktopAssetManager.java public Spatial loadModel(String name){ return loadModel(new ModelKey(name)); }
Instead, this should work :
However, doing this creates a circular dependency in the gradle configuration, as it tries in the core project to use classes from the plugins project.
Anyway, the problem is that the core loader does not take into account custom ModelKeys from the plugins.
Here's a model exported from Blender using the ogre exporter. If you look into the mesh.xml file, you can see the materials are properly set. crystaler.zip
Here are the log warnings :
Even though we convert the ogre mesh into an .j3o file, we need the materials to be properly loaded...
The text was updated successfully, but these errors were encountered:
Strangely, I didn't see any notifications for this thread.
@thoced Nope, because of this : "However, doing this creates a circular dependency in the gradle configuration, as it tries in the core project to use classes from the plugins project." If it was a simple, then of course I would have done it. However, it is much more complicated. It's actually a conception / architecture problem.
The ogre mesh loader only loads the default material, which is the one with the same file name as the mesh itself. Even if the ogre exporter exports multiple materials correctly, jme3 will fail to load them.
Whilst debugging, I found out where I think the bug is :
DesktopAssetManager.java
public Spatial loadModel(String name){ return loadModel(new ModelKey(name)); }
Instead, this should work :
However, doing this creates a circular dependency in the gradle configuration, as it tries in the core project to use classes from the plugins project.
Anyway, the problem is that the core loader does not take into account custom ModelKeys from the plugins.
Here's a model exported from Blender using the ogre exporter. If you look into the mesh.xml file, you can see the materials are properly set.
crystaler.zip
Here are the log warnings :
Even though we convert the ogre mesh into an .j3o file, we need the materials to be properly loaded...
The text was updated successfully, but these errors were encountered: