Ps3 Controller Pcsx2 Mac Files

Hi all I have an issue regarding my PS3 Dualshock 3 Sixaxis controller and Desmume. My controller is randomly pressing buttons by itself while I play. It has worked perfectly fine for over two years and suddenly it just began acting up. Games are now unplayable and my Nintendo DS is no longer functioning. The main issue is with the pointer (A) button which keeps pressing even though I am not touching the controller. It cannot be the controller as it works perfectly fine in another emulator.

I am running Desmume on Mac OS X 10.7.5 and using ver0.9.11. Please help, and thanks.

It's really hard to respond to this because the entire OP is inconsistent with itself. First, the OP says that the controller 'worked perfectly fine for over two years and suddenly it just began acting up', which suggests that this is a controller problem.

And then the OP says that 'it cannot be the controller as it works perfectly fine in another emulator', which suggests that this is a DeSmuME problem rather than a controller problem. I strongly doubt that this is a DeSmuME problem due to the first statement, and I'm pretty sure that the second statement is a case of the failure to troubleshoot the issue correctly.

So with all of that said. First, you need to determine if DeSmuME itself is behaving erratically. Turn off the PS3 controller and use DeSmuME with keyboard input only. Does DeSmuME behave erratically?

I'm pretty sure everything should work fine here, but if DeSmuME does behave erratically, then you've got some serious issues on your hands beyond DeSmuME not working. And then, there is the possibility that the Bluetooth connection in either the PS3 controller or in the Mac itself could be the culprit. Have you tried disabling the wireless on the PS3 controller and plugging into the USB port directly? Does DeSmuME behave erratically when the PS3 controller is plugged in? If so, then your PS3 controller is absolutely the culprit, and you should replace it with a properly working one. Hi all Thanks so much for the replies.

I am not entirely sure what the issue could be, I am just providing the facts of the issue I am facing zeromus. I am no developer, I am actually an accountant.

Pcsx2 Ps3 Controller Plugin Download

Anyway, thanks for the information rogerman, I will try your suggestions and get back to you as soon as I can. As I have stated in the OP, I have been using Desmume since 2014, when my DS gave in. I have not had this problem before, and suddenly this past weekend when I started playing a new game it started doing this.

I then upgraded Desmume from 0.9.10 to 0.9.11 thnking it could be due to the old version, but the problem persisted. I ran a different game that used to work fine in Desmume, but the issue persisted there. I then ran another emulator (not sure if we are allowed to mention names of other emulators here), and it worked fine, on the same machine with the same controller connected in the exact same way, hence I deduced that it would have to be a Desmume issue right, seeing that it cannot be the controller as it worked fine in the other emulator? Apologies if it seems to some as though I am claiming to know everything about these things, I do not. Thanks in advance.

I then upgraded Desmume from 0.9.10 to 0.9.11 thnking it could be due to the old version There was an internal change between v0.9.10 and v0.9.11 with how hatswitch inputs work, and PS3 controllers just so happen to use hatswitch inputs. This means you will need to remove all of the existing PS3 controller bindings in your DeSmuME Input Preferences and rebind all of them to ensure that everything works in v0.9.11.

Also, v0.9.10 has some critical bugs in it and should never be used in the vast majority of situations. Always use v0.9.11 for your casual use. Hi again With regards to your suggestions rogerman, I have removed all input settings for the PS3 controller and the issue still prevails. I have also connected the controller via the USB cable (not Bluetooth) and the issue still prevails. I do not understand why this issue is occurring because if I connect the controller in the exact same way it works fine in PCSX and in PCSX2 on Mac OS X and on Windows 7 respectively, so the only logical explanation is an issue with Desmume and the controller, perhaps they just do not like each other anymore. Any other suggestions would be greatly appreciated.

With regards to your suggestions rogerman, I have removed all input settings for the PS3 controller and the issue still prevails. I have also connected the controller via the USB cable (not Bluetooth) and the issue still prevails. Let me make sure I'm understanding this statement correctly: 1.

You have the PS3 controller plugged into the USB port. In Mac DeSmuME, you have removed ALL of the input mappings for the PS3 controller. The issue, which is the random registering of NDS button presses in Mac DeSmuME, does occur when the PS3 controller is plugged in via USB and when all input mappings for the PS3 controller are removed. The issue does not occur when the PS3 controller is completely turned off. If I am understanding you correctly, then this problem is either one of two things: 1. You have some third-party software installed that is affecting the PS3 controller, which is then interfering with DeSmuME's ability to read the PS3 controller properly. Usually this happens with keyboard/mouse emulation drivers, such as USB Overdrive, ControllerMate, or Enjoyable.

Mac DeSmuME has no need for any third-party input drivers in order to work correctly since Mac DeSmuME can handle reading input devices by itself, so you should disable these before use Mac DeSmuME. Your PS3 controller truly is broken somehow, and if I am understanding you correctly, then I am 100% certain of this now. Mac DeSmuME uses a very sophisticated and rich input handling system that directly uses HID, while PCSX and PCSX2 both use a very simplistic input handling system based on SDL.

I'm betting that the reason this issue is being revealed in Mac DeSmuME and not PCSX/PCSX2 is because the input handling system of PCSX/PCSX2 is so simple that they are ignoring some of the PS3 controller's inputs, thus avoiding the issue altogether. Mac DeSmuME can actually read every possible input of an input device, which is why you're seeing the PS3 controller problem here. Another reason I defend Mac DeSmuME is because when I was writing the input handling code, I did a lot of testing on the PS3 Sixaxis controller, to the point where I even included a PS3 controller specific hack just to make it work that much better. The PS3 controller is actually one of the most tested controllers in Mac DeSmuME, so it is very difficult to see a PS3 controller, which by your own admission worked fine 2 years ago, fail to work in Mac DeSmuME unless the PS3 controller truly is broken.

Hi Thanks for the information rogerman. I do not have any third-party software on my Mac to run the PS3 controller, so it would have to be issue two.

It would seem as though my only options are to purchase another controller or to use the keyboard, and it will have to be the latter as I do not have cash right now. From your explanation it would seem that Desmume works too well for it's own good. Just a final question, would reverting to a previous version of Desmume possibly solve the issue? Mac DeSmuME is the only port that fully supports all analog inputs, for which the PS3 Sixaxis pointer is one of them.

Configure Ps3 Controller Pcsx2

Analog inputs are essentially useless for all NDS controls except for one - the Taito Paddle Controller. There are some games that use the Taito Paddle Controller, such as the Space Invaders Extreme series of games. If you can emulate the Taito Paddle Controller in its native analog mode using an analog input, this setup becomes a MAJOR advantage in these games. I've been able to get my hands on a friend's PS3 controller for testing, and everything seems to work just fine for me. So in light of these recent tests, it even further cements my conclusion that your particular PS3 controller is broken somehow.

Reverting to a previous version of DeSmuME would NOT solve this issue. More likely, you would experience even more bugs than v0.9.11, since there have been some important bug fixes and enhancements to the input handling system with each Mac DeSmuME release.

Table of Contents. About PCSX2 PCSX2 is a free and open-source PlayStation 2 emulator for Windows, Linux and OS X and currently the only known Playstation 2 emulator capable of running commercial games. PCSX2, like its predecessor project PCSX (a PlayStation emulator), is based on a PSEmu Pro spec plug-in architecture, separating several functions from the core emulator. These are the graphics, audio, input controls, CD/DVD drive, and USB and FireWire (i.LINK) ports. Different plug-ins may produce different results in both compatibility and performance.

Additionally, PCSX2 requires a copy of the PS2 BIOS, which is not available for download from the developers, due to the copyright concerns and legal issues associated with it. At present, PCSX2 is not compatible with PlayStation games. PSX games can be played by using GSDX with a PlayStation emulator such as PCSX or ePSXe. The main bottleneck in PS2 emulation is emulating the multi-processor PS2 on the PC x86 architecture. Although each processor can be emulated well on its own, accurately synchronizing them is very difficult.

Source: Configuration File Locations.retrorig/.config/pcsx2.retrorig/.config/pcsx2/inis BIOS Files (required component) PXSX2 requires a BIOS be placed in the proper location to function properly. In the current version used by RetroRig (SVN, 1.3.0.0), this typically is one file, but I have been told in IRC at times, newer versions may require sets of files or archives.

The RetroRig/BIOS/PCSX2 directory is symlinked to the config directory of PCSX2 so you don't have to remember to place them in the typical /.retrorig/.config/pcsx2/bios directory, and use the structured /RetroRig/BIOS folders. There are currently two ways to load BIOS files:. Use the main setup file, retrorigsetup.sh you used to install RetroRig, under RetroRig Settings BIOS Loader. This function is needed, due to PCSX2's configuration file explicity needing the exact file name specified, in contrast to Mednafen expecting the file based on the ROM you are using. Use the RetroRig Settings menu from the main XBMC window (beta only at the moment).

Navigate to Emulator Settings PCSX2. The emulator will launch, which you can then use to select your BIOS file in it's BIOS/Plugin selector.

BIOS files will not be provided. Please do not ask for them. System Requirements Known minimum system requirements encountered during testing include:.

Capable Linux OS 1. CPU that supports SSE2 (Pentium 4 and up, Athlon64 and up). GPU that supports Pixel Shaders 2.0. 512mb RAM.

(Quite possibly) For Nvidia and AMD Graphics cards: Non-open source drivers 2 Recommended. CPU: Intel Core 2 Duo @ 3.2ghz or better. GPU: 8600gt or better. 1gb RAM Maintainer Notes: 1 This is subjective, most major distros will be fine, but the most popular distros should suffice.

2 One thing I noticed during testing, is PCSX2 seemed to fail to run a game whatsoever when using am Nvidia graphics card, and the nouveau driver. In this sense, until confirmed by other testers and users, the suggestion will remain to use the proprietary drivers with graphics cards. Default Settings There are number of tweaks I have made to PCSX2, and they will always be up for debate. Trying to find a good middle ground on hardware support and the game looking good is always a priority. Graphics (standard settings). Renderer: OpenGL.

Interlacing: Auto. OpenGL Internal Resolution: Custom Scaling (system resolution).

Fxaa shader: enabled. Shade boost: enabled (150, 50, 50). Texture Filtering: On. Alpha Correction (FBA): enabled. Edge anti-aliasing (AA1): enabled Running Games with PCSX2 Under RetroRig It was quite an ordeal to find a cohesive solution to making PCSX2 gamepad-friendly and workable under RetroRig. The general process involves. Copying the proper ini files as usual.

Including the utility antimicro (compiled form source) to handle modifier keys. Juggling the proper key sequence to properly close PCSX2's main GUI window, due to the -nogui option ever exiting properly form a console launch. Antimicro You can review the below example files (PS3 Bluetooth) to see how antimicro is involed:. A comment in the controller mapping file denotes the SDL name is just for information purposes.

Use Ps3 Controller On Pcsx2

Until further notice, this should mean that there is no need to swap out the MAC address. Further evidence of this is noted by when two controllers are connected to AntiMicro, there is no change to the file or two MAC ID's displayed. AntiMicro will launch in a hidden mode when you launch a PS2 game. When you exit the PS2 game with RCB, Anti Micro performs a ESC + CTRL + Q key sequence wich exits the game ( Esc), and then the PCSX2 window ( CTRL + Q).

This was deemed the most workable and safe solution. The PCSX2 will hover for about 1-2 seconds after exitint the game. I could not find a way to reduce this lag. Troubleshooting There are a number of things to try and get more stable or perfect playback. Due to this emulator just being recently added, scenarios and fixes will show up here over time.

Please consider beta testing RetroRig for us to help identify game compatibility. I get gridlines on my game(s)!!! In testing, games such as Mega Man X Collection and Metal Slug Anthology gave me this issue as well.

Try these settings to correct your gridlines:. While the game is launched in RetroRig, perform Alt+ TAB and select PCSX2. System Pause. Config Video (GS) Plugin Settings.

Texture Filtering set to Off Known games to have issues with PCSX2. Metal Slug 6 does not work.