Somian
0
Since this bug only got 2 votes to be fixed, hinting at a low user base, it has been decided not to directly support the cheetah 3D materials.
The material mapping has been fixed, though. This means it's now possible again to put a .jas into Unity and it'll assign the correct materials IDs and names to the materials. The corresponding materials may then be assigned. I think this used to be broken.
According to our QA, this has been fixed in Unity 2020.3.17f1+, 2021.2.0b9+ and 2022.1.0a6+. I just verified it with 2022.2.3f1.
While in theory, it should be possible to support the materials, this will need some additional work. I think the only real use-case is when using the PBR materials and it looks like this hasn't carried over properly in the past (e.g. "metallic" wouldn't map to "metallic" in Unity). Usually, in my workflow I only import the models with the material IDs and then replace the materials so I'm happy that the material mapping works again.
The material mapping has been fixed, though. This means it's now possible again to put a .jas into Unity and it'll assign the correct materials IDs and names to the materials. The corresponding materials may then be assigned. I think this used to be broken.
According to our QA, this has been fixed in Unity 2020.3.17f1+, 2021.2.0b9+ and 2022.1.0a6+. I just verified it with 2022.2.3f1.
While in theory, it should be possible to support the materials, this will need some additional work. I think the only real use-case is when using the PBR materials and it looks like this hasn't carried over properly in the past (e.g. "metallic" wouldn't map to "metallic" in Unity). Usually, in my workflow I only import the models with the material IDs and then replace the materials so I'm happy that the material mapping works again.
Attachments
Last edited: