Matt wrote - “Composite curve. Joins multiple end-to-end sketches, 3D sketches, curves, edges”
Oh, ok.. I never saw that icon before. Never intentionally used one. If SW does that hidden, I have no idea.
the part only had round and square holes.
I deleted all of the holes, and the error remains.
[quote=Dtief190 post_id=2006 time=1617032992 user_id=147]
I tried the macro from Alin - Downloaded. Used Tools / Macro / run. Nothing happens or changes. Tried it on the assemblies, and all the way down to the .PRT file. Maybe there is something else I have to do? I never ran a macro before.
It’s not a read only file, I have edited these designs multiple times, never got the read only complaint screen.
Would updating to SW2020 make the problem go away by loading and letting SW update to the new version on saving?
[/quote]
My apologies; looks like I did not provide enough information.
Please watch this short video:
https://youtu.be/d1jfDPHaLEk
Also, the fixed file set is attached.
[quote=Dtief190 post_id=2006 time=1617032992 user_id=147]
I tried the macro from Alin - Downloaded. Used Tools / Macro / run. Nothing happens or changes. Tried it on the assemblies, and all the way down to the .PRT file. Maybe there is something else I have to do? I never ran a macro before.
It’s not a read only file, I have edited these designs multiple times, never got the read only complaint screen.
Would updating to SW2020 make the problem go away by loading and letting SW update to the new version on saving?
[/quote]
My apologies; looks like I did not provide enough information.
Please watch this short video:
https://youtu.be/d1jfDPHaLEk
Also, the fixed file set is attached.
[quote]It’s not a read only file, I have edited these designs multiple times, never got the read only complaint screen.[/quote]
This specific problem is not caused by read-only files.
The bug has been documented in SPR 722235 – ‘Sub assembly shows rebuild icon when inserted into top level assembly, no warning or rebuild icon (stop light) is shown when sub assembly is opened in its own window’ which was reported as fixed in SW2020 SP1.0. and reopened under SPR 1156595, which is currently open.
Starting with SW 2020 SP1.0, the CompCurves are still there, but they no longer give you rebuild warnings.
The creation of parasite CompCurves was due to a bug in creating mates. The bug was reported as fixed in SW 2021 SP 2.0.
Alin, do you know when the bug was introduced? Might be useful to figure out the number of potentially affected files.
Sorry, no idea. I think it is a very old bug.
mattpeneguy per the read only remark.
Matt, I have to think about it myself whether it is an annoyance or not. I believe there are some options in system options as well as the save dialog to not save read-only parts - but don’t know if they would alleviate the rebuild mark…
At about 0:24 in the video, you click a button that is named reveal hidden features. I don’t have this button. I can’t find it in any menu.
I tried using tools/macro / run macro/ with the macro file you posted earlier, but nothing happens. I also found that I can edit it, but I am not that good at code writing to know what it’s doing.
I need to be able to do this, as I have several designs that have these hidden comp curves causing this problem. They got propagated to a lot of similar designs that are all made from using pack and go to create new versions of similar designs.
Thank you,
Dave
Let’s have a remote session, so we can install the button on your toolbar. PM me your email address.
Also, you will probably want to install CAD+, so you can process all assemblies in all folders automatically. No more manual, repetitive work!
Update- I am part way through working this out with my VAR / tech support. So far, now at the same point I got to here… They sent me a macro, that appears to do nothing. So I am still stuck with the rebuild warnings.
Update - The macro from my VAR does the same thing - just disappears, with no resulting list to show the items. We discovered I am running 2018, and he only has a macro for 2019 and up.
The dates on the macro from Alin are all newer than 2018. Is whatever is different a big thing to change?
Have you tried stepping through the macro and see where it fails?
I just fixed the macro!
I did a web search for 2018 / 2019 differences. found this -
https://www.javelin-tech.com/blog/2019/10/solidworks-macro-not-running/
So I opened the macro editor. Opened the references window. It showed a handful of missing 2019 libraries. I un checked those, and checked the 2018 ones with the same names, and it worked. Deleted the comp curves that showed rebuild warnings, and the whole thing works now.
Great detective work there, solved your own problem. Javelin’s got some great articles (wink wink Alin )
I know posting to old thread is taboo in most cases. But I’m going to risk it because we have the “Rebuild warning that won’t go away” problem on a majority of our upper-level assemblies because it starts in a bunch of our lower-level assemblies. When the problem assembly is opened all is good, rebuilds with no errors or warnings. It only shows the rebuild icon from a parent assembly.
We figured out what the problem is, it’s configurations. Nothing to do with context refs. Rebuilding all the configs and/or turning on the “Rebuild all configs on save” mark does not help. All configs but one are some kind of corrupt causing the assembly to show the rebuild icon in parent assembly.
The only fix we’ve found is to delete and recreate all of the configs that cause the rebuild icon. No clue yet what is causing this. For the most part the differences between configs is just which mates are suppressed.
It sounds like a different cause. Mine were the hidden parasite comp curves.
I had some other assemblies that had rebuild errors, that showed up, that were related to configurations and mates, and that stuff. I spent about a week during a slow time cleaning up a couple of projects that had been through a lot of “change this” try that" kind of thing, leaving broken associations or something. Had a couple where a part used in 2 different assy’s had the same name. Stuff was confused. But those errors showed up in the assy that they were in also, not like the hidden ones.
Agreed, different cause. I was about to start a thread about this, but I always try to search topic before starting a new thread to see if it’s already been solved. Of course, the topic had several Google hits that were links to SWYMp which aren’t worth following. Next was this thread titled by symptom rather than problem. After reading it from start I recalled it as I was following it and worked through the suggestions as we were having this problem at same time. Anyway, I added the post just in case there’s someone else out there that might someday follow the same path, and it wasn’t due to file refs or comp curves.
Any chance you used assembly features/sketches/ref. geometry in any of the assemblies?
Did you use virtual parts?
Just went to look at a few examples. There’s a bunch floating around in our data set.
No assembly features such as sketches, planes, points, cuts…
some of the problem subassemblies had virtual parts, many do not.
Many of these assemblies have configs to show different positions and are purchased items, as such most of the sldprt files that make them up are imported geometry. I thought that maybe it was mate(s) to a face of an imported geometry in the component file that was causing the problem. Then some other config doesn’t cause the problem because that mate is suppressed in the one config. But the mates across all configs use the same faces to imported geometry. Also, when I delete then recreate the config I’ve started documenting mates in the config I’m about to delete then recreate them exactly. We’ve had problems with lazy/sloppy work of leaving mates suppressed that are not due to configurations. I had more on that but lead into the weeds so deleted it. It gets into things already discussed such as:
https://www.cadforum.net/viewtopic.php?p=18931#p18931
Virtual parts CAN be the problem - especially if you have a virtual assembly with virtual parts in it.
If you ever find the solution for this, I am eager to hear it. We might have some similar problems.
Let me know if you want me to take a look. We can do a quick remote session.