aggiornamento family table

[michelix]

hello to all, I hope the topic has not been discussed yet!! If you kill me!
work with the developed sheet and I often create family table of objects that vary by flat state and width... with version 4 of proes came out sti xpr file that if I don't remember badly before there were... I can't understand how to update them because sometimes if I change the features while checking the family table, the philges don't update me....I have to delete malicious stimuli files.xpr and he at that point recreates them correct...... is there a method, a macro, something that solves is what?? ? ?
Thank you very much

 

[nicksoft]

hello to all, I hope the topic has not been discussed yet!! If you kill me!
work with the developed sheet and I often create family table of objects that vary by flat state and width... with version 4 of proes came out sti xpr file that if I don't remember badly before there were... I can't understand how to update them because sometimes if I change the features while checking the family table, the philges don't update me....I have to delete malicious stimuli files.xpr and he at that point recreates them correct...... is there a method, a macro, something that solves is what?? ? ?
Thank you very much

there is the save_instance_accelerator configuration option to set up when creating xprs. If you want them back, set the value to none.

 

[Parametric_Ozzy]

there is the save_instance_accelerator configuration option to set up when creating xprs. If you want them back, set the value to none.

exact but.need to make it clear to what these "malefici" files are also needed. :smile:


are accelerating files variants, having the active pro/e creates these files :
for the parts: Namevariant.xpr
for assemblies: variable name:xas

allow faster opening in case of very substantial family table, clearly having it active not only check and update the idx index , but you should also update the variants accelerator file, otherwise xpr files are not updated, hence your problem, if in the option that mentioned nick put the value on save_object then to every change and save the family table also accelerator files are updated.

greetings

 

[michelix]

give more assistance you than the road rescue!!!! great!!! Thank you very much

 

[calacc]

Good morning, everyone. I exhume the discussion to talk again about the accelerating files of variants. Following a bit of cleaning I went to delete all files with xpr, xas and xrp extension (solution that freed me 5gb of space and of this I am very satisfied). going then to work on the assemblies I had suspended, all seasoned by family table and various interchanges I did not notice significant slowdowns in loading and regenerating pieces... So I said, what kind of files do you need if they don't accelerate anything? so I decided to set the option _ with the intent not to create them from now on.
I was wondering, how do you behave with that option? to you helps in the speed of loading and regeneration? But how much?
thank you all, soon.

 

[320i S]

personally, I abolished xprs from the night of time (intensive as from when I use pro-e/cree, or 2001); should help when you have very complex parts that require quite heavy regeneration to be loaded every time (unlike parts to if standing that have a status of storage, the mathematicians in family, are generated at opening).
if you use parts managed by light family, xpr are only occupation of public soil (memory).

 

[calacc]

thanks 320i s. in your intervention you mentioned only xpr files, do you think that you can extend the reasoning also for xas and xrp?

 

[320i S]

if I don't remember badly (it's a topic I repeat, I haven't faced for years):
xpr = parts in family
xas = axioms in family
xrp = simplified representations

if you do not have specific file-related needs, I think it is worth all the same speech.

 

[calacc]

Yes in fact I set the purge for those extensions there