Nested Virtual: Virtual Subassembly with Virtual Part(s)
Posted: Thu Mar 25, 2021 11:47 am
I had a strange error today, and I think it has more to do with software changes than design flow, but I ask for feedback.
I have a stable large assembly, with external subassemblies and one virtual subassembly to connect piping discharges across the ceiling to exit the opposite wall. The virtual subassembly contains virtual parts for its tubing and piping. This was stable for a long time. I judge this in comparison to earlier large projects which were not organized as well into subassemblies.
Lately, I widely changed my workstation. I upgraded (in-place) to Windows 10, and had some VAR troubleshooting which led me to uninstall and reinstall DraftSight and Solidworks.
Today when I opened this large assembly, the virtual part within the virtual subassembly "could not be found" in a location found in a subfolder of AppData in a Temp folder - note this is not where the assembly is saved. Attempting to browse for a virtual entity is futile, because it is not a distinct file. I tried opening it in Large Assembly Mode as well as Resolved, both with the same error.
Thankfully, it was able to be fully restored to previous version saved earlier this month before I know that I had only added one external component in a prior process. That could have gone much worse.
So, should I avoid nesting virtual components in the future, or is this mostly because my temp directories changed through Win 10 upgrade?
I have a stable large assembly, with external subassemblies and one virtual subassembly to connect piping discharges across the ceiling to exit the opposite wall. The virtual subassembly contains virtual parts for its tubing and piping. This was stable for a long time. I judge this in comparison to earlier large projects which were not organized as well into subassemblies.
Lately, I widely changed my workstation. I upgraded (in-place) to Windows 10, and had some VAR troubleshooting which led me to uninstall and reinstall DraftSight and Solidworks.
Today when I opened this large assembly, the virtual part within the virtual subassembly "could not be found" in a location found in a subfolder of AppData in a Temp folder - note this is not where the assembly is saved. Attempting to browse for a virtual entity is futile, because it is not a distinct file. I tried opening it in Large Assembly Mode as well as Resolved, both with the same error.
Thankfully, it was able to be fully restored to previous version saved earlier this month before I know that I had only added one external component in a prior process. That could have gone much worse.
So, should I avoid nesting virtual components in the future, or is this mostly because my temp directories changed through Win 10 upgrade?