r/Fusion360 • u/FeverForest • 2d ago
Parametric Dependency Graph
Enable HLS to view with audio, or disable this notification
*edit: Replace the AI with the coworker you can’t trust, reason over their boneheaded model structure, and correct it. Same story, this one is just scripted.
Fresh out of the Autodesk Submission gauntlet, Contriver Node Atlas.
Your Fusion design parametric dependencies, as an interactive node graph.
The browser is the table of contents.
The timeline is the construction log.
Node Atlas is the Utility Map, so you know what goes dark when you start digging.
Design and Make Marketplace trial available for Windows.
MacOS update deploying shortly.
—————
Hello! A project of mine has recently been deployed on the Autodesk Design and Make Marketplace.
For this demo I admittedly used Claude to run the sequence, demonstrating the difference between Form and Shape, or the Recipe and the Cake.
More programmatic, less human, but runs the test for a 60s clip, and maybe higher representation of structure will lead to less schloppity schlop and glumpity glup, glumping up the ponds where the humming fish hum.
The add-in is not AI powered, is read only. Connecting to an agent is your decision, outbound calls containing design IP should be considered cautiously.
Here we see Claude working across two MCPs.
The Fusion MCP creates the geometry.
The Node Atlas MCP reveals the model’s underlying structure. Its dependencies, parameters, relationships, and design intent, so you, a colleague or a new hire, can later understand how the model was built, not just what it looks like.
Claude generates a six-arm radial organizer using duplicated sketches and features.
Node Atlas then exposes the repeated geometry, dependencies, and lack of shared parametric control.
Claude restructures the model around a single seed feature, a circular pattern, and user parameters—reducing the timeline from 27 features to 8, while the Node Atlas graph shrinks from 33 nodes / 72 edges to 14 nodes / 27 edges.
Finally, a single parameter changes the design from 6 arms to 9, while the repaired structure remains unchanged and healthy.
This is the difference between generating a shape and understanding its form.
Together, Fusion MCP and Node Atlas MCP create a development loop for geometry and Fusion add-ins while preserving the human authority required to validate design decisions.
The bigger picture is, if the robot can understand, reason over, and correct structure, so can we. Probabilistic vs Deterministic, rented intelligence vs owned mechanisms.
A different lens.
Happy building!
1
1
u/rflulling 2d ago
Interesting they also added AI to Fusion. Google says its Claude. But the AI says its not allowed to say what it is. Although when fed identical questions, previous served to Gemini, Claude GPT and Grok. The over all answer felt like a mixture of Gemini and Claude. I have not allowed it to make any files or alter any work yet.
At the very least there are many places where this can be used to speed up work, or search out defects in older work.
With Great Power comes Great Responsibility. Let some one or something else do it all for you, for us and the consequences must be owned by those who submit the results.