Hi @rivnix ,
To better understand what you are seeing, could you please share a bit more detail?
It would be very helpful if you could:
Explain what you mean by “loses tracking” (for example, do the projected lines break, lose associativity, or fail to update after edits?), and/or
Share a short screen recording or video showing the behavior
Let us know whether this happens in a specific design or across all designs
If possible, you can also attach a small .f3d/.f3z example file where this occurs.
With a concrete example or video, we’ll be in a much better position to determine whether this is expected behavior, a workflow issue, or something that needs to be investigated further.
They lose associativity very easy, especially on configured designs. When using projected lines to create mating features, or notches around geometry, and changing the parameter to grow or shrink the model, the projection lines will often lose the reference. Typically what I end up having to do is dimension the feature independently instead of being able to constrain it to the projected geo. While the work around is sound, it should not be necessary as the projections should be able to be used instead.
The best way to get this issue addressed is to provide examples if possible.
I think I know what the issue could be and a simple solution.
Hi! The projected sketch associativity is based on the project source geometry. In theory, when the source geometry changes, the projected sketch should update accordingly. However, it largely depends on the "change." For example, if the source geometry is lengthened or shortened or moved, the projected geometry should be updated without a problem.
However, if the source geometry is deleted, replaced, split, or degenerated (an edge becomes a vertex), the projected geometry will fail. It is because the original source geometry cannot be found.
Please share an example that exhibits the behavior. The forum experts can help take a closer look to see if the behavior is reasonable.
Many thanks!