Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Good morning Doug:
You are correct, that’s exactly what Wildfire 5 is doing. Upon regen of an instance from the main assembly it looks to the generic skeleton size instead of the skeleton instance size to establish the size of the component part.
I’m looking for a way to force the software to look to the new instance of the skeleton part to establish the size of the component parts and not the generic part it was created with. It seems like this would be a very simple and useful tool but I haven’t found a way to accomplish this.
By the way, send me an email to my address below. We share the same family name and may be related. I have a large family with many relatives that I’ve never met.
Have a terrific day!
Hello Doug,
I’m new to this PTC User group but not to ProE.
I’m responding to this tread because I have the same need as you to drive a assembly family table using a skeleton with its own family table. And I’ve experienced the exact same problem as described in this thread. It seems like PTC has placed intention in the software to do this type functionality but I just can’t figure it out and the documentation out there is lacking.
Have you come up with a solution for this problem? If so, could you please feel me in.
Thank you,
Peter Hines
Product Development Engineer
Otto Bock HealthCare
3820 West Great Lakes Drive
Salt Lake City, Utah84120
ph (801) 956-2515
fx (801) 956-2401