Trying to combine two studies having identical mesh and fixtures I get an error message. "Cannot combine studies with different fixtures". Any suggestions? Thank you
can you give some more details about how you are trying to combine things?
if you setup a really simple block type model does the same workflow that you are using work?
Thank you Jared for your attention. Let me give you some details on the workaround I found in the meantime.
Two studies on the same model had identical fixtures. Apparently strictly identical: their name, their place in the list, their definition.
I have deleted all of them in one of the studies, copied and past the fixtures from the second study and recalculated the first study. Te probelm disappeared and I was able to build the combination in the pressure vessel design study.
Analogous things occur when importing temperatures from a thermal study: SW claims sometimes that it cannot interpolate the temperatures, even if the meshes of the thermal and structural study are identical (and it seams moreover that this is not necessary). But if I copy newly the mesh from one study to the other and resolve newly the problem disappears.
This is of course a pity, especially when the resolution times are of 1/2 hour as in my last job.
2012 or 2013 was the first version where you could mix and match mesh between studies
but generally the recommendation is to clone studies to ensure that they are compatible
SW 2014 SP4.0. I confirm that I duplicate a study when I want to apply different loads. Nevertheless it arrives sometimes that the two studies become 'incompatible' (fixtures not identical) in the sequel. I have not yet understood what produces this.
5 years later I was not able to run my initially proposed workaround. But now the following works.
I have advanced fixtures with reference geometry. The geometry is defned by plane surfaces. Instead of using a face of the model as refernece, I shall use a plane defined previously. Strange but working!
As a side note, the SOLIDWORKS Simulation R&D team made some improvements regarding the triggers for this message in the 2019 SP3 release. These code changes will help prevent false/unexpected occurrences of this message which affected certain systems in earlier versions.
Retrieving data ...