![]() ![]() Its nice to see that all that reading and researching really paid off. I had the idea of scrapping the laptop and going much faster with the Xbee’s and getting away from all the extra wii stuff that was getting in the way. Whats nice is that when i first did this i was using the johnny lee library and a laptop with a bluetooth (9600) module to transfer the data first from the wii to the laptop and then again from the laptop to the controller. Its definately working though and it is fast! ![]() Still a work in progress but its really coming along. You can also try allowing Dolphin to take over your Bluetooth adapter with 'Bluetooth Passthough'. Connecting Wii remotes on Windows can be problematic. I also have a small issue with the xbee’s losing part of the 2 byte readings every 20 or so seconds, makes the dot jump across the screen when it happens. You are correct that Android requires the DolphinBar to work with real Wii remotes. i just averaged the last 3 readings and it gets rid of most of the twitching (which i think is caused by the resolution of the camera trying to make measurements on small dots that are 6+ feet from the camera). Yeah, i actually did that later (and put it in a smaller enclosure). Probably the: " + ADDR_SENSOR + " address is wrong ?", e) Throw new Exception("Can't communicate with the I2C bus. Private I2CDevice _camera = new I2CDevice(new I2CDevice.Configuration(ADDR_SENSOR, 400)) Return "X: " + x + " - Y: " + y + " - S: " + size I tried it again after I noticed you mentioned to try logging, nothing notable was logged, but the Gyroscope's behavior has changed.Private const byte ADDR_SENSOR = 0xB0 > 1 Thank you for your reply! Looks like there indeed is an issue with the Gyroscope, this video is with me holding the remote still, and towards the end I just rotate it a bit to see, as you can notice in the Accelerometer: Looking at what's happening on the Gyroscope indicator on the "Motion Input" tab might give some insight.Īlso see if Dolphin generates any useful log output while the remote connects (you'll need to enable logging if you haven't already). ![]() (11-14-2020, 05:40 AM)Billiard26 Wrote: You could try Dolphin's "Connect Wii Remotes for Emulated Controllers" feature and load the included "Wii Remote with MotionPlus Pointing" profile. In any case, what are the things I can try to get this working or narrow down the fault? Thank you in advance! Is it safe to assume the controller's motion plus is broken? It's a relatively new controller so I doubt it. Sensor Bar works fine, and the correct location setting is set (above), normal IR pointing works fine in other non motion plus games and the home menu screen.r So it's safe to say it isn't a problem with the adapter. With some of the adapters I've tried where I can get Bluetooth Passthrough working, even then the same issue persisted. So far what I've tried is using many different bluetooth adapters, the one I'm currently using is a branded Asus BT-400, I've tried others as well and the same issue persists. In Red Steel 2 also I get similar issues where certain/most movements don't get registered properly. Other cases like in the game, the sword moves horizontally but not vertically, and vice versa at times. Some cases the motion plus gets too sensitive. It is detected fine and everything, but for example in Skyward Sword, the pointer in the menu isn't responsive to my movement and in some directions it is sensitive and responds, and to others it is much less. The problem is the motion plus doesn't work properly anymore. I have a Original Red Wii Remote Plus, the model number is RVL-036, it's not a TR version as far as I know as it didn't say when connecting it to my PC.
0 Comments
Leave a Reply. |