Jumpy Orbit Rotation.

[tcrxelizondo]

Hello,

For some reason, when I use the ViewCube to rotate my design around, at some point during the rotation, the drawing makes a jumpy 180-degree rotation. So basically, while rotating my design it goes something like this: Smooth rotation, smooth rotation, smooth rotation, jumpy 180-degree rotation, smooth rotation, smooth rotation, smooth rotation, etc. Can someone tell me how to fix this issue so that the rotation is always smooth and there is no jumpiness?

To illustrate the issue, figure 1 below shows the design after being smoothly rotated counterclockwise right before is about to make the sharp 180-degree jumpy rotation. Figure 2 shows what happens after the sharp rotation (if I was to continue the counterclockwise rotation motion shown in figure 1). You can see the ViewCube how it goes from 'FRONT' to 'BACK' in an instant. Why?

Thanks.

[jhackney1972]

Use the Free Orbit command and take advantage of the Compass icon on the screen.  All I am doing is left click to center the point, on the compass, then place my cursor just outside the compass circle and left click and drag.  The View Cube is not an effective method to orbit consistently.

[tcrxelizondo]

Thanks for the response. I have actually been using the Free Orbit command and it works well, however, most if not all of my designs are so simple that the View Cube feature is more than sufficient and convenient (if it was workings the way it should).

To me, this "jumpy" behavior looks like a bug, I don't remember experiencing this problem before. Can someone from Autodesk confirm that this is a bug? If not a bug, is there a way to change this behavior?

Thanks.

[ryan.bales]

I replied on the case but i'm trying to get the timeline on when this is supposed to be fixed. I thought it have already been fixed, but its possible its in a forthcoming fix early next year.

[Rene.Elizondo]

A new version of Fusion 360 landed and the issue still there. Is this ever going to get fixed? It's my understanding that this bug has existed for almost 6 months (as of the time of post), is that not enough time to fix this bug?