Using SDK to write FBX valid for Navisworks Manage

[Anonymous]

Thanks in advance for anyone replying to this advanced problem!

Related to this post: https://forums.autodesk.com/t5/infraworks-forum/export-of-fbx-ok-in-navisworks-but-looks-wrong-in-ot...

I struggle with creating FBX files through the FBX SDK that can be opened in Navisworks Manage (2018,2019,2020)

I have tried creating 

ASCII / binary 7.7

ASCII / binary 6.6

ASCII / binary 6.1

with textures included and without

Have anyone successfuly created an FBX-file with working texture? Similar to what you can see in the image below?

If yes, which "parameters" are needed to send to the SDK to achieve this? 

Since the GEOMETRY/SURFACE looks ok, I assume it has something to do with the texture-definitions. Unfortunately the FBX-files are binary so they can not be compared "visually" and the "Autodesk FBX Converter 2013.3" just gives me a warning when I try to open the "FBX Explorer" making it unusable.  "Ony three FBX Explorer Maximum". Are there any other tools to dig out details regarding an FBX-file, header, metadata etc? 

[Anonymous]

I have now spent countless hours trying to solve this. Trying different things. The best thing I got was the one below. Still no structure or clue why its behaving like this.

[kevinvandecar]

Hi, so... It's a little unclear where the FBX comes from to start? I read the other thread, too, but not sure there either. One option is that FBX can be in ASCII format. This is a handy way to look at the internal aspects of the FBX file. If the exporting application does NOT support ASCII directly (most Autodesk apps do), then you can still make an ASCII version by using the FBX SDK. Simply import it, and then export it using the ASCII option. That may help to see where the issues are.

Also, it looks like you are reviewing the FBX in an older tool? The old FBX converter tools is no longer supported. The latest FBX review (which is also not being improved lately) is here: https://apps.autodesk.com/3DSMAX/en/Detail/Index?id=6979630331069053932&appLang=en&os=Win64
Microsoft also supports FBX in it's 3D Viewer (part of certain versions of Windows 10 now).

Based on the screen shots here, I can agree it looks like something is amiss with the textures. You might also try with a smaller different dataset to narrow down the problem?

hope it helps,

kevin

[Anonymous]

Hi, so... It's a little unclear where the FBX comes from to start? I read the other thread, too, but not sure there either. One option is that FBX can be in ASCII format. This is a handy way to look at the internal aspects of the FBX file. If the exporting application does NOT support ASCII directly (most Autodesk apps do), then you can still make an ASCII version by using the FBX SDK. Simply import it, and then export it using the ASCII option. That may help to see where the issues are.

Also, it looks like you are reviewing the FBX in an older tool? The old FBX converter tools is no longer supported. The latest FBX review (which is also not being improved lately) is here: https://apps.autodesk.com/3DSMAX/en/Detail/Index?id=6979630331069053932&appLang=en&os=Win64
Microsoft also supports FBX in it's 3D Viewer (part of certain versions of Windows 10 now).

Thank you very much for replying @kevinvandecar !

The file is created with FME Desktop from Safe Software (www.safe.com). The goal is to automate the process of clipping terrain when the data changes often.

I have also tried with a different tilesize - texture size - resolution. I also tried to round off the corner coordinates of the geometry and the coordinates of the textures. I also tried to make the textures 50 pixels larger than the geometry itself to see if the texture was too small.

It can make an ASCII version, and I also compare the version with the ASCII version created by using the Infraworks export but I can not seem to see any difference.

I also tried to embed texures and use binary - to be sure everything needed is included within the file.. The result is given below in both Navisworks and FBX Review - same file. 

File in Navisworks Manage

FBX Review

[Anonymous]

Not sure how I can help any further to get this issue solved.