Sketch Dimension issues following 6.20 update

Sketch Dimension issues following 6.20 update

NewAmericanPublicArt
Contributor Contributor
663 Views
3 Replies
Message 1 of 4

Sketch Dimension issues following 6.20 update

NewAmericanPublicArt
Contributor
Contributor

I am currently working on a project with many fairly complex sketches. Following yesterdays update, the larger ones will not allow me to dimension any additional lines.

As an example. I have a line which is the outer edge of the sketch(constrained), I draw a line parallel to that (which works just fine) then I go to dimension the distance between the two and I am told it is over constrained. The newly drawn line is blue as it should be and the one I am attempting to dimension off of is black and constrained. 

I am now experiencing this problem in several other flies. 

I figured to remedy this I would just jam out a new sketch in a new file hoping this would be resolved so I could continue with my other work... I have reached a less developed point that in the previous sketches(which are now useless) and I am again experiencing the same "over constrained" issue.

 

Is anyone else experiencing this? did I forget how to use fusion while I was at lunch yesterday? Is there a limit to how many constraints can be used in one sketch?

 

I am sorry I don't have the file linked, this is my first time posting and I am unfamiliar with the process.

Thanks!


Screen Shot 2017-06-21 at 2.21.51 PM.png

Screen Shot 2017-06-21 at 2.22.02 PM.png Screen Shot 2017-06-21 at 2.22.08 PM.png

0 Likes
664 Views
3 Replies
Replies (3)
Message 2 of 4

paul.clauss
Alumni
Alumni

Hi @NewAmericanPublicArt

 

Thanks for posting! It looks like you are experiencing some issues withe sketch dimensions after the June 20th update to Fusion 360.

 

I agree that adding the dimension in your example should not overcontrain the sketch, but I have been unable to recreate this behavior in a new file. If you'd like to share the file with me I am happy to have a look - I would recommend exporting a local copy of the file and then attaching it to this forum thread using the Attachments field shown below:

Screen Shot 2017-06-21 at 1.58.56 PM.png

 

 We appreciate you bringing this to our attention! I look forward to hearing from you and having a look at the files.

 

 

 

Paul Clauss

Product Support Specialist




0 Likes
Message 3 of 4

NewAmericanPublicArt
Contributor
Contributor

Hi @paul.clauss

 

Attached is the file I took the screen shots from. It is still acting as it was earlier today. 

One of the other files that had the same problem is now running correctly. 

 

Thank you for taking the time to look in to this.

0 Likes
Message 4 of 4

paul.clauss
Alumni
Alumni

Hi @NewAmericanPublicArt

 

Thanks for attaching the file! I was able to reproduce the issue you described as well as find some interesting new behavior.

 

To be perfectly honest - I am unsure of what is causing this behavior! One piece of advice that I can give is to consider splitting up your large sketches into multiple smaller, simpler sketches. This may help avoid this issue in the future, or at least make it easier to troubleshoot sketch issues when they do occur.

 

As it seems that this sketch was fully defined and working properly before the update, I have logged a bug with our development team (FUS-33627). They will be looking into what may have triggered this issue in the update - thank you for bringing it to our attention.

 

In the meantime, I do have some thoughts. I was able to find some more interesting behavior that I wanted to share with you in the screencast below. It does look like some of the geometry cannot solve in its current state, which suggests to me that it is possible that there was an error in the sketch that was not caught by Fusion until the recent update. I apologize for any inconveniences this has caused you!

 

I will keep this thread updated with any new information I come across about this behavior. Please let me know if you see any other files that show this issue and if the issue resolves itself in other files like the one you mentioned in your last post.

 

Paul Clauss

Product Support Specialist




0 Likes