why *.crc files are created

[ASAMAL]

I am facing this problem in regular basis .Unnecessary *.crc files are created in working folder'


I do not know how to solve this problem.


Can anyone help me

 

[jason_]

This is a circular reference file, you have a circular reference in the assembly that you're working in that is created whenever you regenerate. You need to open it with a text editor and investigate the problem by looking at the models/features that it's telling you are the referenced objects. Do not ignore this message.


A likely scenario is while in an assembly, you've referenced a part later in the regen cycle for geometry creationin a part earlier in the regen cycle (higher up the tree). An example, someone assembles flange 2 to flange 1, flange 1 being higher in the model tree and without bolt holes. Someone then edits flange 1 to add holes and references flange 2's holes to create them. This can't be done.


There are config settings that disable the ability to do this. It's something that needs to be addressed or it will cause many problems for you later on down the road.

 

[kdmgooner]

We too have inherited a number of assemblies from our French colleagues and it does cause problems. Jason, you mention config settings to prevent circular references can you tell us what these are please

 

[jason_]

We too have inherited a number of assemblies from our French colleagues and it does cause problems. Jason, you mention config settings to prevent circular references can you tell us what these are please

There are quite a few and you will have to play around until you get a combination that works for your company. For instance, if your company uses top down design and skeletons you will want to allow designers to use skels as references. Copy Geoms can be create in the skels to pass down critical reference geometry but in a more controlled manner.


Just be careful to not over restrict your designers or it could make for an unproductive environment. We don't restrict too much but rather try to educate the designers on what kind of refs are good and bad.


Here are a handful of the more commonly used ones. Put these in your local config, company wide config or even the config.sup depending on how you want to enforce:


default_ext_ref_scope Sets default scope for externally referenced models.


default_object_scope_setting Sets default condition for reference control.


All (Default) - Any Model, None - Only current model and children, Skeletons - Any component in model's assembly and higher skeleton on branch. Subassembly - Only components and children in model's assembly





default_object_invalid_refs Sets default condition for reference handling.


Prohibit - System will abort all attempts to create external reference that violates scope. Copy - System will issue warning upon all attempts to create external reference that vioaltes scope.





allow_ref_scope_change


No - Displays the message "Reference scope changes are prohibited by the configuration file settings" when the Ref Scope user interface is changed


scope_invalid_refs


model_allow_ref_scope_change


There are more obscure ones. If you do a search in the "Options" area for scope and check off the "Search Descriptions" field you get all of the ones in this zip file.


2008-09-16_182606_scope_configs.zip








Hope this helps
Edited by: jason_

 

[jason_]

delete
Edited by: jason_