Can anyone give me a clue as to why this assembly always needs to be saved, even when first opened? The component in the assembly on its own doesn't have this problem.
Can anyone give me a clue as to why this assembly always needs to be saved, even when first opened? The component in the assembly on its own doesn't have this problem.
Thanks for having a look Glen. It's in my WPDM working folder (it's not in the vault). I tried saving it to different locations and even unloading the PDM addin but same result every time. If I hit rebuild or just save and re-open it's dirty.
What version of SW are you on Glenn? I'm on 2017 sp4.1 and this looks like it's something to do with mirrored components. I just created a simple assembly with a simple rectangle and when I mirrored the part I get the same result - always dirty.
Dave Hoder wrote:
What version of SW are you on Glenn? I'm on 2017 sp4.1 and this looks like it's something to do with mirrored components. I just created a simple assembly with a simple rectangle and when I mirrored the part I get the same result - always dirty.
How did you mirror the part?
I will always recommend number (1) One
I didn't even know there was a different mirror option in the menu that's not available on the ribbon or any tool bar. The scattered UI is the number two reason I cuss at SolidWorks so much, coming in right under the crap BOM editor.
All of our mirrored parts are opposite hand configurations, #3 in your list. If I create separate part files, regardless of how they're created, I don't have the dirty file issue. It seems to be opposite hand configurations only.
Just my opinion but I think #3 is the worst way to mirror a part has been proven to have issues for a lot of people over the years, stuff like that is what makes me move backwards at time. Rebuild issues are my biggest pet peeve and a huge data sap sucker..... You don't need to do what works best
Okay, when I first opened it it required a rebuild:
But after I save it, it doesn't show that message. I completely got out of SWX and back in and it opens fine now.
After just having to perform a clean install because of something similar, I'd say it's possible your installation is messed up. I don't have the diagnostic tools or knowledge your VAR does. So, before going through all that trouble, I'd send it off to the VAR.
Here's the thread I started about getting my settings back after I reinstalled:
How do I get my settings back???!!!
If you are using old templates or used Copy Settings Wizard from an old install, it can cause things like this.
Thanks Matt. I tested this on 3 machines here with same result.
Yeah, I tested my assembly on a couple machines up here and I got the same result because we were all using the same old Custom Settings file.
Are you on subscription?
Yes we're on subscription and I'm sending this off to our var. We don't all use the same custom settings file here. I dug up another library part with a mirrored component and it shows the same behavior.
For SW 2017 SP1 everything looks fine:
Thanks for verifying Vladimir!
Since this is a an assembly with 1 part and 2 configurations (1 config is a sub config of the other), then the way to make this so it doesn't have to be rebuilt every time you open it, is to add the "rebuild/save mark" to both configurations in the part.
Once you do that, the part no longer needs to be rebuilt.
I think it has something to do with the config data not being saved, and since the part is saved with one configuration active, it need to rebuild to create the other one.
Once you add the rebuild save mark, then the config data is saved with the part and you no longer need to rebuild it to create the 2nd config.
Dan,
I am not prompted to rebuild the part at all and I didn't have to take that step. Maybe there is something in your settings different than mine. When I switch configs, it just switches, no rebuild required:
Am I missing something or doing something different?
Matt Peneguy wrote:
Dan,
I am not prompted to rebuild the part at all and I didn't have to take that step. Maybe there is something in your settings different than mine. When I switch configs, it just switches, no rebuild required:
Am I missing something or doing something different?
What are your settings here?
Dan,
Here's my settings:
Hrmm....doesn't make sense then.
Matt Peneguy wrote:
Dan,
Here's my settings:
Something to check go to "Messages/Errors/Warnings" see if you may have hit that little box that says "Do not warn me Again" Somebody did it on my machine and some messages I knew I should get stopped showing up. They were on that page.
Thanks David,
I don't see that setting:
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
To follow up on my reply, I'm not prompted to save, even if I switch configs before closing.
Dave Hoder wrote:
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
After adding the rebuild/save mark, I no longer need to save it when I open and close it.
Hrmm...let me dig further.
Dave Hoder wrote:
Thank you Dan but the assembly doesn't need to be rebuilt, just saved. I tried your suggestion and added rebuild save marks to the configurations in both the part and the assembly but I still get the same result - the assembly needs to be saved every time it's opened.
Dave:
Do you have this checked?
And what do you have to "rebuild assembly on Load"?
Maybe that wasn't the answer, because I just tested it out with these settings (see below) and I still don't have to save it when I open and close it (SW 2017 Sp5):
I had verification unchecked and was set to always rebuild on load. I tried some different settings with no joy.
Dave,
Recently, I had some really screwy behavior on an assembly and had to reinstall SWX. But thinking about it, my templates may have been part of the problem all along.
So, I just checked the assembly you posted and your templates are from 2014.
It is probably not what is causing this problem, but it won't hurt to update your templates. You don't want to end up in the situation I ended up in. Having to do a clean reinstall takes a lot of time.
Hi Matt
These are library parts and rebuilding our library from scratch isn't really an option (I was just adding some smart features). I've seen some other issues since the Windows 10 fall update but I'm going to wait until we move to SW2018 for a fresh install if I can. I tried updating to sp5 but that didn't fix this issue or my SW Explorer problem (rename causes crash).
Dave Hoder wrote:
I had verification unchecked and was set to always rebuild on load. I tried some different settings with no joy.
after rebuilding, I would expect any file to be "dirty"...
Does the software track the last rebuild time? Otherwise, I don't know why that would be necessary. Could you elaborate on that?
Matt Peneguy wrote:
Does the software track the last rebuild time? Otherwise, I don't know why that would be necessary. Could you elaborate on that?
I do not know if a timestamp is involved in how SW keeps track of this or not. but rather than trying to compare pre and post rebuild models, SW just marks all files as "dirty" after rebuilding.
Hi Jeremy I guess I should have clarified the rebuild type. Hitting the rebuild icon (or Ctrl+B) is causing a dirty part assembly. (vs Ctrl+Q rebuilds the entire file and will always dirty the part assembly)
then that is suggestive of some sort of circular reference*
*(disclaimer - I have not opened the sample file you uploaded, and probably will not have time to do so.)
Did you try the Freeze Bar?
Didn't know about that. Is that a new feature? I'm still on 2015
I'll be using that in the near future!!! Thanks for sharing John!!!
Chris
Thanks John I've never used that. I gave it a whack but same result - assembly still dirty on open or rebuild.
Did you try to save the part as an IGES or a Parasolid, then try that file, if it works then I would copy over the one your using and be done with it.
Take a close look at the feature tree and all the sketches, sketch planes and look at all the sketch relations, somewhere you have a external relation, you might have a missing plane in on of the sketches, or one of the sketch points relation is broken. Look for question marks in the feature tree and go from there.
Also, I recently learned about SWX Rx safe mode. Try loading the assembly by bypassing all your settings and see if it is still dirty. SWX Tools>SWX Rx
I know I'm replying to John here, but it dovetails with his line of thinking...I think. Take a look into Design Checker. By building a set of checks for things John has pointed out, you may be able to quickly identify the underlying error.
BTW, your VAR has had your files for 6 days now...I know you should cut them some slack because of Christmas...But, have they been able to give you any guidance, yet?
My no-VAR, in typical fashion, gave me a completely useless response.
My question:
I verified this on 3 machines running SW 2017 sp4.1. Any assembly with a mirrored component is always marked as dirty when opened or after a rebuild. Attached is a test assembly I just created and some folks on the user forum have verified that it works fine in earlier service packs. Has this been reported and do you know if it's fixed in sp5?
The Response:
It appears this is intended behavior of the software. If you perform a force rebuild (CTRL+Q) you will be prompted to save the file in earlier versions and the latest version of the software. If you select the rebuild button located at the top of the standard toolbar you will not be prompted to save.
David,
I'm sorry to hear that. Did they send that and close the case on you or is it still open? If I got a response like that, I would assume my VAR misunderstood my question. But, I have a great VAR...I guess I just assume everyone is as lucky as I am.
They didn't close the ticket but the response is pretty typical. I find this forum far more useful and usually only ask the VAR as a last resort. It was the same with Autodesk products, we didn't pay for support because the forum was a much better resource.
Matt Peneguy wrote:
David,
I'm sorry to hear that. Did they send that and close the case on you or is it still open? If I got a response like that, I would assume my VAR misunderstood my question. But, I have a great VAR...I guess I just assume everyone is as lucky as I am.
I'm lucky to have
Those guys are right by my side and ready to assist, pronto.......
I get the same behavior if I create a simple extrusion as a test part and mirror it so it's not related to external references.
Good point John. I had to do a clean install and am not going to use copy settings wizard to get my settings back. I forgot about Freeze Bar. Good news is that the Help file led me right to it, this time...Right there in Tools>Options, System Options Tab>General>Enable Freeze bar...For anyone reading this post.
It didn't need to be saved when I opened it. Maybe it has something to do with where you have it saved?