hey man thanks a million for this video and file. I have been banging my head on this exact topic for a week. And the file! I was all ready to go and recreate the file from your vid (which i will still do) but then you put a link in the description! How do I thumbs up the video twice!?!?🤩
I found your channel whilst looking for tips on resolving degenerate surfaces...and I'm really glad I did. Some real gems here. Thank you. I'm surprised to see points defined by "Distance" at 6:23 rather than by "Percentage". It's good that the points will retain their even distribution when a model change alters the lengths of these curves, but to anyone who didn't know how those points were created, it won't be obvious that they're evenly distributed. I wonder what SW would do if some well-meaning person rounded that 3.88277... to two or three decimal places to make it look more "intentional". I really would have expected SW to default to "Percentage" for evenly distributed points. There should, at the very least, be buttons to choose between distance and percentage when initially creating the points. I might ask my reseller to raise a ticket for this. Edit: I just tested the effect of altering the "Distance", hoping that SW (2022 SP5.0) might maintain the percentage of whatever the edited distance was, i.e. if the rounded down value equated to 32% instead of 33.33%, I had hoped that the 32% would be retained when the curve length changed, but it doesn't. SW converts it to an unintelligent fixed "Distance" along the curve. Any other points created at the same time, but not subsequently edited retain their even distribution relationship, so as you say, there IS something going on behind the scenes...but it's not quite smart enough yet.
Hi there. It’s a shame that the reference point feature does not expose the point location percentage to equations, as that’d be very handy for this situation. I’ve not used 2024 so maybe they have finally allowed reference point percentages to be controlled externally.
Sorry for comments all being similar, Andrew, but .... this video deserves the same as many, many of your previous videos ==> Great job man !!! + thks for sharing your knowledge to all
Great tutorial, could you explain why you used tangent to face in your boundary surface instead of the curvature to face? Since you were trying to get G3 I would have thought to use the curvature relation. thanks!
Hi there, that is a good question. Quite often when using boundary surfaces, if the boundaries and any cross section curves are CC, then the resulting surface appears to be CC as well, even though the boundary condition is set to tangent. Lots of times in these situations setting the boundary to CC results in no improvement in the surface flow and sometimes ends up with SW forcing a small wrinkle along the affected boundary. I'm waiting for Dassault to add a G3 constraint to the boundary surface, as it seems a bit lacking to have G3 for sketches but not surfaces. Also, Solidworks has no native tools to check whether a boundary is actually CC, so I have been running surfaces through Rhino and using the Global Edge Continuity tool, which can check boundaries for G0, G1 and G2 and lets you know the tolerance on those edges. Thanks for watching and commenting!
Hey Andrew, love the videos, always have some amazing techniques. I've pretty much exclusively done parametric modelling in my career but Rhino is something I've always wanted to sit down and learn. I'm curious, in your real-world work what does your workflow involve? i.e do you create these kinds of surface models in Rhino and port over to SW for detail design? My basic knowledge of Rhino is that these kinds of forms are much easier to create.
Hi Phil, good question. I've worked on very few projects where something has been built in Rhino then imported into SW for further modelling. Clients would always prefer to have everything in one package if possible. Especially in the later design phases. The pebble surfaces would be much leaner and cleaner in Rhino, with the trade off being having to rebuild and rematch surfaces if you make alterations, vs SW (hopefully) updating and being quicker to test things out. Rhino does have history on some functions and seeing as the pebble is pretty simple from a layout POV, you could probably make this and tweak things fairly easily without fully rebuilding. Cheers, AJ
hey man thanks a million for this video and file. I have been banging my head on this exact topic for a week. And the file! I was all ready to go and recreate the file from your vid (which i will still do) but then you put a link in the description! How do I thumbs up the video twice!?!?🤩
All good! Thanks for the comment. AJ
Andrew Jackson. You did it again my man. Another awesome tutorial. I’m amazed with your knowledge on Solidworks. This is gold👏🏽
All good! Thanks for watching.
I found your channel whilst looking for tips on resolving degenerate surfaces...and I'm really glad I did. Some real gems here. Thank you.
I'm surprised to see points defined by "Distance" at 6:23 rather than by "Percentage". It's good that the points will retain their even distribution when a model change alters the lengths of these curves, but to anyone who didn't know how those points were created, it won't be obvious that they're evenly distributed. I wonder what SW would do if some well-meaning person rounded that 3.88277... to two or three decimal places to make it look more "intentional".
I really would have expected SW to default to "Percentage" for evenly distributed points. There should, at the very least, be buttons to choose between distance and percentage when initially creating the points. I might ask my reseller to raise a ticket for this.
Edit:
I just tested the effect of altering the "Distance", hoping that SW (2022 SP5.0) might maintain the percentage of whatever the edited distance was, i.e. if the rounded down value equated to 32% instead of 33.33%, I had hoped that the 32% would be retained when the curve length changed, but it doesn't. SW converts it to an unintelligent fixed "Distance" along the curve. Any other points created at the same time, but not subsequently edited retain their even distribution relationship, so as you say, there IS something going on behind the scenes...but it's not quite smart enough yet.
Hi there. It’s a shame that the reference point feature does not expose the point location percentage to equations, as that’d be very handy for this situation. I’ve not used 2024 so maybe they have finally allowed reference point percentages to be controlled externally.
this man is a treasure
The end result is "fairly smooth" he says.
Dude, it's way better than that! :)
Got to keep up the Kiwi understatement :)
@@AndrewJacksonDesignStudio I didn't know that was a thing, but now I do. Keep rocking man!
Yep, can be a little like the Monty Python ‘just a scratch’ thing 😉
Good job Andrew
Subscribed and liked really appreciate your content Andrew.
All good, thanks for watching Liam
So nice
Sorry for comments all being similar, Andrew, but .... this video deserves the same as many, many of your previous videos ==> Great job man !!! + thks for sharing your knowledge to all
All good!
Thank you, King! :)
Great tutorial, could you explain why you used tangent to face in your boundary surface instead of the curvature to face? Since you were trying to get G3 I would have thought to use the curvature relation. thanks!
Hi there, that is a good question. Quite often when using boundary surfaces, if the boundaries and any cross section curves are CC, then the resulting surface appears to be CC as well, even though the boundary condition is set to tangent. Lots of times in these situations setting the boundary to CC results in no improvement in the surface flow and sometimes ends up with SW forcing a small wrinkle along the affected boundary. I'm waiting for Dassault to add a G3 constraint to the boundary surface, as it seems a bit lacking to have G3 for sketches but not surfaces. Also, Solidworks has no native tools to check whether a boundary is actually CC, so I have been running surfaces through Rhino and using the Global Edge Continuity tool, which can check boundaries for G0, G1 and G2 and lets you know the tolerance on those edges. Thanks for watching and commenting!
Hey Andrew, love the videos, always have some amazing techniques. I've pretty much exclusively done parametric modelling in my career but Rhino is something I've always wanted to sit down and learn. I'm curious, in your real-world work what does your workflow involve? i.e do you create these kinds of surface models in Rhino and port over to SW for detail design? My basic knowledge of Rhino is that these kinds of forms are much easier to create.
Hi Phil, good question. I've worked on very few projects where something has been built in Rhino then imported into SW for further modelling. Clients would always prefer to have everything in one package if possible. Especially in the later design phases.
The pebble surfaces would be much leaner and cleaner in Rhino, with the trade off being having to rebuild and rematch surfaces if you make alterations, vs SW (hopefully) updating and being quicker to test things out. Rhino does have history on some functions and seeing as the pebble is pretty simple from a layout POV, you could probably make this and tweak things fairly easily without fully rebuilding. Cheers, AJ