circular reference

[doug_anderson]

whilst busy working on fairly complicated model and using in-context modelling. CREO is good enough to inform you when you have mistakenly created a circular reference but gives no idea as to where it is. it may only be 1 constraint that is causing it. it would be great and very time saving if CREO could, as well point out the circular ref , point to the feature or constraint that is cause it. this could be done with the yellow triangle in the tree and a note in the info area.

[StephenW]

It's always been that way...not sure why.

Creo does create a .crc file in the working directory that describes the circular reference. I learned how to read those years ago. They look confusing, but then again, it's a circular argument. I usually look at the middle, that's usually the feature that you created the problem.

You can also use the reference viewer. It's a good tool that I have yet to master...I guess because I'm stubborn.

There are other "ideas" on the same topic.

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-debugging-for-circular-references-besides-crc-file/idi-p/488493

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-representation-for-circular-references-besides-crc-file/idi-p/563547

[doug_anderson]

it would be nice if the crc files was easier to read, hence why I thought having it noted in the feature tree would be great.

I try to avoid them and I've figured out whats caused the one I had. I haven't figured out how to spot it in the reference viewer but i'm still quite new to creo.

thanks

[MikkoHinkkanen]

Tools>Refrence Viewer

Works also from model tree: Right mouse button over component, Info>Refrence Viewer.

The functionality "select from parents" in mini-toolbar is also handy for fast investigation.

[doug_anderson]

that's handy to know, but will only be useful if you know which component is causing the error.

how can you tell from looking at the feature tree which is the problem component?

[MikkoHinkkanen]

Well, that did not land nicely.

So, youll have you crc file for potential candidates which you may start to investigate using those two tools.

As a part of this Product Idea, I would suggest that Creo Parametric would have Model Tree Query, that would consume the info from crc file. Please show only the components at model tree, which are part of circular refrence loop.

[doug_anderson]

hi, its all good. yeah I've used the crc files to help but it would still be great, as you then mention, to have the details easily available in the feature tree.

the crc files are not the easiest to decipher. would be good if they pointed directly to a looped part and the exact feature and then the dimensions or constraint. i'm assuming that if it pointed out the crc then it must know exactly what is causing it.

[doug_anderson]

hi. ok quick question.

some model from before I started with my company have circular refs. can you please explain what the 

depth of loop means, as some have 4, 5, 7 and 8?

from the loop how do I know which component / feature is causing the issue?

thanks

[MikkoHinkkanen]

Depth of loop = number of components patricipating

Break any of connections between components and you´ll break the loop.

[doug_anderson]

ok. so how do you figure out where the connections between the components are. the crc gives info, but how do you know from the loop info which feature is the issue and then if its a big sketch how do you know which dim or constraint is the issue?

[MikkoHinkkanen]

https://community.ptc.com/t5/Assembly-Design/How-to-find-circular-references-from-large-top-level-assembly/td-p/430045

https://www.youtube.com/watch?v=TDpaES3uCMM#:~:text=what%20are%20they%20well%20basically,references%20a%20again%20hence%20circular.

[doug_anderson]

thanks i'll have a look

[S_Edgenear]

Is Creo able to immediatly detect when a circular reference is created? If so, it should inform the user imediatly.

If they are detected only after whole assembly regeneration, maybe it's a lot more difficult to have the software provide the user immediate feedback.

[doug_anderson]

looks like its only after regen.🙁

[lwestbrook]

Pulling from @StephenW comment:

'There are other "ideas" on the same topic.

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-debugging-for-circular-references-besides-...

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-representation-for-circular-references-bes...

'