What's new
By:

Save error and corrupted files

L

LewisA

Member
I have the latest version V29 with the latest update. I use GLP with all of the parts and assemblies, that I design. I have been noticing when I change a value in the GLP and hit save then Update Designs, some of the parts in the assembly will disappear. I then have to edit each of those parts and regenerate to the last feature, because each part has all the features suppressed like I was starting the design. Then to top it off, at times when I then try to save the assembly, I get the errors you can see in the attached pdf.

When I open the parts again I find that some of the features are italics and if I check the status, it is either target no longer available, or if the sketch was on a plane I put in, the plane is not available. I have had to repeatedly re-create parts. I have multiple support tickets about this and support cannot find the issue. When I send a package, the problem doesn't show up on their end.

Questions:
1. Has anyone else seen anything like this?
2. If it is my computer, which I am beginning to think that is the problem, what do I need to look for. Please, don't tell me look for a new computer, lol.
3. I am using Norton anti virus, could that be the problem.

Another issue that I have had with GLP and updating design is when I dimension from an edge of a part, say locating a hole and then change the size of the part so the edge changes, the location of the hole is from a construction line and not the edge. Therefore, the hole is now in the wrong place. The construction line doesn't stay with the edge. Has anyone seen this?

I have also attached my system info. I am running Windows 11 V25H2, with latest updates.
 

Attachments

I think what's happening potentially a cause can be your hardware. Alibre's performance is directly tied to hardware. On my machines I never encounter these kinds of errors, bugs or behaviors. I see the opposite issue, Alibre being too slow for my machines and workflows. If support isn't having the same problems with your files, then that could be because of hardware.

My main Alibre PC:
GeForce RTX 4070, Intel 16-Core i7-14650HX, 64GB DDR5 RAM, 4TB SSD
My other installs run on highend macs.

Your files or workflow may require more resources for Alibre to function properly. Slow read/write speeds could cause problems. No or low powered GPU + high render settings with high system usage could cause problems.
 
I use packages to copy projects to another machine. I've always done this as a single Alibre user. I never seen personally any of these kinds of problems. I think because I always have highend maxed out hardware. It might be other reasons in each case.

I did have problems that resolved itself after I packaged and unpackaged an assembly. The issue was related to this thread.


I don't know exactly what resolved the issues. There were bug fixes in the next release, and I had upgraded my hardware.

You could try your packages, open a packaged project and see if you have the same issues.

If GUIDs are clashing internally that's a big bug.

[edit]

I was sure I discussed packages helping resolve problems but I can’t find it.

In the case I referenced above, I still had to redo the assembly from a backup. The originals were throwing save errors or errors on opening.
 
Last edited:
GUIDs only clash if the user copies (and then renames) files outside of Alibre (ending up with more than one file with same GUID). That can also cause apparently random swap out of parts in an assembly.

I did not say this is the cause here - but it is something to check for / eliminate as a factor.
 
stepalibre said:
I use packages to copy projects to another machine. I've always done this as a single Alibre user. I never seen personally any of these kinds of problems. I think because I always have highend maxed out hardware. It might be other reasons in each case.

I did have problems that resolved itself after I packaged and unpackaged an assembly. The issue was related to this thread.


I don't know exactly what resolved the issues. There were bug fixes in the next release, and I had upgraded my hardware.

You could try your packages, open a packaged project and see if you have the same issues.
Click to expand...
The above...
Was only addressing this.:
DavidJ said:
One thing to check (or eliminate) if you send assemblies to support as Package files - file GUIDs get re-assigned when the package is opened.
Click to expand...
The point, if packaging resolve issues, it might be a connection
DavidJ said:
something to check for / eliminate as a factor.
Click to expand...
 
You must log in or register to reply here.
Back
Top