For the issue regarding the controller needing a PIN number, I could not fix it by going to devices and printers, but the code for the controller was just 0000
You can change it in the file "BetterJoyForCemu.exe.config"
The way the driver works, if you're doing combined Joycons then just the first vJoy device will recieve inputs. Make sure the driver is open and running before trying to do stuff with XOutput, and also make sure it actually worked, and your Joycons were paired with the computer before you actually opened the driver in the first place. Just a heads up, I haven't used this software in ages, I don't even use Windows anymore, and linux makes this stuff a non issue, so hopefully this information is accurate.Do I need to set up all the options (in XOutput, for combined joycons) for both of them?
Just copy&paste the same settings into both of the joycons?
I'm pretty late to the party here, but I do think split joycons are the most comfortable controller out there, so I figured I'd try using them for PC games instead of the 360 controller. To be worthwhile, I would need to get them working as a single controller, have true analog sticks, and have no significant input lag. So far, I've seen enough to make me believe that maybe it could work, but not enough to make it actually work. Have you all found this to be practically usable?
One definite problem is probably my hardware. I can connect the joycons to bluetooth, but they frequently disconnect. And I was sitting right next to the PC, when I'd normally be a little further away. I'm just using the Intel bluetooth on my motherboard. Would a dongle get a better connection? Any good ones in particular? Could that be the cause of issues like lag even if they're connected?
The VJoy / Xoutput solution hasn't been consistent for me. I've had brief moments when it seemed to work perfectly, but then it will seem like it's dropping inputs or something. I was using the joystick to move the cursor on the Assassin's Creed: Origins menu, and it was kind of flashing rather than moving smoothly. But honestly, the connection issues made it hard to test, since I might drop a connection to one or both joycons at any time.
Sometimes I'll also end up with just one Joycon working as a single controller. (I have to turn it on its side for the directions to make sense.) I'm not sure what is even making that work. Maybe Windows 10 just figured it out. I have noticed that XOutput will list two wireless gamepads in addition to two vJoy devices. I disabled everything but the first vJoy device in XOutput, but I do worry about some sort of conflict if Windows is treating it as one type of controller and vJoy/XOutput as another.
I also tried BetterJoyForCemu. In most ways this actually worked the best. It worked for a good while as a single controller, and all the buttons and the analog input seemed to work. Just one massive caveat--the input lag made it completely unplayable.
I'd love to get this working, so any pointers would be much appreciated.
Please do, I'm not very tech savvy and I've been working for hours trying to get this to run properly. Either that or an updated video on this would be much appreciated!An installer will come out that combines vJoy, XOutput, and the driver itself into one package, heck if I knew how to make installers I could whip something up. One thing I could do is make a little batch script to load everything at once, would require putting everything in the same folder though.
Update: It's working! The only thing I can't figure out is the shake. I've been trying it out on Rocket League and, it may just be the game, the controller vibration hasn't worked at all. Does anyone have a fix for this?Please do, I'm not very tech savvy and I've been working for hours trying to get this to run properly. Either that or an updated video on this would be much appreciated!