Welcome to WSL!

New to the forum? Please read this and this.

Fusion v17.2.1 Breaks PathMap Support in FBXMesh3D nodes

Moderator: Chad

User avatar
AndrewHazelden
Fusionator
Posts: 1768
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 11
Location: West Dover, Nova Scotia, Canada
Been thanked: 39 times
Contact:

Fusion v17.2.1 Breaks PathMap Support in FBXMesh3D nodes

#1

Post by AndrewHazelden »

Fusion version:
Fusion Studio v17.2.1 Build 14


OS and version:
macOS 10.15.7 Catalina


Additional relevant system info:



Description of the bug:
Fusion v17.2.1 appears to have changed how FBXMesh3D nodes expand PathMaps.

Summary: PathMaps and FBXMesh3D nodes are nackered.

If an asset like an OBJ mesh is stored in a folder that can be expanded into several different PathMaps there is a read conflict and the model fails to be imported into Fusion.

In the simplest form, this issue removes the ability for Fusion to load in FBXMesh3D models from a Comp:/ relative PathMap folder location like:

Comp:/Cube.obj

This issue also impacts the ability for Reactor to deliver 3D compositing sample comps that are able to load assets from inside the "Reactor:/Deploy/Macros/" relative PathMap folder structure using the "Macros:/" PathMap. This causes issues with KickAss ShaderZ, KartaVR's sample comps/meshes, and any Reactor "Comps" example that uses an external mesh stored on disk that is read with a relative PathMap.

Severity (Trivial, Minor, Major, Critical)
Major


Steps to reproduce:

Example 1:

1. Have an .obj model located in the same folder as a Fusion .comp file.

2. Read in the .obj mesh using a FBXMesh3D node using a relative "Comp:/" PathMap.

3. Save this Comp. Close it. Then re-open the Comp.

4. When you display the FBXMesh3D node in the Fusion viewer window, it will fail to load the OBJ mesh with the following error in the Console:

Code: Select all

FBX Error: "The file
 Comp:/Cube.obj
 could not be found!" while importing file
Comp:/Cube.obj
FBXMesh3D1 failed at time 0

Example 2:

An OBJ is able to be successfully read from an absolute filepath like:

/Library/Application Support/Blackmagic Design/Fusion/Reactor/Deploy/Macros/KickAss ShaderZ/Assets/kas_ShaderBall.obj

It can also be read successfully from the Reactor based PathMap:
Reactor:/Deploy/Macros/KickAss ShaderZ/Assets/kas_ShaderBall.obj

But the Fusion native PathMap version fails to work:
Macros:/KickAss ShaderZ/Assets/kas_ShaderBall.obj

Additionally, if the Fusion .comp file is saved inside the same Pathmap resolvable folder location, using the "Comp:/" PathMap also fails to work.

Comp:/kas_ShaderBall.obj

1. Turn on the Fusion Preferences > PathMap > [x] Enable reverse mapping of non-user paths checkbox.

2. Use either the "File > Import > FBX Scene..." menu item, or the "Select Tools > FBXMesh3D" dialog to load in a model from inside a multi-resolvable PathMap folder. You could use a Reactor provided "KickAssShaderZ" model to try this issue out like the "kas_ShaderBall.obj" asset.

3. Click on the FBXMesh3D node you just imported in the Nodes view. Select the "Browse" button to show the file dialog. Select the "kas_ShaderBall.obj" asset and then click "Open" to close the dialog.

The PathMap will be re-written by the Fusion preference's [x] Enable reverse mapping of non-user paths checkbox option to the shortened form of:

Macros:/KickAss ShaderZ/Assets/kas_ShaderBall.obj

4. Save this Comp. Close it. Then re-open the Comp.

5. When you display the FBXMesh3D node in the Fusion viewer window, it will fail to load the OBJ mesh with the following error in the Console:

Code: Select all

FBX Error: "The file
 Macros:/KickAss ShaderZ/Assets/kas_ShaderBall.obj
 could not be found!" while importing file
Macros:/KickAss ShaderZ/Assets/kas_ShaderBall.obj
FBXMesh3D1 failed at time 0

Please, if possible, provide a Fusion setup to help demonstrate the behaviour, either as an attachment or between [code] tags:
Cube.zip
You do not have the required permissions to view the files attached to this post.

User avatar
UserNoah
Fusioneer
Posts: 194
Joined: Mon Mar 09, 2020 11:43 am
Been thanked: 6 times
Contact:

Re: Fusion v17.2.1 Breaks PathMap Support in FBXMesh3D nodes

#2

Post by UserNoah »

Can confirm the bug on Windows 10.

User avatar
AndrewHazelden
Fusionator
Posts: 1768
Joined: Fri Apr 03, 2015 3:20 pm
Answers: 11
Location: West Dover, Nova Scotia, Canada
Been thanked: 39 times
Contact:

Re: Fusion v17.2.1 Breaks PathMap Support in FBXMesh3D nodes

#3

Post by AndrewHazelden »

PathMap support in FBXMesh3D nodes is still broken on Fusion v17.2.2 Build 4 on Linux.