Select Chamfer Edge

[mluterman]

When there is a chamfer error (dimension gets disconnected) and you try to Recover/reattach it, you never get the "Select chamfer edge" request the first time, I must always click Recover (red cross) twice to get that request to appear; then I can finally reattach the chamfer. Anybody else experiencing this? This has been happening for years now.

[johnsonshiue]

Hi Mitchell,

I guess I did not follow the exact same steps as yours. I could not reproduce it. The sick chamfer note requires two picks (chamfer edge and the reference edge). Could you share an example that illustrates the behavior?

Many thanks!

[mluterman]

Hello Johnson, this only happens when doing "Replace Model Geometry" in a .dwg (copied from a similar-looking part), so the workflow (and what happens along the way) is this:

-Copy an "old" .dwg and its associated .ipt as a starting point (using "Save As" command) for your new part/drawing and save both with new names.
-Click "Replace Model Geometry" to replace old .ipt with new one on that new .dwg; this is where most dimensions become orphaned ("disconnected").
-Click "Recover" on an orphaned Chamfer dimension, and it never displays "Select chamfer edge" the first time (so you exit the command).
-Click "Recover" for a second time, and magically, it requests, "Select chamfer edge", the way it should the first time (it always works the second time).

[CGBenner]

@mluterman 

Are you able to simply grab the connection point glyphs and drag them, without using the "Recover"?  It may take a few tries to figure out which one goes to the edge, and which to the reference... but maybe it will save the extra clicks?  I have not tested this.

[mluterman]

Unfortunately, that doesn't work with these orphaned chamfers, only orphaned dimensions.

[johnsonshiue · Accepted solution]

Hi Mitchell and Chris,

This is absolutely a bug. I am able to reproduce it in 2021, which regresses from 2020. The attached simple dataset can reproduce the behavior on Inventor 2021 and later. I will work with the project team to understand the behavior better. Hopefully, it will be fixed soon.

Many thanks!

[mluterman]

Thank you very much, Johnson. It's been "bugging" me for a long time...

[johnsonshiue]

Hi! This has been reported as INVGEN-70221.

Many thanks!