I’m using this on a Mac with latest version of Mavericks. I didn’t have this issue until updating from 4.3 to 4.4. Most of the time within the editor I will have to double left click in order to get anything to work. If I single click a tab to switch to it, it will drag off of the window and I’ll be moving it around the screen. I also have to double click the + and - buttons to minimize or maximize, double click Play or Compile for it to work, and so on. The mouse functionality in the editor is really weird now. It’s so bad it’s getting in the way of an efficient workflow because I’m not used to having to do this just to navigate the editor and complete even the simplest tasks. Is this issue a known issue? Is it happening to others? If there is a fix please let me know!
I think I’ve narrowed down the issue. It seems like the editor thinks I’m holding left click instead of clicking and releasing. This is why it’s requiring me to double click for it to do anything. Never had this problem until upgrading and this doesn’t happen in any other apps.
Okay, it’s not segregated to just my project. I opened a new project and it does the same thing. I’m thinking this is a frame rate issue. Due to low frame rate the editor doesn’t recognize that I have released left click when I move the mouse away from where I click. It thinks I’m still holding left click. I have set the Scalability down to low and it still does it. Not sure what the issue actually is but just noticing some things that are happening and trying to narrow it down. This problem never happened on 4.3 even with Scalability set to Epic. It’s very frustrating.
I’m having the exact same problems using trackpad on the Mac. The trackpad input is really messed up for OS X in UE4.4. Will probably have to stick to 4.3 for the time being :(. Like you I usually have to double click on everything for it to work, and if I single click within the viewport, half the time the cursor gets stuck and then it thinks I’m permanently holding down the left mouse button.
It sucks that this issue is coming up for others as it’s a real hamper on production and efficiency but I’m glad in the sense that it isn’t only me experiencing these issues. I as well am using a Macbook but I had an external USB mouse connected. I haven’t tried using it with the trackpad. (ick! hehe) I had thought about it to see if the problem persisted but now that you’ve replied I’m going to give it a shot but I foresee the same issues.
Hopefully we can get an admin or staff reporting on this issue or providing some sort of fix to get by until an official hot fix can be released. I’m still not sure if it’s due to low frame rate but that shouldn’t be an issue with Scalability being on Low and still experiencing the problems. Like you I will probably stick to 4.3 for now until this gets resolved whereas it’s taking me twice the amount of time as normal to do anything.
Hi,
Could I ask you to try reproducing this in a common Epic sample project such as RealisticRendering?
You should enable the in-editor frame-rate counter when you do so, that way you can tell me what the editor frame rate is (in FPS & ms/frame):
From the Main Menu, select Unreal Editor > Preferences… > General > Miscellaneous > Performance > Show Frame Rate And Memory
Please also attach a summary of your machine specifications, or better still a system profile which you can generate using /Applications/Utilities/System Information.app, so that I know what kind of CPU, RAM & GPU setup you have.
I’m not able to reproduce this on a 2013 , quite understandably if it is a frame-rate related problem, but nor am I able to reproduce the problem in RealistcRendering on a 2012 MacBook Pro with Nvidia 650M. Are you running with a realtime viewport enabled? (Viewport options are in the top-left corner of the viewport - the unlabelled down arrow).
I do not believe this has anything to do with frame rates as my frame rate is above 30 and I have the same problem. It’s editor-wide, most buttons require two clicks and when you click in a viewport it seems to think you’re clicking and dragging (even though you only clicked once, so you have to click again to make it in-click the mouse button).
I’m on the with 750m, 16gb ram. Try the touchpad on your retina, and enable tap-to-click rather than using the physical trackpad button. That’s how I have mine configured and the editor is completely unusable.
No issues on 4.3 or lower.
Also, this does not seem to depend on any project, it is for the entire editor, even the project selection dialog has the same problem where you have to click open twice.
Strangely, using my bluetooth mouse, I have no problems, for me it is only broken on trackpad, which is bad since I exclusively use trackpads. But I thought I’d try it. Apparently this does affect mouse users too based on the reporters comments.
I’m using the same computer specs as Raziel except I’m using a USB wired mouse and experiencing these issues. He’s also right as far as the different projects or scenes. It happens no matter where I’m at or what’s open in the editor unfortunately. No issues here on 4.3 or lower either.
Out of interest sake, are you using 10.9 or 10.10? I’m on 10.10 but can confirm that 4.3 worked perfectly. Now both animation and mouse input is broken in 4.4.
Hi guys,
Just to confirm - when you open the project selection dialog do you find that you can click on the New or Existing Project tab and the tab highlight goes orange, but doesn’t actually switch the visible tab?
Then if you try to click on a project icon, nothing happens?
If that’s the case then I can reproduce what you are seeing here on the 4.4 release.
As an aside, at present we are not actively testing against pre-release versions of OS X. If you are running on the Developer Preview or Beta releases of Yosemite you do so at your own risk 
It sounds like you have it reproduced, yes. Once you start using the editor you’ll notice how bad it is, like, you’d click on the viewport and all of a sudden your mouse is captured and you’re looking around until you click again. Then you click on a button, but it does nothing, so you have to click it again. That kind of thing.
Did you have to switch to 10.10 to reproduce it? So far I’ve not had a single problem with UE4 on Yosemite, it worked perfectly, at least until 4.4 arrived - now two major parts of the engine stopped working properly. Mouse input and skeletal animation.
I realise I’m somewhat on my own here, but wouldn’t it be best to avoid changes that are incompatible with 10.10 as that is releasing very soon. Keeping in mind that 4.3 worked perfectly.
- This is all on 10.9 - we don’t support running UE4 on pre-release versions of OS X.
- I’ve not managed to reproduce the in-editor problems so far.
- We don’t deliberately make changes to break things but it does happen, best intentions and all.
I have been having the same problems on my Mac which is using 10.9.4. That and along with major lag and it crashing quite often; for example when ever I try to open any of the Maximo anim pack files (except Alpha). My Mac also meets the requirements.
Lego, yep I am aware that this affects 10.9 too and am trying to look into it.
Please post a separate AnswerHub question for your crashes, including the logs from ~/Library/Logs/Unreal Engine/.
In reply to 1: That’s good as I was not expecting it to be specific to 10.10, as mentioned, it’s been pretty rock solid in the time I’ve been using it.
2: That’s really weird… I’m seeing these kinds of problems everywhere in the editor. Keeping in mind it doesn’t always trigger the bug. So just use it for a while, you may find you just have less of a problem than we do.
3: Around 10.10, I know it’s not intentional, I’m just saying that some limited testing on it now could avoid a lot of pain when everyone upgrades in October(?).
I’ve identified the cause of the problem & understand what’s been going on. It is timing dependent, so it won’t consistently reproduce, hence why I haven’t seen it in the editor and why our QA didn’t spot it sooner. Fixing it will take a little longer & I’ve no idea which release the fix would end up being part of.
Future releases will be tested against Yosemite so that we are ready for it when it arrives, but we have to pick our battles until then.
I’ve fixed this problem, at the cost of reintroducing some lesser issues, for a 4.4.1 update. Not sure when this will be released, but it should return mouse handling to the same state as in 4.3 which should help you get on. Apologies for the inconvenience & thanks for clarifying things for me - knowing what you were seeing helped enormously.
That is great news, thanks so much!
Thanks for the info and for investigating this issue for us. That’s why I love the Epic staff. You guys are awesome!