Closed CuriousMike56 closed 2 months ago
Thank you for the test mods, I feel way more confident than if I tried to reproduce all by myself.
The offending commit is 74ed1083cb9e53e38096ec96b6a7b1f0b237ce01.
I accidentally pushed the fix directly without making a PR. But it's pretty straightforward and only tackles the one thing, so I'm confident it doesn't break anything.
This issue ticket provides additional details to the
Texture with the same name interferes between mods (even if they are in separate ZIPs)
problem reported in #3122.To assist with testing, I've created two test mods: MaterialConflictTestRed.zip MaterialConflictTestBlue.zip
They are simple cubes, with the center being submeshed (texcoords), left a prop, and right a flexbody. Also features a custom N flare material with the same color. The submeshed cube material name is
CM_TestCubeSubmesh
, defined in a.material
file. The flare material (CM_TestCubeFlare
) is also defined in this file. Prop and flexbody cube material name isCM_TestCube
, defined in themanagedmaterials
section. Both versions share the same material and texture names.In 2022.12, both versions can be spawned without conflict:![screenshot_2024-04-05_18-48-36_1](https://github.com/RigsOfRods/rigs-of-rods/assets/46073351/ff6aa4db-33ad-4d95-9a25-55efc85ff18c)
Now with the introduction of the tuning menu, spawning either version will conflict with the other:
Submesh, prop, and flexbody cube textures all conflict. Only the flare uses the correct texture.