You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Still 100% a noob with this stuff so this may be user error? Myself and a few other users that have managed to get UE5 imports to work flawlessly in the past, haven't been able to get the latest version to work. Objects are being imported with no textures, some objects don't get imported at all, and after the import finishes we're met with a new error message that we hadn't seen prior to this version of Charm.
Error: FBX Scene Loading: Found material name clash. name clash can be wrongly reassign at reimport . material (name here) was renamed (new name here)
This error occurs on every import we've tried.
The text was updated successfully, but these errors were encountered:
Issue is ongoing in Charm 2.0. Something in the Python script isn't working properly. Textures are present in the texture folder but aren't being applied during import.
bump.
really wanted to get the Black Garden imported to Unreal, then ported to Unity, but im not seeing any of the textures map over on Unreal, to the materials at all, and it looks like id have to do that manually. (Which im not familiar with Unreal Engine at all, so thats a HUGE issue to me) :<
Really hope it gets fixed soon, cause i REALLY wanna see how crazy some of these maps are in VR. not optimized at all with over 1m tris, but eh whatever
Still 100% a noob with this stuff so this may be user error? Myself and a few other users that have managed to get UE5 imports to work flawlessly in the past, haven't been able to get the latest version to work. Objects are being imported with no textures, some objects don't get imported at all, and after the import finishes we're met with a new error message that we hadn't seen prior to this version of Charm.
Error: FBX Scene Loading: Found material name clash. name clash can be wrongly reassign at reimport . material (name here) was renamed (new name here)
This error occurs on every import we've tried.
The text was updated successfully, but these errors were encountered: