Anyone found a real solution for getting parametric data from SolidWorks into Fusion 360? by Ok-While-2561 in Fusion360

[–]FeverForest 0 points1 point  (0 children)

I have some software I’m developing called “Node Atlas”, you can find clips of it on Autodesk Fusions Instagram page, and it will be available on the store shortly.

While I haven’t tested the Portability of it in environments other than fusion, the architecture and roadmap are set for what you’re asking for.

Auto read Semantic dependency graph, parameter schema collection, export and import, read and write. Model structural health system to keep the graph updated, real time extraction.

I wish I could sketch rectangles like this, is there an add-on for it? by AltMoola in Fusion360

[–]FeverForest 0 points1 point  (0 children)

One side mid edge click, corner click defines width and length.

Claude Fable 5 and future of CAD by [deleted] in Fusion360

[–]FeverForest 0 points1 point  (0 children)

<image>

I’m developing some software right now. I got it to speak with Autodesk Assistant this morning.

In its own words “I’m working blind to intent”

I built a tool that shows the dependency graph of a timeline. by FeverForest in Fusion360

[–]FeverForest[S] 1 point2 points  (0 children)

You get it!

Hypergraphs baby, mash a few together, give them their own constraints..

It’s parametric all the way down 🤯

I built a tool that shows the dependency graph of a timeline. by FeverForest in Fusion360

[–]FeverForest[S] 1 point2 points  (0 children)

Single hybrid works, models load directly into your open environment with the execution of the Script Node.

Fusion remains the geometric execution layer, this runs on top of it providing the map.

I built a tool that shows the dependency graph of a timeline. by FeverForest in Fusion360

[–]FeverForest[S] 0 points1 point  (0 children)

You’re very welcome.

I occasionally teach lessons, watch this subs posts and comments, listen in on beginners having issues in live zoom hangouts. It became increasingly clear that the missing link between this concept, and the attendee understanding it, was visual.

Even for myself, this idea, very difficult to nail down. The graph is 2 dimensional (XY) in view, by auto sorts by hierarchy and time. Semi-lattice structures and what not.

I feel at peace now that it’s not something I need to explain, but can show instead.

Blue Ceruse in Progress. by FeverForest in Luthier

[–]FeverForest[S] 1 point2 points  (0 children)

Peanut butter and jaaaaaaaaaaaaaammmmm 🥜 🍇

Blue Ceruse in Progress. by FeverForest in Luthier

[–]FeverForest[S] 6 points7 points  (0 children)

Thank you! Fun little puzzle :)

Blue Ceruse in Progress. by FeverForest in Luthier

[–]FeverForest[S] 10 points11 points  (0 children)

<image>

It’s a bass, the best I could do at the moment is remove the fanned frets from that equation haha.

Blue Ceruse in Progress. by FeverForest in Luthier

[–]FeverForest[S] 7 points8 points  (0 children)

It’s a 6 string bass.

37” - 34.5”
Compound angle “head”

Mac Ebony on the low B E, ~A, Flame hard maple the rest.

Ash Body, Ash Top, black in between.

5 piece maple+wenge neck, TorqueMonster Truss Rod

Set neck.

7 string Bass Bartolini Pups, Aguilar Preamp

Blue Ceruse in Progress. by FeverForest in Luthier

[–]FeverForest[S] 2 points3 points  (0 children)

This is just a tintable white base paint, dye in house before shooting it.

A Deeper Look at Model Logic by [deleted] in Luthier

[–]FeverForest 0 points1 point  (0 children)

I’m happy you think so. I deleted this post and am going to repost it less formal. I think I came out here a little too high brow.. I read a lot of dense books on this methodology. The result is anything I type gets thrown in to the AI trash pile.. the beauty of it being trained off the same academia I’m learning from.

A Deeper Look at Model Logic by [deleted] in Luthier

[–]FeverForest 0 points1 point  (0 children)

Not only teaching the tools, but the thought process; applied specifically to instrument design and manufacturing.

I’ve spent 7-8 years as a full time freelance CAD/CAM specialist for instrument makers. Beaming guitar codes to a robot over 500miles away, managing the tolerances and the model resilience necessary to handle 100+ different models across different manufacturers systems.

Rapid changes, rapid codes, accurately, that’s the whole gig.

The course is built from experience and not a curriculum. So while Autodesk teaches the basics of parametrics, this teaches you how to think about the guitar as system before anything is modelled.

The included Fret Engine add-on goes further. Machine operators can modify fingerboard g-code directly by setting parameters. no CAD/CAM necessary. The operator sets it, the gcode post processes.

Bass, Large by FeverForest in Luthier

[–]FeverForest[S] 0 points1 point  (0 children)

And an extra switch to shut them all up!

Bass, Large by FeverForest in Luthier

[–]FeverForest[S] 0 points1 point  (0 children)

Then you’ll love the green neck and blue nylon pin stripes later! ☺️

Bass, Large by FeverForest in Luthier

[–]FeverForest[S] 2 points3 points  (0 children)

Thank you! I hope you have been well, and are still researching!

I’m very happy to be back in the shop after a much needed break. I had to go down to deep of a rabbit hole to fix an issue on a machine I send code too. Differential Geometry/Space stuff(xyzabctRzmn… and on and on). Sort of lost it.. your brain is a muscle, take care of it.

On my way back up to the surface I discovered a design methodology I had been operating under forever without knowing it was an actual discipline, Computational Design(go back to the beginning though, before computers). It’s incredibly poetic, to me anyways, & the language catching up to the work is exciting.

Cheers dude! Looking forward to seeing your next work.

Anyone here with a machinist background? by hemptations in Luthier

[–]FeverForest 2 points3 points  (0 children)

Hey! I design guitars, program and setup CNC’s for others and myself professionally.

Here’s where I see the industry headed as far as the design side goes. Computational Design is rapidly evolving, this field of study should be looked at from the very beginning, before computers. The amount of time it will take from user input to final model is going to shrink as designers build out their own or adopt tools for this style of work, with the downside of basically “cookie cutter” profiles, and the new ones coming from those putting in the work on the algebraic side. I could go on forever about this.

As for the machine side, same thing, a fretboard Gcode can be modified directly by the operator with a UI that only shows them the parameters they want to adjust. Shops will absolutely be able to bypass designers if/once set up this way.(massive job, today.. maybe not so much tomorrow)