Skip to content
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

No warning when mergegroup objects have multiple materials #80

Open
StjerneIdioten opened this issue Nov 8, 2020 · 3 comments
Open
Labels
bug Something isn't working

Comments

@StjerneIdioten
Copy link
Owner

Describe the bug
The exporter does not show a warning when an object exported as part of a mergegroup, has multiple materials. This leads to having multiple subsets on merge group shapes objects, and that makes GE crash instantly.

@StjerneIdioten StjerneIdioten added the bug Something isn't working label Nov 8, 2020
@Kieruss
Copy link

Kieruss commented Sep 9, 2022

I found that if you try to export two meshes as a merge group, and they have different materials, you end up with one mesh (with its own material, but no child mesh) and one empty that's just an empty. If they're set to the same material, it works fine.

However, the Giants exporter will happily export a merged mesh where the individual meshes have separate materials. Both materials get assigned to the actual-mesh, and it works fine.

@ssnd292
Copy link
Contributor

ssnd292 commented Sep 9, 2022

While the Giants Exporter will export this, this method is not recommended. Even Giants themselves did not allow a mesh with two materials at release of FS22.

@StjerneIdioten
Copy link
Owner Author

I guess I could make it add two materials to the parent object and then only "paint" the vertices that the material came from before merge, but as Redphoenix mentions it's not exactly recommended. Without bothering to look it up too much atm I seem to recall that it would increase drawcalls or something since you have multiple materials? In any case if it didn't hurt performance at all then we wouldn't need the vehicleshader and the UV trickery 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants