Now working: FORCED w/ Wiimotes, x360ce, GlovePIE / FreePIE, PPJoy

[rainwalker]

After MONTHS of being unable to play FORCED with my Wiimotes, I think I've finally figured out the culprit: my 64-bit Windows 7 system.

UPDATE: In spite of what’s written below, I can confirm that deleting my local FORCED game content and reinstalling it to the /Program Files (x86)/ directory does NOT, in fact, fix my Wiimote connection problem. Although 99% of the information below will likely work, for you, as far as I can tell right now, you will still need to be on a 32-bit Windows install to make FORCED work with your Wiimotes.


Since I store my Steam games on a separate HDD than my OS, I had been installing all Steam games into S:/Program Files/Steam, instead of S:/Program Files (x86)/Steam. I don't know if adding "(x86)" to the file path would change things (any Windows savvy folk, out there?), but I do know that attempting to run FORCED on an alternate 32-bit Windows 7 system finally allowed me to use my Wiimotes. Here is my short guide to using FORCED (and possibly other non-working games) with your Wiimotes:

1) Enable Test Mode (http://www.queryadmin.com/147/enable-disable-windows-7-test-mode/)

2) Install your game on EITHER a Windows 32-bit system or into C:/Program Files (x86)/ on a Windows 64-bit system.

3) Install PPJoy and configure as many joysticks as you plan to use. My configuration for a single controller can be seen, here: http://imgur.com/RJuG3po

4) Download GlovePIE or FreePIE. I am more experienced with GlovePIE so I'll use that. Download an place this .PIE script somewhere you can find it: https://github.com/lewispgj/GlovePIE/blob/master/Wiimote-Nunchuk-Triple-Axis

5) Download x360ce. This part is kind of painful. Some people recommend using an older version of x360ce, since the new version appears to not work as well with some systems. For me, the old version does not work at all. Try your luck with both. We'll configure x360ce in a bit. For now, place x360ce and any associated files in your FORCED directory (C:\Program Files (x86)\Steam\steamapps\common\FORCED).

6) Reboot.

==============
To connect & play:
==============

1) Open GlovePIE, open your PIE script, then go to step 2.

2) Open your Bluetooth config and add a new device. Press 1 + 2 on your wiimote until the lights start blinking. Tell it to pair without a passcode. Your wiimote lights must be blinking through this entire process; if they’ve stopped, it may already be too late (in which case you should remove the new Bluetooth device and re-add it), otherwise you can usually just hit 1 + 2 to get them blinking, again. Anyway, once your comp says that the new device has been successfully installed, you should IMMEDIATELY go to GlovePIE and hit “Run”, then hit “Stop”, then hit “Run”, again (also be sure that “No Bluetooth auto-connect” is selected in the Troubleshoot menu). I don’t know why I/you have to do this twice, but it doesn’t work for me if I don’t. If it worked, the wiimote lights should light up and stay solidly lit; if it didn’t, you can probably still press 1 + 2 and it will start blinking, again, which is a sure sign that it hasn’t worked.

3) REMEMBER: IF YOU DIDN’T ADD THE WIIMOTE VIA BLUETOOTH AND START/STOP/START YOUR SCRIPT IN GLOVEPIE, ALL IN THE SPAN OF TIME STARTING FROM YOUR FIRST PRESS OF 1+2 GOING UNTIL THEY STOP BLINKING FOR THE FIRST TIME, THERE IS A GOOD CHANCE THIS WILL FAIL. YOU HAVE TO BE FAST! If your wiimote is now connected and showing solid lights, you may proceed.

3.5) You have to repeat the above procedure for each wiimote that you wish to add. Once your first wiimote is connected and running w/ GlovePIE, open GlovePIE and hit "Stop". Then open your bluetooth settings, Add a New Device, hit 1+2 on your next wiimote, before the wiimote lights stop blinking (but after it has been successfully added to/installed in your system) go back to GlovePIE and hit Run/Stop/Run, again. Now you should have two wiimotes connected. Do this for as many as you like.

4) Go to your FORCED directory and open x360ce. It should spawn a message indicating that it has found a PPJoy controller and would like to download settings for it, from the internet. Sure, go ahead and let it. If x360ce is not detecting your Wiimote(s) and you’re fairly confident that you’ve got PPJoy and all else configured correctly, you’ve got a more specific problem and you’ll have to remedy that before you can move on. Once the program detects your wiimotes, you can configure the buttons (which will correspond to PPJoy buttons) and settings, like I have: http://imgur.com/VC7KRDK

4.5) Additionally, you'll need to enter some identifying information that is specific to each wiimote, using a tool you can download called "ditool". This tool will open a cmd terminal and give you identifying information about your ppjoy joysticks. You need to enter that information into your x360ce.ini file, or else x360ce won't know which devices to talk to. You can model your own file after mine (in fact, you can just copy this file directly, if you've used all of my other files, and simply replace the mappings, productGUID, and instanceGUID with your own settings): https://github.com/lewispgj/INIs/blob/master/x360ce.ini

5) At this point, if I’ve instructed you correctly, you should be able to move your nunchuk stick and press buttons and see them affect the x360ce button-map in real-time. Again, if this isn’t working, something is wrong with your setup and you should backtrack.

6) Close x360ce and start FORCED. Your Wiimote should now be read as an x360 controller.

7) I’ve literally spent weeks troubleshooting this somewhat complicated setup. Therefore, I will very likely not be devoting any more time to this project than this initial post. Ask someone else, if you need further help.