No siree, bios are in place, not getting a message at all. (correctly named, and in the right folder).
any way i can help? (logs and such)
No siree, bios are in place, not getting a message at all. (correctly named, and in the right folder).
any way i can help? (logs and such)
No siree, bios are in place, not getting a message at all. (correctly named, and in the right folder).
any way i can help? (logs and such)[/quote]
Iâll test those games out myself when I have the time I guess.
i am having the same issue with my ipad2 5.1.1. I have my bios placed correctly in .Retroarch and tried every possible sitting. But still every time i load a rom it crashes. Those roms run perfectly on the Android version so it shouldnât be the problem of the roms. I just couldnât figure it out.[/quote]
Permission problems - and also, âOwnerâ and âGroupâ ownership is important to get right (mobile/mobile).
For what itâs worth - here is what a user told me who has having repeated problems trying to get ROMs to work on her iOS device -
Check it out⌠Just fixed the problem. In my documents folder, I have a âromsâ folder with correct permissions. But in that folder are separate folders of PS1, SNES, NES, GBA, etc⌠All with correct permissions. Moved over the ps1 out of the the âPS1â folder to the âromsâ folder and the PS1 games load fine now. However, this is not a problem when loading a game on any of the other cores Iâve tried (SNES, GBA, and Sega).
i am having the same issue with my ipad2 5.1.1. I have my bios placed correctly in .Retroarch and tried every possible sitting. But still every time i load a rom it crashes. Those roms run perfectly on the Android version so it shouldnât be the problem of the roms. I just couldnât figure it out.[/quote]
Permission problems - and also, âOwnerâ and âGroupâ ownership is important to get right (mobile/mobile).
For what itâs worth - here is what a user told me who has having repeated problems trying to get ROMs to work on her iOS device -
Check it out⌠Just fixed the problem. In my documents folder, I have a âromsâ folder with correct permissions. But in that folder are separate folders of PS1, SNES, NES, GBA, etc⌠All with correct permissions. Moved over the ps1 out of the the âPS1â folder to the âromsâ folder and the PS1 games load fine now. However, this is not a problem when loading a game on any of the other cores Iâve tried (SNES, GBA, and Sega).
[/quote] i have changed the permission of every single folder to 0777 and mobile/mobile but it is still crashing when loading roms.
It could be that the permissions of the files inside the folder /Applications/RetroArch.app/modules need to be fixed as well. Try that.
I have constant problems to connect a dualshock 3 controller. Itâs working perfectly fine with SNES9X EX+, but with RetroArch it sticks at blinking the 4 leds rapidly⌠like a BTStack crash or somethingâŚ
How and why are people having permissions issues on jailbroken devices with this app. I dont see any one on stock having these issues. Is it the way the deb installs? When you install the package is the directory permissions already mucked up? Im thinking a postinst in the deb to fix (set) the perms if this is the problem would fix this.
Tried but still nothing has changed. I have followed every step in the videos uploaded by Idevicemovies and tried again but the app just crashes every time when i load a game.
Tried but still nothing has changed. I have followed every step in the videos uploaded by Idevicemovies and tried again but the app just crashes every time when i load a game.[/quote]
Crash log please. This isnât telling me anything.
First of all I would like to say this is a great app, but I need help with using my paired PS3 controller.
I have successfully paired my PS3 Sixaxis controller with my iPad using Blutrol, but I am having a similar problem to what some other users have reported. In the Cocoa UI when I swap to Input Options > Device > SixAxis/DualShock3, RetroArch is still not registering input when i go to bind keys in the âPlayer 1 Keysâ dialog. Can anyone see what I am doing wrong here?
I have studied the Retroarch-ios-0.9.9.PDF, but the section on pairing PS3 controllers is a bit brief and did not yield a solution, nor did the FAQ. Thanks in advance.
You shouldnât use Blutrol though for RetroArch.
My recommendation would be that (after successful pairing of your device with the PS3 pad), you go to RetroArch - you stay at the game ROM selection screen and you press the âSyncâ button there. Wait until the LEDs stop flashing. Then start the game. The pad should work then.
These issues are really BTStack configuration issues and not so much to do with RetroArch. If it still doesnât work, respring - it could be that the wrong Bluetooth stack is currently selected.
You shouldnât use Blutrol though for RetroArch.
My recommendation would be that (after successful pairing of your device with the PS3 pad), you go to RetroArch - you stay at the game ROM selection screen and you press the âSyncâ button there. Wait until the LEDs stop flashing. Then start the game. The pad should work then.
These issues are really BTStack configuration issues and not so much to do with RetroArch. If it still doesnât work, respring - it could be that the wrong Bluetooth stack is currently selected.[/quote]
Thanks a million. This worked
You shouldnât use Blutrol though for RetroArch.
My recommendation would be that (after successful pairing of your device with the PS3 pad), you go to RetroArch - you stay at the game ROM selection screen and you press the âSyncâ button there. Wait until the LEDs stop flashing. Then start the game. The pad should work then.
These issues are really BTStack configuration issues and not so much to do with RetroArch. If it still doesnât work, respring - it could be that the wrong Bluetooth stack is currently selected.[/quote]
Thanks a million. This worked[/quote]
EDIT: Itt seems the most reliable method to sync the PS3 controller in RetroArch is to press the PS button in the Rom selection menu (as you said), then start a game and open cocoa GUI and go to input options, then select Sixaxis.
Well it is true that not all of the options in the Cocoa menu are in sync with those in RGUI. this could be something for meancoot to look into.
Also - the default keybinds i added for Wiimote / PS3 - ideally there should be an input autodetect option similar to the Android port. What this would do is that it would autoconfigure the connected gamepads based on those default binds.
well as a fun note this runs fine in ios 7 (to be expected)
Ahh my mistake, I have been using RGUI and mistook it for the cocoa UI
Is there a way to access RGUI or Cocoa before loading a game or selecting a core? The thing is, the lights on my PS3 controller wonât stop flashing, even when I have got this to workâŚ
Tried but still nothing has changed. I have followed every step in the videos uploaded by Idevicemovies and tried again but the app just crashes every time when i load a game.[/quote]
Crash log please. This isnât telling me anything.[/quote] Sorry to ask but where can i find the crash log?
Mate, make sure your ps3 controller has the right blutooth mac acress associated first (does it work in blutrol for example?), then enable BTStack (NOT THE ICADE ONE, the 2nd option), and push the PS button when the bluetooth logo shows on on the status bar. Should connect right away (5seconds max)
Mate, make sure your ps3 controller has the right blutooth mac acress associated first (does it work in blutrol for example?), then enable BTStack (NOT THE ICADE ONE, the 2nd option), and push the PS button when the bluetooth logo shows on on the status bar. Should connect right away (5seconds max)[/quote]
Yes I think it has the correct MAC address, as I set it through sixpair twice to be sure. Also it does connect flawlessly in blutrol. Not sure what the problem is. To test for a potential conflict I uninstalled blutrol and respringed multiple times (testing in retroarch each time). Now I am not having any luck syncing my controller in retroarch. Also btstack is enabled in my deviceâs settings and in retroarch. Also icade is disabled. No progress has been made