Arc creation has issues with the initial point placement

[liam]

Version: Fusion 360 2.0.7400, Student License

OS: Windows 10 Pro

Issue: Issue with arc creation point not sticking to the mouse

Explained:

I have been having an issue with Fusion 360 for a while, where the first point of an arc to be placed will detach from the mouse, and 'stick' to one part of the screen. This means that I often have to use constraints to pull the first point to where I want to create the arc from, before I can even begin working with it. This sticking occurs even in a new sketch, so it does not appear to be that the initial point is trying to line up with other existing sketch elements (Not sure on the term to use for the dashed blue lines that show up to align things to in a sketch).

Attached is a video showing this behaviour.

Expected behaviour:

For the initial point of the arc to behave like all of the other sketch element creations, in that it sticks to the mouse, and snaps to the alignments as desired by the users input/settings.

[karina.harper]

Hi @liam 

Have you tried updating your graphics drivers?

What are your current graphics settings? (See this article for some examples of things you can do to limit your settings).

Do any of those settings make a difference?

Cheers,

Karina

[liam]

Hi @karina.harper 

My GPU is an EVGA RTX 2070xc, running the latest NVIDIA drivers.

Attached is a screenshot of the graphics diagnostic output - I have just turned on the "limit effects to optimise performance", as per the articles suggestion.

Turning that setting on has reduced the number of incidents of this problem occurring, however it has not solved it fully.

I could not imagine it being my GPU that causes it to occur in the first sketch of a new document, with nothing else in that sketch? Nor my CPU, an AMD 3700x, would be causing that issue, as it does not have an iGPU that Fusion would be getting confused with.

Thanks for the article though!

[karina.harper]

@liam 

Interesting that optimizing the graphics has improved the behavior. You might try changing your driver in Fusion to DirectX 9 in preferences and see if that makes a difference.

Do you notice any change in your task manager when the arc is trying to be placed?

Also, to clarify, it's just arc right? You haven't seen this with any other commands?

Cheers,

Karina

[davebYYPCU]

Just a thought, when I first reviewed the movie, (not working now) seemed to me, that the detachment from the cursor aligned with the Browser boundary.  Second point, is then lower down, and not effected by the Browser.

On such a big screen, it’s known that moving under the Browser (zone) produces similar effects.

Might help....

[liam]

@karina.harper, just testing in a new blank document, I have found that the issue does show up on all but the standard line and two point rectangle tools. It seems to affect all of the other ones, and is very easily replicable.

Is that the windows task manager that you are talking about, in regards to looking for arc placement?

If so, yes, moving the mouse around with any sketch tool selected in the blank document, will cause fusion to

shoot up from ~<8% CPU usage, right up-to potentially 25% usage.... which is not what I would expect...

The amount of CPU usage does not appear to correspond to the issue.

I think @davebYYPCU is onto something, as it does appear the browser boundary is the issue.

[liam]

@davebYYPCUI think you are onto something here.

Fiddling around some more, it does appear that this is the issue.

What is interesting, is that after selecting the sketch tool, and moving it around, and the issue shows up,

if I then zoom in, and move towards the -X direction, the issue seems to resolve itself? As if the browser

boundary was on the sketch canvas, rather than staying attached to the browser, and then when you zoom

and move, that boundary gets destroyed?

[lance.carocci]

Thanks for the report, @liam - I can reproduce this issue (and found a few more way this can happen, too) and will get it where it needs to go.

In addition to changing the width of the Browser, one interesting workaround appears to be using Fusion on a secondary, rather than primary display.

[liam]

Hi @lance.carocci 

Actually thinking about it, this issue was occurring on my secondary display, and on my primary.

My secondary is 1280 * 800, and my primary is a 1980 * 1080 screen. Maybe it is taking the scaling from the primary screen size, not the screen it is actually on, or something silly like that?

[liam]

@lance.carocci Just wondering if this ever ended up being fixed out of curiosity? I have only used Fusion on a Mac of late, with one screen.