Have you run an evaluate/check on the geometry? I have found some knit errors arise from a general error or inconsistent edge, which can be narrowed down by rolling back feature by feature and re-running the check. Fill surface. I once found this to randomly change resultant edge ID's. Very Random, ...

The first time I dropped support, it was midway through the 2017 cycle, maybe SP3. I did manage to get SP5 via one of the resellers who has the installers available online. SP5 installed fine, even after being told during install that I did not qualify as support had stopped before the SP was releas...

In theory future version features are not exported and the model butchered accordingly I've worked in 2023 in a model that was saved from 2024. No butchering present. It was a surface model. There's been 2/3rds of FA development on surface features in recent years which means it is now possible to ...

I've been thinking about the addition of this feature and I concluded that a reason we are seeing this now is because the addition of new features (not just new ways to achieve the same thing, ie, SW2025 sketch colour change etc...) is definitely slowing down. Has anyone had an issue with saving to ...

I agree so much about the flat tree view! I searched far and wide on how to make SW allow folder creation in flat tree view, but so far came up with nothing. Your solution with dots is pretty neat. Although for a 100+ feature parts that's still a lot of scrolling :D I don't mind the scrolling too m...

I thought the feature tree was nicely organised. I did however hit Ctrl T straight away as I am allergic to absorbed features... and the tree was still tidy in flat view! I name features as you have, but as folders are not available in flat view, I add a dummy sketch containing just a point, then re...

It is definitely a SW tesselation issue with the curvature analysis. SW should not be deriving curvature combs from a mesh though, so that is weird if you are seeing differences in combs before/after knitting etc. A work around would be making your own intersections on a series of planes then displa...

After making the isophote cheat I spent time trying to add shortcut keys to control the image quality. There are some macros around to do this, but I found I'd have to manually go in and change image quality the first time after opening SW otherwise the macro would not work... I'm no macro expert so...

Hmm ok, that is odd if the surface curvature combs change after knitting etc.
How'd you find the isophote cheat? Unfortunately, it too is at the whim of the SW image quality settings...

Just quickly, as I do not have time today to have a look at the model - but are you basing 'surface quality' on the surface curvature analysis? The facets you can see are based on the analysis mesh SW generates which is typically way too coarse for useful analysis. You can try and change the curvatu...

Thanks for doing that! I cleaned up the code a bit as I had some errors due to the obsolete saveAs3! UU Option Explicit Dim swApp As SldWorks.SldWorks Dim swModel As SldWorks.ModelDoc2 Dim swModelDocExt As SldWorks.ModelDocExtension Dim opt As Long Dim lErrors As Long Dim lWarnings As Long Dim Units...

Splitting it across two sketches is something you need to do sometimes when using 3D sketches as SW will add a G2 constraint to a style spline, however no constraint exists as you can drag the 3rd CV around at will, which is the CV which is constrained via G2. Instead, the reference geometry needs t...

mgibeault wrote: ↑Fri Oct 27, 2023 3:43 pm Would you mind showing the first lines of the macro? I might miss some.

There is a link to a .txt file of the macro in the video description, have you had a look at that?
Also may be differences between needed versions of Rhino (6, 7, 8)?

For the mesh settings, to have a good evaluation, you could insert this script that works well for a document in inches: -Properties Object RenderMeshSettings Object AdvancedOptions Angle 15 AspectRatio 0 Distance 0 Density 1 Grid 16 MaxEdgeLength 0.015 MinEdgeLength 0.005 Enter Enter Enter Enter F...

Validating the surface for tooling - so looking at continuity, flow, divergence etc. 100% agree there. Zebra and curvature can be quite poor in SW, as the user has little control over the analysis mesh that SW generates. I have a macro set up to dump out any selected faces/bodies into Rhino where i...

But where Creo is better is in surface validation. This is the area they are really bothered about as they need to sign off data for tooling and right now the validation tools in Solidworks just don't cut the mustard (compared to the ones in creo). XNurbs doesn't really do validation, but GeometryW...

Central Innovation. They were my reseller, but they used some pretty poor tactics in emails to try and get me back on maintenance. Fear, doubt and unknowns... They shot themselves in the foot though, as their email encouraged me to look around and guess what, there is more than one reseller in NZ now!

You've hit the nail on the head. Am so use to not have to deal with normals in Solidworks because the Parasolid Kernal doesn't work that way. Which explains why it can be done as a solid and not a surface. In my Wildfire days, I did use the 'flip normal' feature a few times. It was quite handy for ...

I tried this with two surfaces in SW. One edge will knit, the other won't. Dump the geometry into Rhino and it can join one edge but when trying to join the other it gives an 'inconsistent normals' error. Honestly, this is unsurprising. Displaying normals illustrates the issue clearly.

Hi Jake, good stuff getting into this at 17! Steep learning curve as you have discovered. I modelled a 747-100 (based on the first 747) in Rhino a few years back and one of the most challenging things was the cockpit side glass. Lots of models you see if aircraft, the modeller has just trimmed the g...

Ok, thanks for confirming.
I tried reinstalling SP3 but that did not help. I've rolled back to SP2.
I'll report to my VAR now.

Edit - reported...

I've just updated to SW2023 SP3 and some surface features are not being named automatically. So far I have Offset srf, Sweep srf, Planar srf and Knit that are not being named. SW is naming them --1, --2, --3 etc. Boundary srf is being named correctly, as is Ruled srf. Has anyone else had this issue?...

Try swapping to flat feature tree view instead of nested view.

Great add, Mark. Many thanks. There's also an important topology lesson there. SW and the parasolid kernel hate hate HATE when things ALMOST match. The replace face trick turns an *almost* into an EXACT match. Another version of this is to ‘move face’ the face that is almost on the centreline, then...