WF4, M100 * I have an assy with a single skeleton file.* The skeleton was created in that assy, not another.* The assy once had a second skeleton, but now does not.* The skeleton is not assembled by 'default', but is instead afterthe 3 default datum planes and assembled with 3 plane alignmentconstraints. In the config file for this client, I have set'multiple_skeletons_allowed' to 'yes'. If, however, the client configis not loaded for some reason, Pro/E will tell me that I have an invalidor second skeleton and I need to remove it. Of course, removing theskeleton pretty much hoses the assy. Not cool. I had removed the second skeleton to avoid this error. I don't want myclients having to deal with this if they don't have the option set.However, it seems that I still need it, best that I can tell, due to theno-default position of the skeleton. Is this correct functionality? Is there any other way around thisbesides using default placement for the skeleton? Doug SchaeferThis thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn