I'm trying to import a mesh out of 3dsMax into UDK and running into corruption issues. I have a highly detailed mesh to begin with so I'm scaling it way down in 3dsMax using ProOptimizer to under the UDK vertices ceiling. What's weird and where I'm running into a problem is that UDK corrupts any mesh I import into it that has been ProOptimized more any less than 90%. Optimizing and reducing the polys on the original mesh in 3ds by 90% or more imports fine into UDK but any less than that and I get crazy looking corrupted meshes in UDK. While 90% or more works it's a bit too low poly for my tastes so I'd like to get this figured out.
Image of the meshes in UDK after being ProOptimized and exported out of 3dsMax as FBX. From left to right: 90% optimization looks fine, 89% has some corruption, 75% has a ton of corruption.
Thoughts on WTF is happening here? Everything looks great in 3ds.
At first glance the mesh is too dense ..
This is a 3D sculpture? Zbrush / Blender / Sculptris / Mudbox? If this is the case you need to do a retopology to optimize the mesh and have a clean base and slight if you have not done
Looks like you didn't set up smoothing groups, which means every vert of every tri is duplicated for each tri it is part of. To check this, give the entire mesh the same smoothing group and try to import.
In my experience it *is* a polycount problem, though it seems not to follow particular rules. I once had the very same problems, and the errors even variated for one and the same model when I imported it several times. That was a while ago though with an older UDK version. Static Mesh only btw. Apparently Skeletal Meshes can have more polys/vertices since some 2012 UDK release.
In any case - what do you want to achieve with the head? Because despite this particular error, 20k for just a head is rather intense and not really necessary for a character.
Originally Posted by ikifenix
That is weird, I imported a 120k tris = 60k polys mesh just for test and it is ok.
I just tested it too (with the same model that once gave me these errors) and despite the warning for collision it worked well too. I used the UDK februrary release this time. So by now I think it can be either a problem with the model (make sure to collapse the stack. It just worked for me not doing so, but safe is safe) or with the UDK version.