Can't escape orbit!

[Anonymous]

The June update has introduced a serious problem for me, I cannot escape orbit once initiated. It's the exact same problem that 123D had a few releases ago. I open a scene, orbit the view and it gets stuck in orbit with no way to stop it. The machine is a bog standard win 7 pc. The May and earlier releases worked fine so I don't know what has changed but I cannot use F3D. All I can do is quit the program once it happens.

Any ideas?

[Phil.E]

Thanks for following up. 

[jasperF8RUK · Accepted solution]

@Anonymous @
Don't know if anybody was able to fix this already. I did find a way workaround to exit the forever, annoying, orbit, mode though.

 

[sergedagher]

Yes, I can confirm your solution works!

[mark.bushman]

This fixes it for me - this should be recorded as the definitive answer to this question.

Thank you ssmith!

[moe2FEJS]

Life saving trick here! I just hope everyone else finds their way this far through the post

[patrickobrien.wi]

Still an issue. Why does this take years to resolve?

[bpreston1]

I am having this same issue and it is becoming very frustrating. Did anyone ever find a solution?

[licheong]

It's 2023, and this problem still persist

[laughingcreek]

the process described in post 62 has been working for me.

[thechosenrick]

this is hilarious. i'm a senior software engineer i've never heard of a bug this old and so easily reproducible. if this message gets to 20 likes i'll apply to Autodesk just to fix this bug and then quit 

[Anonymous]

9 years this has been going on. Shame on you Autdoesk, you are culpably ignoring the problem.

[Anonymous]

You can imagine what it is like in a classroom with university students stressed on delivery and it dies. I have to recommend we move away from this software now.

[Phil.E]

Please try the posted workflows and workarounds to ensure your students know there are ways to avoid this.

I also want to point out a couple things for the record, because I think the problem is mischaracterized here and I don't want other customers to think there is no desire to fix this, or there is no possible workaround. That is just not the case.

1. The original post (2014) is not the same problem you are having today (starting at message 5 in 2021). 

2. There is a workaround that has a marked solution. That solution is the workaround for the problem you are having today. If it doesn't work for you, please create a new post and we can look at why the workaround doesn't work.

3. There is a technical issue blocking us from fixing it. We try to fix customer reported issues in a timely manner whenever possible. Of course we deeply want to fix this, and as I said, we are blocked for the time being.

In addition to the workaround that is marked as a solution to this post, there are other workflows that avoid it naturally.

• The only way to achieve this bug is to drag the view cube.
  • If you know of another way, please create a new post describing it.
• Orbiting with mouse or trackpad does not require the view cube. 

I appreciate your passion and desire to help other Fusion users by urging us to fix the bug. Please have continued patience while we work towards an eventual solution. 

[Anonymous]

>>The only way to achieve this bug is to drag the view cube.

Okay thanks for dismissing a customers claims, right on! So back at you: Why dont you just filter the event stream for that event? Block it? Not need it? They can work around that rather than face the gut wrenching feeling of losing their work?

[Anonymous]

Why is it taking ten years?

[Anonymous]

Deleting my account. 

[Phil.E]

I'm sorry for any misunderstanding but I'm not dismissing your claim. I take it very seriously which is why I'm offering the help of the posted solution and other workarounds. 

I didn't know that your students were losing data. There is no description of crashing, or being unable to save in this post that I'm aware of. Can you please describe what happens to cause loss of data for your students?

[jeanmarc_roberge]

As the person who started this post I would add the following. This issue is very frustrating and when it occurs for new users. The first reflex is not to search the Internet for a work around, the only way to get out of it is to exit the program and restart. I cannot imagine that Mircosoft would allow such a bug to persist this long in their software.
Fusion 360 is a great tool packed with very complex features, the fact that something this basic cannot be fixed is very difficult to comprehend. Saying that the Fussion 360 team was not aware that students could lose their work clearly indicates that the user impact of this bug is not understood. Also any suggestion that this bug be closed because there is a workaround or that it is experienced in different ways would just serve to doctor the stats on bug closure, from a user experience this is a real problem.

[Phil.E]

Hi,

Thanks for responding. 

Please be assured, there is no desire to close the bug. It should be fixed like all the other customer reported bugs that are fixed whenever there is the ability or opportunity to do so. 

The original post from 2014 is for a different problem on Windows.

Are you using windows? I ask because the vast majority of the posts on this thread, that begin in 2021 are referencing mac. 

The reproducing steps as reported by customers have been knowns since 2021.

Do you experience this bug in any way other than dragging the view cube to orbit? (and releasing the mouse on the model browser tree) If so, please describe how so I can try to reproduce it for the team working on this bug. So far, we are only tracking the case listed above> Dragging the view cube and landing the mouse on the browser.

If there is something I don't understand, please describe it or make a video to help us fix the things that bother you.