Hello is it necessary to save each instance to create accelerator file? But if i forget to save the instance is it possible to have unstability?? Thanks
What is the use case for this? do you need a complex, nested family table to see the speed difference vs using just the regular .idx method? I've seen this option for years. Thanks for showing how it works!
Well, you should NEVER use nested Family Tables. And it's not accelerator files vs. instance index files; you either use index files or index & accelerator files. But if you have large Family Tables - like several hundred components - in assemblies with high number of instances (washers, screws, nuts, etc.), accelerator files can improve performance. The assembly will retrieve the accelerator file instead of retrieving the generic, selecting the instance, and regenerating it. In large numbers, you can see benefits. Also, remember that a lot of this stuff was developed between 1986 and the early 1990s when computers were a lot slower and less powerful.
Is there way to select the annotations in the family table, so that in an instance i can have some annotations that i don't wont to appear in the others?
Instance Index files do not get checked into Windchill. They are particular to a local folder. They contain a list of all the instances of all the Family Tables that are stored in that particular folder. They facilitate retrieving instances from that folder. They are not associated with a particular CAD document, so they don't get checked into Windchill. As I mention at the end of the video, Instance Accelerator files get stored as secondary content in Windchill.
Is there a quick way to make drawings of family tables? Particularly flat patterns dxfs
Hello is it necessary to save each instance to create accelerator file? But if i forget to save the instance is it possible to have unstability?? Thanks
What is the use case for this? do you need a complex, nested family table to see the speed difference vs using just the regular .idx method? I've seen this option for years. Thanks for showing how it works!
Well, you should NEVER use nested Family Tables. And it's not accelerator files vs. instance index files; you either use index files or index & accelerator files. But if you have large Family Tables - like several hundred components - in assemblies with high number of instances (washers, screws, nuts, etc.), accelerator files can improve performance. The assembly will retrieve the accelerator file instead of retrieving the generic, selecting the instance, and regenerating it. In large numbers, you can see benefits. Also, remember that a lot of this stuff was developed between 1986 and the early 1990s when computers were a lot slower and less powerful.
Is there way to select the annotations in the family table, so that in an instance i can have some annotations that i don't wont to appear in the others?
If you place the Annotation Elements in an Annotation Feature, you can include or exclude them from instances just like any other features.
Will this idx and other file extension get checked in in windchill
Instance Index files do not get checked into Windchill. They are particular to a local folder. They contain a list of all the instances of all the Family Tables that are stored in that particular folder. They facilitate retrieving instances from that folder. They are not associated with a particular CAD document, so they don't get checked into Windchill.
As I mention at the end of the video, Instance Accelerator files get stored as secondary content in Windchill.