Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

25 Excellent

1 Follower

About Chadmando

  • Rank
    16-Bit Artificial Intelligence

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You're welcome. It took my a while to get my set up just right, hopefully this will save you $$$ for dongles and accessories as well as hours worth of struggling like I did.
  2. Hello, you are correct you will need two different bluetooth adapters, or else windows cannot decide which it wants to use for it's bluetooth driver, and they will conflict with each other. I am using the Kinivo BTD-400 Bluetooth 4.0 Low Energy USB Adapter for PS3 controllers ( BCM20702A0 chipset) https://www.amazon.com/gp/product/B007Q45EF4/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 Windows will try and fail to install the drivers for this device (because windows can only use one bt driver) at a time. You will use the Zadig program to change the drivers for this device into a libusbk device, https://zadig.akeo.ie/ I believe it is also available in the scptoolkit package, and part of the installation instructions that come with it. I followed the ps3 controllers instructions section of this website to setup pcsx2 and scptoolkit https://1upsdevelopment.com/pcsx2-socom-2-xlink/#settinguppcsx2 Yes pressure sensitive buttons work with this method (for PCSX2) an extra added bonus is that when PCSX2 is not in use it will work just like an ordinary Xbox one controller. Once everything is setup all you have to do is turn on your wireless ps3 controller as normal and it should auto connect every time (unless you synced it to something else of course). After everything is installed I manually disabled windows from being able to try and update this driver, because a windows update messed it up for me once. Used this tutorial https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/ For my normal everyday xinput (as well as I use with 8bitdo using their Xinput modes) I am using my default one that comes with my motherboard (bluetooth 4.0) with my rampage V extreme. I can connect up to four (maybe more?) xinput devices at once with no issues with this adapter. After programing all my 8bitdo controllers to use Xinput mode, all I have to do is turn on any controller, xbox, ps3, 8 bitdo and windows will assign that controller to the controller number in the order it was turned on just like all the modern console do. I also took the extra step of swapping the 8bitdo button assignment around to match so all the controllers feel the same on each emulator (via the instructions provided with 8bito controllers).
  3. One last thing I did was I changed the name of the folder autohey.exe was in
  4. I believe this is a scaling and or dpi issue. I had this issue with my pause screen menu program, It took a lot of work to fix it so the menu would automatically adjust. Is your font settings for you computer larger than 100%? If so try setting it back to 100% and see if that helps.
  5. If you download the Hex editor I linked to open up the autohotkey.exe file with it. Go to the top of the tool bar SEARCH >Find in the search field Search for: AutoHotkey V choose the text encoding: Unicode. You will see the window text in the "Decoded text" field seperated by dots. Change each letter of "AutoHotkey", make sure you don't add any extra characters, or delete any characters, just replace them with random letters.
  6. I have 6 of their mod kits, the adapter acts just like if it was plugged in, I imagine it would act the same way as all other plug in controllers (the slot is powered on 24/7). I chose to use my built in Bluetooth for them instead. I use XINPUT mode for all of them (the manual tells you how to set them up for this, you only need to do this once for every controller). Windows will the assign the player order sequentially as you turn them on. All you need to do is set up your emulators controllers settings to use XINPUT instead of dinput. Using this method is similar to how all the consoles these days handles wireless controllers. I highly reccommend thus setup, it's pretty well hassle free. If the hori pad can use xinput mode then you're set. It should always remain player one if it's always plugged in.
  7. I was just wondering if there's a temp file created or something where I can get the currently running game, Emulator, etc? I noticed everything in the xml files are organized nicely with game id, emulator number etc. If I could retrieve those numbers I should be able to easily parse through the files to get all the information I need from them.
  8. I never changed or compiled the scripts. Although I bet if you compiled a script instead of using a hex editor you may bypass it in the same way.
  9. I think I used this one here: https://mh-nexus.de/en/hxd/ When using it search AHK's title bar name.
  10. Just adding a little bump here to announce my new updates! I edited the top post with the new download and update information.
  11. So simple, yes this worked thanks!
  12. Launchbox and bigbox suddenly won't open, I haven't added any plugins or anything since the last time. Possible that the update came up and my 5 year old clicked on update without the admin password and messed it up that way. I think I have had this issue before can't remember what I did to fix it.
  13. I am first going to focus on allowing the user to create their own sub menus with the settings program (Like insert a coin for player 1-4 in mame, sync a wii remote for dolphin, etc). I will then look at adding artwork, manuals, controller layouts,etc. If I can get the running game information somehow from launchbox I think it would fairly easy do.
  14. I just released a new version that includes a settings file for retroarch. Please check the top post again with the updated file and installation information.
  • Create New...