This is a rebase of
J-Peterson's 2011 Wii MotionPlus build onto the latest master (5.0-5667). It was rebased a few months ago by an anonymous user, then I updated it again for ubershader support.
Download
Source
Included is a config for XInput controllers made by the anonymous user as well as a readme on how to effectively use it.
note for anybody reading, if you have issues with this build, you have to get support in this thread. Nobody will care outside of this thread.
Instead of just rebasing something that was deemed not high enough quality to be used in mainline Dolphin, it'd be great if someone put this effort toward actually cleaning up the code and fixing some of the issues people pointed out with the branch.
This kind of thing will give people false hope that it'll actually be useable when it's really just a pain in the ass to do anything in the Wii Motion+ games.
Yeah, I just glanced through this and it's still just shoving everything into existing UI controls. That is not going to be usable for anything that isn't Skyward Sword, and even Skyward Sword will be miserable.
I'm gonna use this, thanks!
(10-15-2017, 03:43 AM)JMC47 Wrote: [ -> ]Instead of just rebasing something that was deemed not high enough quality to be used in mainline Dolphin, it'd be great if someone put this effort toward actually cleaning up the code and fixing some of the issues people pointed out with the branch.
I recently finished my masters thesis, so now i have some spare time till year's end. I'd like to do some some research regarding "TR"-Audio and the thrill of rewriting the Wiimote Codebase is also still there. I recently had an idea on how to do the Accelerometer and Gyro emulation. I'll see what i get done in that time, though no promises
(10-15-2017, 04:20 AM)Helios Wrote: [ -> ]Yeah, I just glanced through this and it's still just shoving everything into existing UI controls. That is not going to be usable for anything that isn't Skyward Sword, and even Skyward Sword will be miserable.
(10-23-2017, 03:01 PM)berniemarg Wrote: [ -> ]I'm gonna use this, thanks!
The internet in a nutshell.
(10-24-2017, 05:50 PM)Kurausukun Wrote: [ -> ]The internet in a nutshell.
AHAHHAHA well I really want to play skyward, and I'm saving all my money for a Switch so I can't buy a wiimote.
(10-24-2017, 03:15 AM)JulianLoehr Wrote: [ -> ]I recently finished my masters thesis, so now i have some spare time till year's end. I'd like to do some some research regarding "TR"-Audio and the thrill of rewriting the Wiimote Codebase is also still there. I recently had an idea on how to do the Accelerometer and Gyro emulation. I'll see what i get done in that time, though no promises
Software engineer with little spare time here, but I've debated taking a look through the code and giving it a go.
I know people have questioned how you can assign motion controls in the past, but that is a separate problem from Dolphin emulating them. A few years from now Wiimotes/Motion Pluses are going to be impossible to find, so users shouldn't be required to have one for normal system functionality. Basically, how you *assign* the controls is independent of Dolphin actually emulating them.
That being said, I have some ideas. I was wondering if it's a correct assumption that in 90% of all use cases you only have to worry about one axis of rotation at a time? If so, the control issue becomes a lot easier to solve.
One thought I had for a modernised emulated MotionPlus system was that when OpenXR is finalised, we'll have a reasonably simple way to support a wide range of motion controllers, although they'll probably all have completely different tracking methods to the Wii. If we implemented a simulation of the Wiimote, we could have that be controlled by a more generic motion controller, and then use the simulation to calculate what the values reported by each Wiimote sensor would be. Anything else would require hacks, even if it would be potentially a lot simpler than this.