Mac Editor: Undo causes RMB Fly-mode FOV wackiness

100% repeatable:

  1. Drag while holding RMB to fly around. Note it works.
  2. Select some object in viewport
  3. Move object using it’s gizmo.
  4. Drag while holding RMB to fly around. Note it still works.
  5. Hit Cmd-Z to undo to object transform
  6. Drag while holding RMB to fly around. Note crazy perspective distortion.

It will continue to have this distortion when holding RMB (even after releasing, and holding again) until you right-single-click once in viewport to bring up contextual menu, and then press Escape to close that menu.

Demo Movie

  • UE 4.4.0-2237849 Binary

  • OS X 10.9.4

  • iMac 3.5 GHz quad core i7, 16 GB RAM

  • NVIDIA GeForce GTX 780M 4 GB VRAM

Z is hotkey for zoom out. I’ve never experienced this issue you are having though and i cant reproduce it so i dont know whats up with it.

Edit: Just noticed that you are on Mac, i’m using Windows so it seems to be OS X related.

Hey swillits,

I’m not seeing this behavior. Does this happen in every project? Does it occur in a new project?

Yes. Every project. Even new ones. I’m using a pretty typical Logictech multi-button mouse since UE4 doesn’t work with Magic Mouse for some reason… (Should I file a report on that?)

I know that we’ve had issues with Magic Mouse in past, but if you’re experiencing issues with it currently, please make a new post with details. I’m looking into perspective distortion you’re seeing and will let you know what I find.

Okay, it sounds like your Z key is getting stuck after Undo operation. I’m not getting this to reproduce personally, but it sounds similar to other issues in 4.4 on Mac currently, and I’m informing developers of your post.

Yep. That’s what it is. Tapping Z after doing an undo un-sticks it.

Hey

We’re pretty sure this has been fixed along with several other issues in 4.4.1 hotfix, which should be released later afternoon. Could you try again after updating and let us know whether this behavior continues for you? Thanks!

Fix confirmed!

This has been fixed in 4.4.1.