BUG - getting stuck in orbit

[roambotics_scott]

I'm not quite sure what triggers this but I quite often find myself doing somethign in a browser then tabbing back to f360 only to find that I'm locked into some sort of orbit mode that I can not escape without quitting the app and re-opening it.

The cherry on top of this bug is that I can no longer intentionally get into that same mode on my trackpad so it's both impossible to get out of it once I get stuck there and want to do anything else and impossible to get into it when I want to do that.

[roambotics_scott]

Apparently it can also just happen spontaniously as well.

 [http://youtu.be/lMRCw-aJidc]

What's awful about all of these things is that they distract and interrupt the flow.

[cekuhnen]

yeo can confirm that

also the 3d view cube is bugged - resulting often in crazy rotation movements when hitting the display edge with the mouse

[Anonymous]

What usually works for me when something like this happens is choose free orbit and orbit a little (with shift and middle mouse), being sure that middle click more towards edge of screen, then choose contrained orbit again and try orbiting (again middle button clicking point being towards edge of screen).  Hope that helps. 

[roambotics_scott]

Yeah I tried that but with no luck.

.. also, I can't use shift + any number of taps on my trackpad to get into orbit anymore (which is another huge gripe; going to the cube might not seem like a big deal but it interrupts my flow and is a major pain in the **** in aggregate)

[cekuhnen]

Honestly for me what only works is quite Fusion and restart. It is a nasty bug.

[roambotics_scott]

What annoys me the most about this is that it's been broken in this way for so long.

[cekuhnen]

I have to agree on that one.

[roambotics_scott]

Yeah exactly / for me as well cekuhnen

Shut the whole thing down (which takes time), have it complain that it's in the process of uploading something, Once it's finally shut down, restart it [not close to instant]. Maybe (as just happened to me) get a scare where your design temporarily disappears from the dashboard (and, at the very least, have it say that you're working on the wrong version of something with no indication of what consequences that has or anything that you can do about it). Eventually get back to what you were doing (after at least 10 minutes / by which time you're pissed off and your flow is completely broken).

[dunderhead]

I press Escape Key to exit orbit mode.

I don't have the foggiest idea either why it happens, I never use this mode on purpose (exit for shift-mmb).

[Anonymous]

Sorry to hear your frustrations you're experiencing.  Does Restore Defaults in preferences do anything?

If the right version or autosaved file is not showing up, do you know how to access list of all versions in the A360? 

[Anonymous]

I actually tried exporting a .f3d file when what I think you're describing happened to me, to see if the problem might happen to be 'exportable' (doesn't seem to be).  But after exporting and going back to my workspace the problem seemed to go away (I was in CAM simulation mode and got kicked out of that mode, don't know if that has any relevance). 

[brianrepp]

Bug has been noted, archiving due to Bug notification being placed in Ideastation

[Anonymous]

DO SOMETHING ABOUT THIS AUTODESK!! ITS NOW NOVEMBER 2017 AND THIS STILL ISNT FIXED

[roambotics_scott]

They're never going to fix it @Anonymous

Please prove me wrong there @brianrepp

[brianrepp]

@roambotics_scott - we are actively working on a project that we are hopeful may fix this issue.  That said, my understanding from the team is they've had trouble with a 100% reproducible workflow, and have very few reports of the issue to work from.  Does anyone on this thread have a way to reproduce this consistently, and if so, would you mind sharing your machine + browser specs?

[dunderhead]

I can provide a clue. For those affected, try to replace your mouse, see if that helps.

I believe the underlying problem is that a micro-switch may wear out and contact bouncing then produces a couple of extra rapid-fire mouse events that are not filtered out in mouse driver. 

I guess that Fusion's event handler then partially locks up, so perhaps Autodesk folks can reproduce in a test harness by bursting a few middle-click up/down events much faster than humans generate them. (If I remember right it's the middle click button that's involved.)

[roambotics_scott]

I have a trackpad and have encountered the same issue on multiple different MacBook Pros

[roambotics_scott]

Sorry I can't reproduce it consistently, @brianrepp. If it helps, my specs follow. Will let you know if I find a way to trigger the issue (as far as I can tell, it seems to be completely random, though)