4 Replies Latest reply on Aug 17, 2018 3:48 PM by Scott Ellery

    Showing SolidWorks Configurations?

    Gabriel Mazzitelli

      Has anyone discovered a way to easily import multiple SolidWorks configurations into Visualize? I have assemblies where one specific part comes in a few different versions. I want to ideally be able to easily choose which part to show without having to create completely different Visualize projects.


      As far as I can tell, the configurations in Visualize are more for setting different material/lighting/etc... rather than different parts. When exporting a SolidWorks file with multiple configurations into Visualize it only imports the current configuration you are using. I was able to sometimes get parts in other configurations to show in Visualize by saving the SolidWorks file (updating visualize) while in each configuration. Then in Visualize I could set each the visibility of each part in different configurations. However, this quickly gets very messy when attempting to update the Visualize project after making changes in SolidWorks.


      Also, after renaming some Visualize projects they have lost the link to their respective SolidWorks file. Is there a way to link them together again?



        • Re: Showing SolidWorks Configurations?
          Ryan Navarro

          Here are my findings - maybe someone will have better advice.


          Depending on how many configurations you need, one workflow I have found is to manually import the models in, with "monitor file" off.

          This requires saving the SOLIDWORKS file for each configuration you want active and then importing. Then you can hide/show the different versions selectively.  You could alternatively import them into different "Model Sets" using that model set pulldown.



          This seems to work well for getting the various states of the model in there, but doesn't work too great with updates. You can update manually, selecting the Model and choosing "Reimport" down below. But that seems to sometimes reset all instances of the model since they share the same file name.


          For your files that lost references, maybe you can use the "Re-locate file" option to point to them again?