Michael,
Blender will not accept a FBX file directly from moi. It complains it is not a high enough version. It demands 2016 (the ini file say 2017 in Moi). I normally out put my files to FBX the run them through the Autodesk FBX convertor (2013) to update them so I can to get them into Blender. Normally there is no issue as Cycle has no trouble with them and Octane has no trouble with them but I have been playing with radeon and they are showing up mangled. When I run the fbx conversion through 3DSMAX 2020 (2019) they work fine in blender so it clearly is the FBX version that is having the trouble. I was wondering if somehow I don't understand what is happening in moi for a correct export version or if there was away to update the FBX exporter so I don't have to go through 3DSMAX or? any insight would be appreciated.
thanks,
Val

Hi Val, MoI v4 can export to a 2016 FBX version, there is some info on how to set it here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8683.9

MoI does not recognize a value of 2017 in there, so if you have that it will default to the same one as MoI v3 which is 2010.

If you put in 2016 does that then work ok? I guess the problem is that there was a big change in FBX starting with version 7.4/2016 to make it 64-bit and that broke compatibility.

- Michael

I just did a quick test and over here a setting moi.ini of:

[FBX Export]
WriteVertexColors=n
FBX Version=2016

comes in ok to Blender v2.80

- Michael

Ha, I must have changed the INI file to 2017 at some point when there was the error initially and then gave up. I punched in 2016 and now can get the fbx file in directly but it still has the errors as the 2013 convertor that doesn't happen in 2019.

Hi Val, from what I understood FBX 2016 or higher won't be readable by programs using an older version of the FBX toolkit like the 2013 converter.

Can you post a sample like just a box in FBX 2019 format so I can take a look at it?

Thanks,
- Michael

this is the same part just different imports one from 3dsmax one directly from moi. It only happens with radeon so.... not a huge deal or anything just odd.

Hi Val, maybe the difference could be if you're exporting n-gons, maybe the conversion from n-gons to triangles is happening differently between those versions.

If you export to "quads & triangles" out of MoI instead of n-gons do you then get consistent behavior?

- Michael

this is the part. like i said all other rendering engines are fine with it only Radeon in Blender. Radeon in 3dsmax is fine with it as well.

tried with triangles, tried with quads and triangles. same problem

Just to throw in a more info. This is in 3DSMAX 2020 also radeon engine one is a SAT file with a mesh modifier on top as the radeon engine freaks out about CAD files and one FBX file directly out of MOI both look good.

Actually I just redid the quads and tri export with the 2016 export. looks like it works fine. I'm a little sad about the N-gons as it's a nice easy way to UVmap. Anyway thanks for your help.

Hi Val, so another thing is that there is more than one way for vertex normals to be set up in FBX files, there are options for things like whether each polygon has a list of its own vertex normals or whether the polygon has an index into a separate list of normals.

Maybe the 2019 file you're writing out has them set up differently than the one that MoI writes and maybe there's a Radeon bug when processing MoI's style but not the 2019 file's style.

Old versions of FBX did not support using the indexed mode for setting up vertex normals, so MoI doesn't write them using indexed mode, it writes them using the "direct" mode.

- Michael

Hi Val,

re:
> Actually I just redid the quads and tri export with the 2016 export. looks like it works fine. I'm a little sad about
> the N-gons as it's a nice easy way to UVmap. Anyway thanks for your help.

So that probably means that the conversion from n-gons to triangles is happening at a different place something like one is handled by the FBX toolkit code and the other one is making n-gons go all the way through to Radeon but it has trouble processing them.

- Michael

Radeon upgraded their plugin for 2.8 so I imagine there are a few bugs. It's all to be expected. I'll meander over there and see what they say. thanks again.