MacOS drag and drop in editor not working

Anyone experiencing drag-and-drop issues in editor in this beta(2018.2.0b2)? I just don’t understand what it’s causing this. I have a success ratio 1:100 to make drag-and-drop working just by spamming click-to-drag.

2 Likes

Could you please submit a bug report for this issue and reply in here with the case #?

I confirm this issue on Mac: Trying to drag an asset in the project window or a GameObject in hierarchy window works 50% of the time. Unity 2018.2.0.b2. I am reporting the problem.

Yes can confirm that bug. You have to try it two or three times for the same item until it finally gets dragged.

Can confirm as well

We have a known issue with the markers for dragging and dropping in the Hierarchy not appearing, but were unable to reproduce actual drag and drop difficulties. Unity Issue Tracker - [OSX] Markers for drag and dropping do not appear anymore in the Hierarchy

Could we please get bug reports from you if the issues you’re experiencing are not related to the one I linked to?

@LeonhardP I created a case for it case 1033847. It doesn’t happen every time, I find that if I switch the selection in the hierarchy window and then try to drag it tends to happen more often, but still not every time.

1 Like

I’ll test against 2018.1b1 this evening.

Was able to get to my laptop sooner, bug report submitted, case #1033916

1 Like

Getting the same problem in 2018.2.0b3 on OSX. Case #1034090

2 Likes

Same here in 2018.2.0b3.

Thanks for the bug reports everyone!
We were able to reproduce the behaviour and will address it ASAP. You can follow the resolution process here:

1 Like

Still occurring in 2018.2.0b4.

1 Like

Confirming that this happens in both b3 and b4, making it impossible to work with Unity on MacOS. Hoping for a hotfix released soon!

1 Like

Can confirm this. It seems that clicking and dragging slower will make it more likely to succeed. This has slowed workflow to a crawl.

We have a fix. Hopefully not long until it gets backported. Probably not going to be in b5 though :frowning:

Is there no way this could be added as a seperate package / hotfix? It is genuinely stopping me from any development this entire sprint, and if its not in b5, will mean the next sprint is forfeit too.

I know this is beta, but the editor is completely unusable and that is not okay?

1 Like

indeed at hotfix would be great… it’s quite unusable for many of the tasks we’re working on.

1 Like

At this point I’m just moving things in finder, it’s that much less of a pain. :face_with_spiral_eyes:

1 Like

Agreed! Normally companies that develop software would release a hot-fix asap for critical bugs like this. We’re currently required to work with the beta, and telling us that we have to wait for another 2 beta releases is not good enough. As paying customers we expect that the newest/beta versions will at least be usable.

1 Like