v0.4.1.4 Small tweaks to underlying code, using new features of AHK

I changed the way the input is grabbed by the keylist helper part of the program. This should be more efficient and even though this isn't a big part of the program still wanted to update the code.

Also updated the code for button presses and releases to use the new Switch ability in AHK. This only does the variable evaluation once, instead of multiple times. Since there are only a few options anyway it may not save a lot of time, but again as above I feel its always better to update code if possible.

Since I was modifying the code I took the chance to add the ability to map buttons to the mouse wheel. If BotWmouseWheel option is enabled, you can't map Up and Down.

WheelDown
WheelUp
WheelLeft
WheelRight

These work as a single key presses (you can't use them to hold down a key) because the wheel doesn't fire an "UP" keystroke like all the others. I decided to just make it automatically depress the button 100ms after it was pressed, which seems to work well in my tests.

Please let me know if there are any issues that I created, or haven't fixed yet.

0.4.1.3

Added ability to save settings without closing them.

Hopefully fixed controller profiles for Pro controller.

I also uncompressed the exe, so it will be larger now (1.12 MB) but should hopefully no longer be flagged as a false positive by anti-virus.

Some very minor changes.

I've not done a lot of updates to this program in a very long time, however this version was sitting in source code for awhile without being released.

Bug Fix: I added the '=' key to the forbidden keys to be mapped, this was causing issues since the list is stored in an ini file.

Known Issues?: I've noticed that the controller profiles for the PRO controller don't appear to be working very well, so please try using the GamePad profile instead. I will try to figure out why this has changed and update with new controller profiles when I do.

New: Added ability to change walking speed on the fly, so if you toggle walk mode you can then fine tune your speed using the set keys, defaults are pictured here

I will attempt to answer questions related to this project again, if I have the time

Saved Key List Manager!! and Complete Settings Re-Write

• Added ability to save keylists, in pretty much the exact way CEMU lets you manage Controller Profiles
• Completely re-wrote settings code
  • Allows me to more easily manage adding and/or changing the settings for the script
• From this version on, 64bit is required, this shouldn't' be an issue since CEMU already has that requirement.
• Updated included ScpVBus, as the version I had was outdated, and probably 32bit.

I highly recommend deleting your settings.ini file when upgrading to this version. Things have moved, and one section changed names ever so slightly. The way this works shouldn't cause any actual issues, but still the file will be cleaner if you: make note your settings -> delete the file -> launch the script -> re-input your changes.

CEMU Version 1.11.0

• The changelog says:
  • input: Deadzone is normalized correctly now and should be the same for xinput and directinput devices

I'm hoping this means that the Direct Input issue is fixed, I admit I no longer have access to the Patreon Builds so haven't tested, but am hopeful.

This means there is almost no need to use the vXBox option anymore for CEMU. However, there is also no reason to remove the option, and it allows the script to be used for other programs that can use XInput (PlayStation Now, rpcs3, etc..)

---

As always please let me know if you run into any issues, either here on GitHub, a PM on Reddit ( Since my post is archived ), or on my post on the official forum.

vXBox is now a main settings option.

I've updated the guide in the README and on my forum and Reddit post.

Relevant part is here as well.

1. Install the latest vJoy
2. Run the vJoy Configuration (Not necessary if you only plan on using vXBox)
   • Set it up so it has at least 18 Buttons, I set mine to 32.
3. Download controller profiles for CEMU > 1.9.0      (Also included in GitHub release zip)
   • Extract these text files into your CEMU controllerProfiles folder
4. Then open CEMU and goto the input settings
   • Choose the type of controller you want to use, either 'Wii U Pro Controller' or 'Wii U GamePad'
   • If using standard vJoy Device
     • Choose DirectInput for the Controller API
     • Make sure to choose the device as vJoy Device and confirm it says connected
   • If using vXBox Device
     • Run the script FIRST and choose 'Use vXBox Device' on the General Page of settings
       • If this is the first time you will be prompted to Install ScpVBus, choose yes, then yes again on the security prompt to run DevCon
       • Script will reload and if the message box doesn't show up again you should be ready to use vXBox.
     • Choose XInput for the Controller API
     • Make sure to choose a controller and confirm it says connected (May need to press refresh for Controller to show up)
       • If it doesn't say connected try switching the vXBox device number in the script settings one of them WILL say connected in CEMU (this seems to be a CEMU quirk as other applications don't care which vXBox device is selected it will always grab the active one)
   • Not sure if necessary but Press Calibrate
   • Choose the appropriate Profile for the type of controller you are setting up.
   • Click Load

 

v0.3.2.1 - Added what buttons are ✕, ○, ⬜, △ in the keylist helper when vXBox is active. This helps with people who are using this for things like rpcs3 and 'Playstation Now' instead of CEMU.

Added vXbox Support as a Hidden Advanced Option w/ Other improvements

New in Version 0.3.0.0 of the script.

You can now alternatively have the script use a virtual XBox controller instead of DInput, this eliminates the deadzone issue as it isn't present for XInput devices. Or instead enable BotW motion aim (granted this is only a specific game fix instead of a general fix)

• Make sure you've downloaded the latest version of the script (at least version listed above)
• Open your settings.ini file and either create or change the value of your chosen option to a 1.
  • usevXBox=1 OR BotWmotionAim=1
  • The BotW motion aim does nothing when using vXbox
• After enabling either feature reload the script
  • Either re-run, or right click the icon and choose reload from the menu
• If it is the first time you are running the script using vXBox it will most likely need to install ScpVBus
  • A Message Box will pop up
    • if you press yes a prompt to run Devcon will appear, press yes
    • If you press no, vXBox will be disabled for this run
  • The script will reload and if successful the message box will not re-appear.
  • Set up CEMU input settings similar to the guide at the top except
    • Pick XInput
    • Choose the virtual XBox controller
    • Load the appropriate vXBox controller profile for your chosen controller type (included in the download)

I will work on advancing this option, and once ready I will add it to the Settings GUI, and re-make the main guide for the option, for now I am considering it an Advanced (hidden) option, and will expect users to know a bit about what they are doing with my script. That doesn't mean I won't support users trying this feature out, but I will most likely ask for steps already attempted.

---

Controller Profiles have been added for vBox_Pro and vXBox_GamePad, as well as updating the axis assignment, so please update your CEMU input settings when upgrading to this version of the script. (Or alternatively remap your move up/down keys, and change the inverted axis option in settings)

---

v0.3.0.1 Fixed a error caused by having an AND where there should've been an OR

v0.3.1.0 Re-Added invisible overlay window as it apparently was doing more than just hiding the cursor.

Biggest change was an update to the guide/readme

There weren't many code changes in this version.

• Added ability to customize the Mouse check frequency
  • My thought for this would be it would help for some people who feel there is a delay when moving or stopping the mouse.
• Added ability to assign more than one key to the same vJoy Button
  • This can only be done by manually changing the KeyList string
    • It is accomplished by appending extra keys with the | symbol
      • XButton1|e in the list would set Mouse4 and e to the same vJoy button

Notes for 1.9.1

• There is some built-in Deadzone in CEMU that even when set 0 is still present (around 10% it seems)
  • This causes the camera movement to be jerky, and precise aiming is a giant pain
• The Deadzone sliders are reversed under the sticks, meaning the left slider affects the camera instead of the right one
  • This is un-intuitive and a bug most likely.

Currently the best settings I've found to HELP alleviate the issue is as pictured here.

Hopefully in 1.9.1 this will be resolved.

Built-In Keylist Helper

Note for CEMU > 1.9.0

There is a new folder called controllerProfiles in the directory of Cemu.exe now. If you put these text files in you should be able Load the vJoy layouts directly, hopefully it works on machines other than mine.

Download controller profiles for CEMU > 1.9.0

I will make a new release once 1.9.0 is public and I can test things myself - this is in progress.

 

---

I've added a built-in KeyList Helper, this is a much more streamlined solution vs. having to use an Excel file, or memory, to map your keys properly.

 

You can change your key mappings by following these instructions:

• You goto the KeyList page and press the KeyList Helper Button located on Mouse2JoyStick>Keys page
• You will then see an updated version of this screen come up, I've done my best to make it look like CEMU's Input settings so it should look familiar.
  • Example of Manually Clicking Through
  • Example of Auto Cycling Through
• When you click save you will see the KeyList string update itself with any changes you've made.

That's it, when you click OK on the main settings screen, your keys are now mapped how you have set.

• Note you can still keep KeyList strings for different games saved to a text file locally and just paste it in (like it used to have to be done)
  • I may even consider keeping an array of game layouts internally (No promises though)

This was quite a large addition to the code, so far in my testing I have not come across anything that broke, and honestly nothing should've, but please let me know if you find anything that isn't working as it was.

 

Since there are no Extras anymore, other than the layouts, I'm only attaching the EXE and the layouts zip. If you want the script, download the source code, the layouts are included there as well in a folder.

 

Small Changes:

• BugFix: LButton wasn't working as a key
• Added some fail safes when auto-cycling the KeyHelper to try and prevent strange behavior if the window closes during the process.

Gyro without disabling script has been added.

• I've added a key you can hold to work the gyro without first disabling the script. Pressing any other key or releasing the key will cancel the control.
  • I've set this to be the v key by default but you can also change it under the 'KeyboardMovement>Keys' settings page.
  • Currently the mouse isn't hidden during this process, but I may re-implement my old method for hiding the cursor to fix that, or I may not as it is a good indicator that it is working.
• The icon used for the tray has changed number within the Windows dll for new versions of Windows, I've added code to try and pick the right icon based on windows version, but haven't tested on any machine but mine yet.

 

That is basically it for this update, please let me know on reddit, or here I guess, if you have any problems, or requests.

First Release of All-In-One script

I've combined all the versions I used to try and maintain into one script. This comes with several efficiency updates, as well as a settings overhaul.

The different features can be toggled on or off on the Extra Settings Page.

I believe this change will help me to maintain the script and add features. I should also be able to provide better support since I only have one script to worry about, and I've added my own version internally that I can ask for.

Please still feel free to PM me on reddit, or ask in the comments of my post for help.

 

Future Plan

• Add ability to generate KeyList inside the program, removing the KeyHelper file, and streamlining the process.