Jump to content
LaunchBox Community Forums

Chumpalot

Members
  • Posts

    19
  • Joined

  • Last visited

Chumpalot's Achievements

8-Bit Processor

8-Bit Processor (3/7)

3

Reputation

  1. A little update. I paired a Sony Dualshock 4 controller via Bluetooth to my PC using the same dongle used for the 8Bitdo controller and both controllers are being assigned as player 1. I'm not quite sure how to get round this. I have tried switching both on and off when the other is one etc. , re-pairing, and different USB slots. I'm not quite sure what else to try. For all intents and purposes things work fine. All of the inputs are picked up on both controllers meaning MAME at least picks up player 2 inputs and some good Street Fighter action can be had. I'd just like it if they were identified by Windows as P1 and P2 that's all. I had a quick look to see if there was a way you could hard-code the assignment but I haven't come across anything yet. If i add the Xbox controller into the mix all pads are still assigned P1 status. Meh. If anyone could shed any light that would be great. Cheers Chumpalot. edit: so I cam across this: ----------------------------------------- Firstly, there's a paired device and a connected device and then an actively communicatingdevice. Your links above confuse these and no distinction, but there is a difference in functionality. A device can be paired, but not connected. Similarly, it can be connected but not transmitting. Think of a paired device as a saved wireless network that you're not connected to. -------------------------------------- From looking at my list of Bluetooth devices in windows, it seems that the 8bitdo controller falls into the first category, the PS4 controller looks like its the second category and then the Xbox pad is using the proprietary wireless network. With all that in mind, if all three devices are using different ways of connecting then I can understand why they're all being seen as player 1. Or maybe I'm making things more complicated than they should be.
  2. Evening all, I'm having an issue whereby both my 8bitdo SNES bluetooth controller and my Xbox 360 wireless pad are both being seen by the OS and emulators as player 1. I have tried resyncing the Xbox pad whilst the SNES pad is connected but it just assigns to P1. Everything else I have tried has been unsuccessful. I think I know why this happens but grateful if someone could confirm and let me know if there's a workaround. I believe this is happening because the two devices are using different connection methods (bluetooth and proprietary wireless). Is this the case? If I were to swap out the 360 pad for a PS4 pad would this resolve the issue? Both pads would be using the BT dongle and hopefully play nicely together. I would like the ability to pick up a different pad depending on the game I'm playing (SNES pad for older titles and newer pad for newer stuff). Sorry for waffling. It's late and I've been transferring a shed load of roms and updating Launchbox. Cheers Chumpalot.
  3. Messing with the per-game overrides was on my list of things to do. Thank you.
  4. Ah. This had given me a headache when trying to play Metal Gear Solid. The analog controls weren't working and I had to switch to Dualshock. I then noticed that another game (Final Fantasy 7) was completely unresponsive to all controls and so had to switch it back. Glad you got it sorted. Anyone know if there is a way to get around having to manually change this setting per game? Cheers.
  5. Youll need to check in the core options also. Load up a PSX game and bring up the retroarch menu. Check the settings under Options. These are core speciifc settings.
  6. Update: I bought one of these from Amazon and after wrestling wirh disabling the onboard bluetooth and installing the new USB adapter I finally managed to get it working. You don't need the files on the mini CD provided. Windows 10 should just pick it up. I must say it works great and response seems to be very good. Street Fighter is a different game altogether compared to using the Xbox 360 d-pad. Hopefully this helps others who are having issues with this gamepad and their onboard Bluetooth. Cheers. edit: fixed the link
  7. Thanks for the suggestions and for posting those screenshots. The controller came with the latest firmware but it completed the update anyway. Still no joy. I'll get a dongle from Amazon and see how it goes. Thanks again.
  8. I think the issue is definitely to do with the motherboard. Would you mind telling me what bluetooth adapter you're using please?
  9. Hi all, I had the above controller delivered yesterday. Got really excited only to find out Windows doesn't see it at all over Bluetooth. If I connect via USB all is good (Street Fighter II is amazing) but I can't get it to work via BT. I've tried starting the gamepad with both DInput and Xinput. The Bluetooth module on the motherboard is 4.0 compatible and it can see other devices nearby such as my TV and Sonos speaker. I tried connecting the SF30 to my Macbook and it recognises it and pairs straight away, no problem. Thought I'd see if anyone had any similar issues before I go ahead and order a bluetooth adapter. My motherboard is a MSI Z97i Gaming ACK. I have the latest drivers are installed (although they're from late 2016...) Cheers Chumpalot.
  10. Excellent. Looks like I'm using the best one anyway. Thanks.
  11. Thank you for this. I thought I had things set up quite well but it seems I can squeeze a little bit more out of it using some of the settings above. Is Glupen64 still the emulator of choice for the N64? I'm currently using Mupen64 and whilst things aren't perfect games are absolutely playable. Cheers.
  12. From doing a little bit of research there are two methods: - have seperate instances of Cemu to run games that require bespoke configurations. - use the batch file method of moving configs files etc Neither I find very attractive so I guess this is something that will just have to be swallowed. Cheers.
  13. Thought I'd throw in my thoughts here as a newbie to emulation. I've not been on the scene that long. For no particular reason I ended up starting off with an older version of Retroarch. I found it a little cumbersome and there was no way to automatically find and download cores. I quickly discovered the latest version and haven't looked back. Emulating Sega Mega Drive, SNES, NES and PSX games is so easy and it is absolutely seamless with LB. Once you get things set up you won't look back. I quickly found myself playing old games such as Alien Storm and Altered Beast and having an absolute blast. As for the standalone emulators, CEMU is pretty much the one to use for Wii-U and PCSX2 for anything PS2 related. MAME for your arcade stuff and Demul for Dreamcast emulation. All of these I have found to work very well when using LB as a main frontend. As Retro808 said you might want to enter some custom parameters to hide some emulator GUIs and save resources when the game loads. CEMU for example requires a '-f -g' parameter to get games running and at fullscreen. Apart from that setup for the most part is a breeze. My main issues so far have come from getting the emulators themselves to behave how I want them.
  14. Actually I have just discovered that my motherboard, a Z97 MSI Gaming ACK supports Bluetooth 4.1 so I'm hoping it works out of the box. If you could let me know what Bluetooth adapter you're using all the same that would be great though. Cheers.
  15. Thank you for this. I have just ordered a SF30Pro from Amazon. It's getting delivered tomorrow. I don't yet have a bluetooth receiver, which one do you use? I'll be using this (plus another one if I get on with it) along with an Xbox 360 wireless pad which has been great. It's only letdown is the d-pad which has prompted the purchase of the SF30 I guess. Cheers.
×
×
  • Create New...