3DS Max Fbx export issues

Gustavo_Elliott

I have been attempting to export my model as an fbx... but when importing back to 3DS or Marmoset I get this flickering mess on all parts of my model, this part is just for example. Any help is greatly appreciated. The geometry is clean and there are no overlapping faces or anything that should be causing this.

Gustavo_Elliott

Update: this is actually something to do with 3ds max's perspective view port and is apparently not the reason I am getting terrible bakes in marmoset

Gustavo_Elliott

SOLUTION: Turning off view port clipping in 3ds max effectively stopped the flickering in perspective mode.  The reason my Marmoset bakes were bad was because both the low poly and the high poly shared the same material and I remember reading something long ago stating that sometimes marmoset will bake the high-poly's Uv's onto the low polys normal map---- it is fixed by assuring that you have a different material assigned for both the high poly and low.

monster

If your model is z-fighting like that in Max and there is no duplicate geometry, check the size of your model. Only really large or very small models have that issue. And if the size is okay, then update your video card drivers.

Gustavo_Elliott

Thanks for the help @monster ... I will try that too! Its weird because it's only in the perspective viewport, no flickering occurs when in orthographic mode.

Mark Dygert

I get that sometimes with imported meshes. It's a weird bug and it can be hard to reproduce and sometimes hard to fix.

Usually if I apply edit poly or edit normals and collapse the stack it fixes it. Sometimes applying vertex color modifier will fix it too. Resetting xForm can sometimes fix it too.

Or in some extreme cases I create a box, snap it to my mesh location, apply edit poly, attach my imported mesh and collapse that. 

Gustavo_Elliott

It was a crazy headache that's for sure, tis fixed now and I am back to normal in both pers. and ortho. views. Thanks for the helpful information for if myself or someone else happens to have this happen to them in the future. In this case, It was fixed by changing the size of the model just like @monster said, it was too large apparently, so yeah its fixed. Thanks again for the response guys!