I_am_dumb wrote:Gil_Hamilton wrote:You're twisting my words around to make it sound like I'm saying people HAVE to use GlovePIE. On the contrary, I'm saying something simpler SHOULD exist.
When I wrote that little quip, I was mainly referring to the people on -that- forum. I had a bad impression of you back in the first thread about the first adapter, but afterwards, when you 'came around,' I didn't think you were completely against the concept or shouting me down about it.
My opinion never changed. I'm still sure the product doesn't exist solely because you e-mailed them about it.
And while I am being negative on this ... abomination, I'm glad the other device exists. The Wiimote is a lot of additional overhead if you just want to use the Classic Controller.
The folks replying to the guy's post on Neogaf, on the other hand... it's like they're confused as to why anyone would even want / need such a device when they can just go spend $40 for a Wiimote, $20 for a CC, whatever $ for a BT dongle, and go track down some scripts for Glovepie or whatever and have to go through the resyncing process whenever they want to use it again.
Enthusiasts can be... special.
I'm no exception, though I TRY to rein in my excesses.
GlovePIE is exceptionally special, since it was designed for VR controllers, not standard gamepads. While it's suited for the Wiimote(if a little overkill for it's limited capabilities), for a mostly-standard gamepad it's like bringing a 50mm gatling gun to a pistol duel.
Gil_Hamilton wrote:There's no reason whatsoever there can't just be a run-and-done driver for the Classic Controller Pro. But no one will do it because one side thinks GlovePIE is "good enough" and the other side would rather sell proprietary hardware at ginormous markups than do something sane.
Eh, so long as the adapter doesn't exceed $25, I don't see it as being that big a deal.
And prices drop on their stuff anyway when they see that too few people are buying.
So if it doesn't end up selling well because people can just use non-proprietary BT
dongles, that just means the prices will go lower, which is a benefit and incentive
for all the 'newbs' who would want to buy and use such a device.
Well, I'm somewhat polarized on the issue currently, having gone shopping for a wireless keyboard and mouse and gazing in wonder and disgust at the massive proliferation of proprietary 2.4GHz interfaces.
Bluetooth was supposed to unify us under one common wireless protocol, not result in an economy of scale for devices that can easily be adapted into proprietary RF dongles.
There's no reason everything should need it's own radio dongle. They're ALL using Bluetooth devices with custom ROMs to break proper functionality, and it's outrageous.
It's like if everyone sold devices that used standard USB connectors, but nothing ACTUALLY used standard USB communications, so you had to have a bunch of adapters to plug these devices into.
Gil_Hamilton wrote:Alternatively, Mayflash could treat the Bluetooth transceiver they sell as a "value-added" feature, by making their proprietary dongle -ALSO- work as the Bluetooth transceiver that it is. You're paying for a Bluetooth transceiver no matter how you come at it, it may as well be one that works with ALL Bluetooth accessories. There's simply no excuse for taking a perfectly good interface protocol and wrapping it in a layer of proprietary mess to break it for all but one or two specific devices.
All I know is that the adapters for both the Wii U Pro controller and PS3 controller are meant to convert those devices to be useable as Direct Input HID devices. I don't know how a Wii U Gamepad, a Wiimote, or a 3rd party Wii U Pro controller or a BT earphone piece or whatever the hell else uses Bluetooth, I don't have either adapter yet, and I don't think that other non controller type devices would really conform to whatever software is running to make devices work as Direct Input controllers.
Well, you could implement a two-path setup in the device. Things which are "normal" Bluetooth devices pass through unmolested, while things which are Wii U gamepads get further processed by the device and are presented to the system as a USB HID gamepad.
I seriously doubt they will, which... frustrates me.
Here's to -hoping- though, that they will at least support third party versions of the Wii U and PS3 controllers. I mean if those things also trick the consoles into thinking they're the real deal, surely it would behave the same way with the adapter. (But then again, when I tried to hook a Nyko Wing to the wireless adapter for the non-U Wii controllers, the buttons in Windows Gamepad Setup screen just went all red but yet that controller is reported to work fine on an actual Wii (though it's also reported to stop functioning if the user tries to load the Homebrew Channel.)
Ahhh... were you trying to connect the Wing DIRECTLY to this adapter? Because the Wing wasn't designed to talk directly to a host system.
It communicates with a dongle that attaches to a Wiimote, so it is functionally the same as a Classic Controller(tm), right down to needing a host Wiimote. I wouldn't expect it to reliably connect to anything but it's own dongle.
Unless Nyko redesigned it to be a standalone device after I bought mine. In which case I hope they fixed the d-pad too. Mine was... sub-optimal.
