Datasmith 4.23E0 Texture Invert Reads Wrong

Hi All, I have a curious problem that hasn’t popped up until using 4.23.0 (Public release not preview) and its latest datasmith exporter 4.23 E0 for 3DS Max 2020. Before this I was using 4.22 and datasmith exporter 4.23 E2

Problem - For some reason when using the latest datasmith exporter (4.23E0) in 3DS Max 2020 and then importing using the datasmith tools for Unreal 4.23.0 if there is a map with an invert on it inside of Max it is no longer being read properly. I tried to look over every setting in regards to the texture file that is created during the import process and its definitely different than using 4.22 Unreal and 4.23 and their respective datasmith importer/exporters.

The first set of Images below shows the material in Green being correct in 4.22

The next set of images below show the material changed and now showing up red in 4.23

I’ve done everything the same way for both instances but and no other materials have been affected in my scene so far but there is one difference in this material and that is in the map settings there is an invert enabled in the map and I believe that is the culprit

Hello,

We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

https://epicsupport.force.com/unrealengine/s/

Thanks

ah perfect, I was trying to find this thank you Jeff!

ok I think I figured it out. For some reason the new exporter/importer is reading this one map as a Normal map instead of just a regular map but only seems to be in this scene, if I separate it out and import it into a new level its fine.