Project Geometry not yellow but purple (not adaptive i think)

[Charlies_3D_T]

Hello Guys,

I get this problem a lot and i hoped you guys could help.

If i have an ass and i edit a part and place a sketch in the part in the ass and i use project geometry i get the lines sometimes in yellow (what i want) and sometimes i get this in blue/purple.

I don't know why it gives me the 2 different line? I can't figure it out.

If i get the yellow line and i change something the line is moved like the part. But the blue line isn't. 

What am i missing? 

[johnsonshiue]

Hi! I believe one is associative but the other one is not. Typically, when you project an edge within the same part or across the part, the projected sketch and the edge should be associative. There are exceptions. 1) Somehow the geometry is missing or cannot be located after being projected. 2) Project assembly workplane or axis to a part sketch (there may be other similar behaviors in cross-context workflows).

If you can share an example here, we can take a further look.

Many thanks!

[Xun.Zhang]

Johnson is right. 

I'd like to talk about little about line color.

Blue: Not fully constrained and no associations with the reference.

Purple: Fully constrained and no associations with the reference.

Yellow: Keep associations with the reference and fully constrained.

Hope it helps!

[Charlies_3D_T]

Thank you! 

But the problem is that i don't know why it is giving me the yellow line and couple of minutes later it doesn't?

Can you only link to one part with the project geometry or can i link all the geometry i want? 

[johnsonshiue]

Hi Charlie,

Please share an example exhibiting the behavior. I would like to understand the behavior better.

Many thanks!

[kelly.young]

Hello @Charlies_3D_T are you able to embed a screenshot or record a screencast of what you are experiencing?

When you are creating your parts are they done individually and brought in with Place into an Assembly?

Or are you building them as Adaptive Parts within the Assembly?

If you break links or have missing components you can get sick geometry (pink). Like @Xun.Zhang states, black is unconstrained, blue is fully defined, yellow is projected. 

Please select the Accept as Solution button if a post solves your issue or answers your question.

[bradley.vanasse]

I have experienced this same problem. I get the sense that the previous answers have not understood the issue. I have attached a PDF showing screenshots of the assembly and the different kinds of projected items.

[johnsonshiue]

Hi Bradley,

I believe this is a limitation. In certain projection workflows, particularly from assembly to part or from part to assembly, the resultant projected geometry may be grounded. For example, if you project an assembly workpoint to a part sketch, you will get a grounded point. This is because there isn't a workflow allowing the part to update according to the assembly. Adaptive does not apply in this case.

Many thanks!

[gihaume]

I have the exact same issue and struggling with it from many days. There has to be a better answer. The tutorial help section doesn't explain what makes a projected line to be yellow or not.

[JDMather]

---

@gihaume wrote:

There has to be a better answer. 

---

Attach your assembly here and I’ll wager that you get a better answer.

[batmark12]

I found that the first sketch in a part can not be adaptive. Lines projected to the first sketch in a part will never be yellow. Try making another sketch in the part you are projecting to, and make geometry projections in this sketch. Hopefully this will work for you as it did for me.

[johnsonshiue]

Hi! I am sorry I think I am missing something. I am not aware of a limitation that the first sketch cannot be made adaptive. The only exception is that if the sketch is shared, it cannot be made adaptive. It has nothing to do with being the first though.

Many thanks!

[gihaume]

Exactly, sorry I never came back to tell what was the issue. In fact I had a few copies of the same files and that's what removed me the ability to make adaptative projections.

[davesmith00]

Hi all, Ive had this problem a few times. @johnsonshiue due to a bit of lack of understanding on my part, its is related to some of the issues ive be asking about in other threads related to adaptivity. It seems to raise its head when you are working with a part in an assembly with multiple model states. The part itself doesnt need to be in another state other tham primary, ive found it just needs to have them.... removing all additional model states then allows "yellow" projected geomatry onto that part from surrounding parts.

[johnsonshiue]

Hi! When you have a non-Primary Model State active, please avoid using Adaptive workflows. It is because Adaptive isn't fully supported in Model States. You will run into limitations fairly quickly. The limitations are two-fold. 1) When a given component has a non-Primary Model State, its own adaptive flag will be turned off.

2) An adaptive instance of a part or a subassembly can remain adaptive only in one Model State per hosting assembly.

Many thanks!

[k_alderlieste]

I was facing the same problem, that projected geometry was randomly locked eventhou the application settings were correct. The setting that made me able to use the adaptive projected geometry again was found in the Document settings of the part i wanted to project on. Under the modeling tab and than the "Adaptively Used in Assembly" had to be turned off for it to work how it was supposed to.

When you make the projected geometry the setting will be turned on again and if it works correctly your part (and assembly) should be put on adaptive automatically

[jtylerbc]

@k_alderlieste, That often happens because the part was created as a copy of another.  If the original part was adaptive, the copy still thinks it is adaptive in the original assembly too, even though it isn't actually placed in that assembly at all.

Since you can't have the same part be adaptive in multiple assemblies, this prevents you from setting the copy as adaptive.  Turning the setting off clears that adaptive link, allowing it to be recreated in the new assembly.

There may be other issues that can cause this problem, but this is probably the most common explanation.

[johnsonshiue]

Hi! If possible, please share an example that exhibits the behavior. It is either a limitation or a bug in Adaptivity.

Many thanks!

[k_alderlieste]

The casus that i'm working with is a frame made of u-profiles.

These were originally the same but the assembly + profile part have been copied and renamed before building the main assembly.

In the attatched picture there is the working case. When it wasn't working the projected geometry (green) got locked and wouldn't turn part 900-208 adaptive.

If it happens again ill reply again 🙂

[johnsonshiue]

Hi! I could be wrong but  I suspect this has something to do with the part being adaptive somewhere and reused elsewhere. An adaptive part can only be adaptive in one assembly and also in one instance. You cannot have multiple instances of the same part being adaptive at the same time.

Many thanks!