Emulated Wii remote DeadZone? Pointer won't move?

[cammelspit]

Ok, so I will admit I haven't played any Wii remote games in a while but I decided to try and play Metroid on the Wii today because of how many changes there have been to the Wii remote stuff I have seen on the GitHub. The problem is, The Wii cursor feels completely different than the last time I used it and has made IR pointer games, frankly, unplayable. I recorded a video so you can actually see what is happening. Before, the IR pointer was what I can only describe as 1:1 based on my mouse movements, this was great and felt very natural compared to what a real Wii does. What is happening is that whenever I try to use the IR pointer it seems to have some kind of minimum speed required for it to actually make the cursor move. So, when I go and try to make small adjustments to my aim it just simply doesn't move at all until I move the mouse over a certain speed. A minimum movement threshold, dead zone, response curve, forced acceleration, whatever you want to call it, it's hard to explain exactly but I think you will get my meaning. So really I am asking two questions here, either one should suffice but why was this added?

1. How do I make Dolphins IR movements 1:1 to the mouse again?
   
2. How can I remove this minimum movement speed requirement?
   

https://youtu.be/41FiBmRY8i0

i56600K @ 4.5Ghz | R9380 @ 1010Mhz | Win 10 Pro x64 | 16GB DDR4 @ 3200 | Dolphin 5.0 - 1413

[JosJuice]

If you want it to be like in the past, don't enable Relative Input.

[cammelspit]

If you want it to be like in the past, don't enable Relative Input.

I am aware of relative input and I had it off. Thank you very much for responding, though, I have already fixed it... Seems every time I go and take the time to post here I end up figuring it out sooner than anyone else can help .

While I was in the process of trying to bisect the revision I had the problem, I notice that the old versions had a default and that default was cursor X/Y. The new revs don't have a default,  prolly because of the UI stuff, I would guess. I had set it to mouse axis via the auto detection instead of manually setting cursor, which I assume uses the actual X/Y coordinates on the screen instead. Magically, it is all good now and I apologize for bothering you guys. At least this is here so anyone else who has a similar question can find my solution. The only reason I didn't already have it already dialed in is because I had a recent HDD failure and lost my Dolphin saves because they were on my SSD. This time, I am going portable.  

Again, thanks for your time and have a fabulous rest of your day!

[JosJuice]

Good to hear that you solved it. I didn't know that there wasn't a default mapping for the IR anymore... I should check it out.