Accepted Solutions
The reference viewer supports such queries. Use the RMB in the model tree on the component of interest to activate the reference viewer as shown below.
Then set the context of the reference viewer to current component placement feature as seen here.
Yes, you are right it is actually possible to find constraint this way. But only one level further. And also when working on assebmly level you don't want to know which feature is creating this constraint. Most of the time(99.999%) you want to know which surface or which part is making constraint.
But this feature... it does something i don't know how to describe. It is unreadable.
For example:
In this case i've modeleed simple boxy thing and connected everything with coinsident constraints. Each box has 3 mating surfaces with previous one.
For some reason there is 4 reference surfaces from 1 extrude. But I've made mating by coinsident constraint with only 3 of them.
Next problem that i can see from here is that there is no children found. But if you look at the model it is obvious that next box is connected to the one I've highlited.
I always try to do these kind of analysis in 2D since its always pain in the ass. I would try getting parrents from pro-program, export it as text and build a quick tree with some programming in python/batch
@ilyachaban wrote:
Yes, you are right it is actually possible to find constraint this way. But only one level further. And also when working on assebmly level you don't want to know which feature is creating this constraint. Most of the time(99.999%) you want to know which surface or which part is making constraint.
But this feature... it does something i don't know how to describe. It is unreadable.
For example:
In this case i've modeleed simple boxy thing and connected everything with coinsident constraints. Each box has 3 mating surfaces with previous one.
For some reason there is 4 reference surfaces from 1 extrude. But I've made mating by coinsident constraint with only 3 of them.
Next problem that i can see from here is that there is no children found. But if you look at the model it is obvious that next box is connected to the one I've highlited.
Hi,
your testing model (6 identical parts) is the root of the problem.
