Guitar Neck Model - I'm close

I’ve attached a copy of your file - some surfaces are hidden.

I basically extended 3 lines from the neck, deleted a bunch of duplicate curves, used SetPt to align some stuff (“J” and shaft curve), added a cross line for reference, dragged 2 curves to meet those intersections, and set the “J” tangent to the neckshaft line. the mounting plate area would need to be widened from the layout lines I extended. This ensures that the edges will be square - typical in this case. There were loose end curves not meeting points of other curves.

neck carve - fix heel area forum.3dm (499.9 KB)

Yeh after i posted last night i found and fixed those loose point and tangency issues

Honestly my only remaining issue is that slight peak where the halves join at the headstock and heel - even after a matchsrf. maybe i don’t have the parameters dialed in right…idk

I’m curious what ppl mean by CAM. To me the CAM doesn’t matter relative to any shape, as CAM can mean more than just 2.5D toolpaths.

Is “manufacturing” better? I do models, 2D, 3D, as vectors and surfaces that will be machined, not presented as art on a flip chart presented to a group.

So my models might look like this:

I use Vcarve Pro and it will project 2D vectors onto a surface. This is a 2 sided part, and I like to simplify it into separate models. The profile cut and tuner holes can be simple 2D profile tool paths at the end. I think of making the part the same as how I made parts before I had CAD and CNC.

My Rhino file is a means to an end, and I apologize if I used “CAM” in the wrong context, and to me CAM is a process that will take a CAD file and produce G code that is readable by a CNC machine.

1 Like

another approach for a transition to positional continuity:

Extend the surface (smooth, merge=no)


Then MatchSrf with preserve Curvature:

4 Likes

I wasn’t intending to say there was a right or wrong way of looking at “CAM”. I was just curious of your perspective. I see it better now I think, thank you for the insight.

Mostly I wasn’t sure what you saw as limitations on potential constraints that might inhibit the design approach.

With CAM I believe there’s many options, but sometimes you’re of course limited on what the machine setup is.

It sounds like you’re maybe using a 3 axis router to antiquate older workflows where you used to do it all by hand or mostly by hand, maybe using some power tools of course.

It sounds awesome that you’re using CNC to make things more faster and automated than before :slightly_smiling_face:

I hope your Gcode can do 3D contour. :beers:

nice :star_struck:

I’m curious about the post op processes after machining is complete. :slightly_smiling_face:

Aweseom info thanks everyone

  • i’ll mess with extend srf and see what i can do - thats a cool tip
  • i technically have enough to machine on … i set this up in MeshCAM last night and it looks ok so far; won’t know for sure until i can d a test cut
  • i still have that little bit of peaking where the halves join that i’ll have to sand out…i couldbt get the surface matching to fix that…?

I extended the layout lines, not the surfaces. Are you specifying Tangent or curvature when you are matching to adjacent surface? Refer to Sky’s videos - he covers all that in great detail. Look at Episode 6

check this maybe helpfull

Wrong NURBS modeling techniques result into overly-complicated and inaccurate end model. “Network surface” is the least usable surfacing tool in Rhino.

1 Like

well it looks ok to me,

That’s fine, but it creates unnecessarily complexity and is not the recommended way to model things.

2 Likes

Sure, it could do the job, as long as the file is used for creating a G-code for a hobby CNC-milling machine, followed by hand finishing of the resulting wooden part. However, modifications of the shape made with the Network surfaces shown in the above video are nearly impossible due to the massive amount of control points. The technique showed by @Gijs several posts above is the proper way to make such transitions.

I can also add that people who are taught to “solve” every shape with overly-complicated rough network surfaces, sooner or later, end up with dealing with plenty of issues, such like: bad objects, surface seams, wavy surfaces, inability to create proper offset surfaces, inability to modify the geometry, etc. The file size is also much larger that way.

2 Likes

If one does have to edit something in the future, I can see how NetworkSrf might be a real pain to modify, whereas a low control point NURBS surface would be pretty simple.

The poster of the video has some great information. Besides all the NetworkSrf and zillions of CV’s, my comments:

I like the curve layout, mostly. CurvatureGraph?

9:28 where he puts a reference line from the section at fret 15 (?) to the bridge end of the neck. If the neck tapers in thickness, the curve he then draws will not be tangent to the line from fret 1 to fret 15. But his environment map inspection seemed good (?).

41:28 when modeling the headstock, there were some deviations that could bite you somewhere further along, but maybe not today. A caveat if you want to 3D print a plastic guitar - ha!

I’ve tried a couple different settings but tbh i’m not sure which apply to my scenario