Hello, do the drawings have the same names as the parts and are in the same folder as the parts?
Hello
Which version are you on? if it's the 2015 or 2016 version, the take-away composition doesn't work which forced me to stay in SW2014, on the other hand if it's the 2018 version it must work unless your drawing refers to a part that is not in the file.
As for the 2017 version, I couldn't test.
If you use the term Pack & Go it means that you must be in SW2018, so no more a problem with the room/MEP link
Hello
I think you are working with different folders , 1 for MEPs, one for parts and another maybe for PDFs and these are a problem when using the Ang Go Pack. The easiest way is to have everything in the same folder and sort by type.
@ac cobra 421 if you have a part that is linked to an MEP it must integrate it into the pack&go, whether it is in the same folder or not.
That's why I'm leaning more towards a break in the link between the room and the MEP, the future will tell us;)
Hello
The term Pack & Go is also valid for SW2017 and it works well even if the plans are not in the same folder and/or do not have the same name as the 3D, provided that the links have not been broken by wild file movements of course.
Kind regards
Hello
Small clarification though, it works well as long as the plans are in the same folder as the 3D or in a lower level folder compared to the 3D, otherwise the Pack and Go seems to lose the links between the 3D and the 2D if you launch the pack and Go from the 3D, it works well from 2D and finds 3D well.
To put it simply, the Pack and Go works well from the file that is stored at the highest level in the Windows tree between 2D and 3D.
Kind regards
That's why I prefer to have everything in the same folder and sorted by type so that everything is at the same level. It gives less problems in terms of link loss.
@FUZ3D: with SW15 and 16, the take-home composition works by going through the Windows file explorer, right-click on the "master" file / Solidoworks / Take-away composition.
A bug known and recognized by Dassault, which did nothing to correct... (a fight with Microsoft...)