Hi there,
it seems that official Leap Motion plugin was released in a broken state in 4.8 (you get extreme jitter for all fingers). Luckily, this had been fixed by here.
Will this commit be part of 4.8.2?
Many thanks,
Hi ,
It looks like that should be included in 4.9, assuming it doesn’t cause any other issues.
Sorry , but I really don’t get it.
Epic’s own plugin is broken (completely unusable) in this major release (as it is case of VR preview).
So why bring developers unnecessary pain and headaches only that they can learn after hours of fiddeling around (like me) that this issue has been fixed internally but was artificially held back until a new major version many weeks later in future (and then tell them that upgrading a project isn’t recommended?)
Why not simply releasing it as hotfix? Isn’t that, what they are intended for? There are so many developers complaining about many bugs in UE4 currently, so if you fixed something, please make fixes available as fast as possible (at least if fixed don’t contain code-breaking changes).
I’m sorry that it’s affecting you badly, but hotfixes are pushed out for major, editor-breaking crashes and like. If editor is still usable, then any bug fixes can’t be made priority as they haven’t been tested extensively enough to release. There are exceptions made occasionally, and I’ll check if this could be one, but you can’t really expect it for a binary release.
With source, however, you can often grab a single fix and implement it. So GitHub link you posted could be synced with a source build, if you need it earlier than next release.
I really appreciate this honest answer, but seriously: ‘Extensive testing’? VR preview is broken (for almost a months now), leap motion plugin is broken also - both of them were working in 4.7. And Epic now refuses to fix them again because of QA concerns? Really? Sorry, but you have to admit that this sounds a little bit - bizarre (no offense)…
That’s nature of our binary release system. Again, you have source, and fix is available. If you need it sooner, by all means, implement it.
Hmm, yes, if this is only method to get fixes for critical bugs introduced by a new release until the next release that’s only way for me, I guess.
Seems I didn’t get hotfix-thing right. I was thinking that they are intended for critical, showstopper-bugs in general, not only for crashes (as far as I know broken VR preview will be fixed in 4.8.2 for example).
Sorry for bothering you, will use GIT version from now on. 
You’re not bothering me =)
Yea, hotfixes are only intended for critical crashes, but as I mentioned, sometimes other things make it in. I’m contacting Whiting about it, but I believe this one is too late for a 4.8.2 hotfix and I don’t believe there are plans for a third.
I can’t find a bug report in our system for leapmotion jitter, so it looks like our devs simply fixed issue upon finding it. Leapmotion itself is not essential to editor, and I would guess that majority of users (non-VR, at least) aren’t using it. There were plenty of people reporting VR preview bug, though, and devs recognized it as a concern (though I’m not sure what is or is not included in 4.8.2 hotfix yet). So that likely made it through because timing of fix was right. This one wasn’t, unfortunately.
Has this issue been resolved, so far I can’t see that it has been fixed.
It’s broken again in 4.9.
Maybe you should better try one of unofficial plugins like this: [Plugin] Leap Motion - Event Driven - C++ - Epic Developer Community Forums