Shame on Maxon that its users had to be the one to find a fix; only took .. what, like 3 years? After goodness knows how many folks filed bug reports about this? I feel like a fool that I pay so much money for a software company that behaves in this way.
Thank you, so much, for the very detailed breakdown! Very informative.
This is for client product work, so unfortunately, sharing it with someone else won't be possible.
I'll consider the trial option, but obviously, that isn't necessarily the best practice for continued work, moving forward.
Hello guys, did you ever make any progress with this? I've just opened a similar question on this here: https://cineversity.forums.maxon.net/topic/2379/glb-gltf-export-issues-named-animation-tracks
But I can't use FBX without breaking materials... Glad of any advice.
It appears you have a lot of "Non Manifold" topology in the model causing this. This means that some edges belong to more than 2 polygons and this is not considered "good" topology.
Select all your polygons, go to Mesh menu - Clone - Resolve Non Manifold and everything should look good...
When working with Redshift Proxies, it is helpful to follow these guidelines:
You cannot retrieve the original 3d app's (Maya, C4D, Houdini, etc) mesh from a Redshift Proxy file, so it is generally advisable to keep the original source data that was used to export the Redshift Proxy.
image.png
So unless you have the original project file you cannot retrieve the data from the proxy file.
Will do, thanks. I pivoted to a different solution for the job. But I'd still like to know, so I'll post an example file as soon as I can free up time.
