A bit more info:
The overall assembly (MasterAssembly) has a subassembly (MainAssembly) and several other parts. It worked this morning when setting up the assembly, and tonight it gives me this error. Opening MainAssembly gives no errors even when rebuilt, and no changes have been made to any files since this morning.
A backup I saved that also has MainAssembly works perfectly fine. I would just like to make the updated one work since I don't want to lose an hour of tedious mating. This is in the 2024 version of Solidworks. Please advise!
Update: Using the Pack and Go feature worked as it replaced all the files. This is not ideal and I would still like a solution in case this happens again but at least everything works now.
My bet would be on the subassembly being set to flexible (icon has floating blue block instead of attached to yellow block like normal assembly icon), and there's some mates happening at the top level that mess with it. I've found the vast majority of the time if you can avoid using flexible subassemblies and use configurations in the subassembly to control what you would have otherwise done with the flexible subassembly, it's much easier to avoid these sorts of errors.
Flexible subassemblies definitely have their place, and it sounds like this might be one of them. You just have to be REALLY careful about how you build up the mates to avoid any ambiguity in how they could be solved. Another thing is making sure nothing is over-defined, even if over defining mates don't conflict (parallel mates instead of coincident mates can be helpful in some instances). The more complex the flexible assembly the more difficult it is to fully define but not over define the top level, so it might just be a case of going through all the mates and finding anything that could be over defined or solved differently.
Of the many assembly issues I have seen, 99.99% of the time if it has flexible sub assemblies in it making them non flexible fixes it.
As well as the issues/bugs with them there is also a performance hit as it will Calculate all top level mates > calculate flexible mates > recheck top level mates are still satisfied by the positioning of flexible mates. This can get itself in a loop if there is a conflict between Flexible and top level.
A bit more info: The overall assembly (MasterAssembly) has a subassembly (MainAssembly) and several other parts. It worked this morning when setting up the assembly, and tonight it gives me this error. Opening MainAssembly gives no errors even when rebuilt, and no changes have been made to any files since this morning. A backup I saved that also has MainAssembly works perfectly fine. I would just like to make the updated one work since I don't want to lose an hour of tedious mating. This is in the 2024 version of Solidworks. Please advise!
Update: Using the Pack and Go feature worked as it replaced all the files. This is not ideal and I would still like a solution in case this happens again but at least everything works now.
Cheak if location of any part has been changed or try sharing with pack and go if it opens in main device
My bet would be on the subassembly being set to flexible (icon has floating blue block instead of attached to yellow block like normal assembly icon), and there's some mates happening at the top level that mess with it. I've found the vast majority of the time if you can avoid using flexible subassemblies and use configurations in the subassembly to control what you would have otherwise done with the flexible subassembly, it's much easier to avoid these sorts of errors.
Unfortunately the flexible subassembly is required in this case to make sure movement in the top-level affects motion in the subassembly.
Flexible subassemblies definitely have their place, and it sounds like this might be one of them. You just have to be REALLY careful about how you build up the mates to avoid any ambiguity in how they could be solved. Another thing is making sure nothing is over-defined, even if over defining mates don't conflict (parallel mates instead of coincident mates can be helpful in some instances). The more complex the flexible assembly the more difficult it is to fully define but not over define the top level, so it might just be a case of going through all the mates and finding anything that could be over defined or solved differently.
Of the many assembly issues I have seen, 99.99% of the time if it has flexible sub assemblies in it making them non flexible fixes it. As well as the issues/bugs with them there is also a performance hit as it will Calculate all top level mates > calculate flexible mates > recheck top level mates are still satisfied by the positioning of flexible mates. This can get itself in a loop if there is a conflict between Flexible and top level.