Include the following details while filing a bug report (edit as applicable):
Bug reproduction steps:
Some Assets when trying to download in FBX mode and missing certain files that make them usable in programs such as Unity.
As you can see below, the left Asset has its sub-meshes, but no master mesh file in the root directory, as seen for the working file on the right.
Let me know if there is any fix for this.
Hi Nathan,
Would I be able to take a look at the fbx files you downloaded? Since this is a public community forum can you send me the scans via message on Discourse or reach out via support@nianticspatial.com?
I have emailed the files.
Thanks, I shared them with our team earlier today. I’ll keep you posted.
Hi Nathan,
I have an update for this question. So this is expected behavior for FBX files. The FBX files are exported with the intent to be used in NSDK/ VPS projects so they can come exported as individual zip folders contained in one.
For external 3D software use, you will want to use the GLB export option instead.
I know you mentioned that this makes the FBX unusable in Unity. Is the Unity project using the NSDK and/or VPS?
I am using NSDK 4.1.0
As shown on my original posts, some of the FBX exports come with several individual zip folders, that also have a fbx, json, and jpeg outside of all the other zips. These zips work correctly.
The two flagged FBX exports just contain the zip folders, with no additional fbx, json, and jpeg. These do nothing when added into a Unity project, and thus are unusable.
Hi Nathan,
Thanks for your patience. I was able to reproduce the same issue. Looks like the zip folder has to be manually unzipped in Unity which then reveals the multiple zips and each of those zips are then unpacked by NSDK as a usable manifest + mesh pairs. Still not the expected behavior, the parent zip folder should be unpacking automatically into only one mesh and manifest so I’ve filed a bug report for this.
