-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing material issue #156
Comments
Can you post the .mesh and the .material? Also: what Blender version are you using? Thanks! |
2.93 |
That material is inheriting from other material, that feature is not supported by the importers' material parser. I understand this is annoying, but it is not implemented right now. You can see it from all the warnings in the Log: A possible workaround is for you to do the inheritance process by hand. |
I'm not familiar with an inheritance material in blender. Would it be assigned in code or in blender. because at the moment when it imports, i have to assign the .png to the object with the material editor tab for every part. Not the worst process because some objects import with textures assigned and some don't. It is weird. |
I just tried importing another .mesh and out of around 30 objects, 4 got assigned textures. Some, all the textures are assigned. Some none are. It is like a random draw. |
The inheritance is in the OGRE materials, not Blender. Example:
The |
Oh I get it now. Thanks! Is that feature coming in the future? |
Yesterday I was thinking about it. But it would be great if you could share all the materials that you are using, so I get a better picture because the Tires.zip only has 1 material that is derived. Also the implementation would probably be suited for this case only because it would be extremely difficult to handle all the permutations of OGRE materials out there. |
This is the main thing, a lot of files from here do the same thing. But a lot also import materials just fine. https://sim-monsters.com/files/file/4278-sm-v5/ If it is not a hard addition, I would greatly appreciate it! |
Probably the ones that are base materials are importing OK |
Ahh. Fingers crossed it could get an update to read all of them. I thank you for the plug-in tho, it is a life saver.On Apr 16, 2023, at 3:23 PM, Guillermo Ojea Quintana ***@***.***> wrote:
Probably the ones that are base materials are importing OK
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I also had issues importing Materials, however, if I just want to edit the model, I don't actually need the materials to import correctly. My problem was that after importing a model, it only had the materials it could import and all information about the other materials was apparently lost. Importing with separated sub meshes kind of worked, but I'd still have to create the materials so that they would be referenced in the exported model (which then could use its original materials as before). Therefore, I edited the import script slightly to create the materials if they could not be found (ogre_import.py from line 1270):
Maybe there could be an option in the import settings for this. |
@FeuerTiger86 can you create a pull-request regarding this change? Thanks! |
So does this fix the issue? |
If you only want to edit the mesh itself but none of the materials that could not be imported, yes. It will create new default (white) materials with the correct names, so that the information about which part of the mesh uses which material is preserved. Then don't export materials so that the edited mesh uses the existing materials. |
@Mjamfan22 as @FeuerTiger86 said, this does not fix the issue. I tried to implement support for inheritance but found it too difficult for me, sorry. |
Trying to import a .mesh and materials don't import. The materials import with this on every .mesh i have tried to import except for this mod. Im not sure why it excludes this mod.
The text was updated successfully, but these errors were encountered: