Sketch dimensions have lost their mind

[Witsend3486]

Hello,

Project Link: https://a360.co/2ZXw9iA

This behavior is so screwy I don't even know how to describe it.  Open up sketch 3 of Component 'Base'.  Right in the middle is a dimension that says 14.768536.  If you use the measurement tool, it says the two lines involved are, in fact, 14.768536 inches apart; however, if you hover over the dimension, it says it is dimension d108 and it has a value of 16 inches (which is what it is supposed to be).  If you go to Modify->Change Parameters and look under sketch 3, it, too, thinks that d108 is 16 inches.  Double clicking on the dimension and entering 16 doesn't get the sketch to change.  Furthermore, when you double click on the dimension, it comes up saying it is 16 inches even though the item you double-clicked on said 14.768536.

The dimension right below it, d80, has the same behavior: it thinks it is 1 inch, but it says it is 3.306161, which is also what it measures.

What's worse is that I got these dimensions by accidentally grabbing the sketch someplace and dragging it, even though it was correctly dimensioned previously and the lines had turned black.

I tried closing the project, shutting down Fusion, restarting, and re-opening, but it didn't fix the behavior.  I suppose I should try a reboot, but I really don't think that will help.

The little fingers of my left hand are very numb and I often type shift/ctrl/caps lock/Window/alt keys when I don't intend to (in addition to hitting ~/`, 1/!, or F1 when I mean Esc), so I probably typed something that confused the daylights out of Fusion, but, really, how Fusion could get so far off into crazy land so easily is less than fully impressive.

I suppose a massive corporate response is not needed.  I'll probably just open a new project and start over from scratch.  (The part I'm modeling is filled with odd-angled weirdness and the drawings I'm working from are incredibly confusing.  This is already my fifth attempt, so what's one more.)

Respectfully,

Bill

[jhackney1972]

If I go to the model link you provided, there is no geometry.  This is the message I get.  Attach your file to your forum question using the Attach file method found just below the Paste A Screencast URL box, it is more efficient.

[Witsend3486]

John,

I guess you wanted an .f3d file attached?  I think i've attached it below.

At the moment I'd be willing to blame Windows.  Microsoft just pushed through an update (subsequent to the Fusion problems) that wanted a reboot.  (Of course, I'm always willing to blame Windows.)  I just became aware and allowed the update/reboot but, unfortunately, I just re-opened the project and Fusion still seems to have the problem with it.  The .f3d file attached was generated post update/reboot, so maybe I can't blame Windows.

Respectfully,

Bill

[Phil.E]

@Witsend3486 Thanks for the file. I logged a bug for this.

The only advice I have at this time is to simplify the sketch. Perhaps this part can be done with a series of sketches, placing different features into their own sketches.

[Witsend3486 · Accepted solution]

Phil,

Thank you for the response, but I would put a low priority on the bug search.  I did as I suggested I would and just started the project over from scratch and, as you can see from the attached file, Fusion 360 handled it perfectly (just as it did the previous 4 tries at this part).  I must have typed something with my numb fingers that I didn't know about, or scratch-clicked with a wobbly finger, or something.  It is probably only of academic interest as to how Fusion can be sent off into such a state.

As an old friend at work often said, it is very difficult to make something foolproof because fools are so ingenious.

Respectfully,

Bill

[Phil.E]

I like that. Agree fully. I've tried to idiot customer proof everything I've designed as a designer years ago, and now as a QA tester. The customer always finds a way. 

Glad you got a working model. We'll peek at the guts of your design to try and figure it out. That's a really neat effect you created and if you did, someone else will. It's worth some time to dig in. The toughest thing for us is when development engineers say "I see the bug... but how did the customer do this?" Without steps to reproduce, it can be a short investigation.

Thanks for posting! Take care,