Any progress on n64?
Agreed. Usefulness would depend on the use of the analog stick on the nunchuk. If that could work, 4-6 button fighting games would be awesome (using the direction pad as attack buttons:)
Well, maybe in the future. In the meantime I will see if I can locate a classic controller for a reasonable price here in Mexico;)
Hmm - that might be a good idea to get this release out without having to depend on a Cydia repo.
Does anybody have a HOWTO on how to make an IPA that will work on all jailbreak devices?[/quote]
I don’t remember if this still works, but if you are “signing” it the same way and you get the .app folder out of the build, you can just zip the .app folder and rename it .ipa. You can also build sign and share from Xcode.
It depends on the distribution method as well. Are you hoping to be able to script-build nightlys and have links on the site? Or something like that.
I don’t know if this still works or if it will work for what you want to do but this worked for me to get it to build with my cert.
Also, I think I’m ready to share the iPhone 5 compatible overlay I’ve been working on. The reasons it’s taking so long is
- I’ve done the whole thing on the iPhone itself using artstudio (best photoshop app by far) and ifile. I haven’t been home for more than a few days before I had to go back out again.
And 2) I’ve been taking some psychology into account. I have my phone to a few people with a static game screen and zero feedback to do the konami code on the device. Little did they know I was recording the touch points. This was done with artstudio with a transparent in black layer in full screen mode. Each touch being a dot. Hide the black layer and yay, “data.”
So I had all the data points to make hit boxes, but they need to be somewhat symmetric and the display had to be pretty darn symmetric as well or it would just look like crap.
Keeping in mind that the iOS also adjusts touch points by a little. It’s important the device knows its oriented properly. This isn’t necessarily the way the screen is oriented as I’ve seen the system UI not know the current orientation (seen by adjusting the volume ) if the system thinks its still in portrait even though retroarch is in landscape, touch points will be shifted sideways instead of up or not at all.
In any case. What came out of all this is what I think is a fairly usable overlay for the iPhone 5 or any other 16:9 device.
There is also a second L key grouped with the face buttons to make 6 button fighting games easier. I’ve also added grouped buttons and diagonals.
The scale is kind of large but this was all designed off the data people added by “playing”.
Feedback would be great. I will add menus and rgui keys soon. Doing this all on my phone on tour is a fun challenge and keeps me sane.
Hmmm. Tried posting the png and I’m having some issues with the wifi here and there’s zero cell service. Will post soon.
@omgsus
That’s a clever idea using the transparent overlay to get usage data. I look forward to checking it out
I wanted to reiterate that I feel the scale is a little on the large side but again, this is what people put in during testing. There was a second part of the test that used the controller overlay so I could deteine how to offset hitboxes too. Looking forward to feedback.
Select and start are top left and top right
Diagonals on dpad. Second l button down by “b” for easy fighting/strafing.
No l1 or r2 yet. Was getting crowded.
Combo face buttons. Rolling press from y to b will let you run and jump etc.
Wonderswan version coming too (already posted in github thread. Will copy here soon)
Rename to ztestl.png
ztestl.cfg is pasted below :
overlays = 1
overlay0_overlay = ztestl.png
overlay0_full_screen = true
overlay0_descs = 21 overlay0_desc0 = “left,64,484,rect,64,50” overlay0_desc1 = “right,249,484,rect,69,50” overlay0_desc2 = “up,151,377,rect,51,57” overlay0_desc3 = “down,151,584,rect,51,57” overlay0_desc4 = “start,1036,40,rect,100,40” overlay0_desc5 = “select,100,40,rect,100,40” overlay0_desc6 = “b,952,572,rect,64,64” overlay0_desc7 = “a,1053,471,radial,64,64” overlay0_desc8 = “y,836,471,radial,64,64” overlay0_desc9 = “x,924,370,radial,64,64” overlay0_desc10 = “l,705,600,rect,84,42” overlay0_desc11 = “r,1091,237,rect,45,90” overlay0_desc12 = “l,45,217,rect,45,70” overlay0_desc13 = “left|down,51,587,rect,53,58” overlay0_desc14 = “right|up,256,378,rect,56,58” overlay0_desc15 = “up|left,51,378,rect,53,58” overlay0_desc16 = “down|right,256,587,rect,56,58” overlay0_desc17 = “y|b,877,548,radial,45,45” overlay0_desc18 = “x|a,1000,450,radial,45,45” overlay0_desc19 = “y|x,918,444,radial,45,45” overlay0_desc20 = “a|b,1036,556,radial,45,45”
Wonderswan discussion and version posted here:
Also am noticing that if you use the orientation settings to force any orientation, there are issues with the touch offset. I recommend not using any orientation overrides at all until that’s fixed. (This is whether the system UI responds to the orientation or not. I thought it was related, but it’s random so far? )
For instance, setting toggles to only use landscape right usually shifts all touch inputs right, which is consistent with how the system works in portrait. Again, this is independent of the iOS overlay (volume overlay) being oriented properly. If you NEED to use orientation overrides and experience these odd issues with touch being odd, exit the game and rote the screen around in the cocoa menu then make sure you are in the “allowed” orientation before loading a core.
Ugh. I forgot another issue from before. I don’t have net sometimes so I should write these down :-/ but now that I have net I dump all this stuff on you guys. sorry.
Pressing the cocoa GUI button (top center of screen) sends a touch to overlay at 0,0 (or 1,1?).
In the first release i could use the left stick to work like the dpad and the right stick to save - load and change states. Now i can’t use them even when i set them in the core and global configurations.
Was that already reported?
Will n64 Core be released in 1.0?
Is anyone else having trouble with iCade support?
I have an iPad 3 and an iPhone 5, both with RetroArch loaded and neither will work with either my iCade or my Gametel (in iCade mode). I have verified that the controllers are properly connected: I can use them in one app fine, but if I load RetroArch, they won’t work at all.
I apologize if this is a stupid question. I’ve looked everywhere and can’t seem to figure out what I’m doing wrong.
iCade was “broken” in the last release but is fixed in the current code. Next release should have icade support again.
Thanks so much for letting me know. I’ll just keep watching Cydia for an update.
I know it was mentioned before that backwards compatibility is being considered, but I was wondering if there is any new information concerning the topic. I pretty much bought an iPad just to play emulators on it and a psx emulator is what I value most. Unfortunately, nothing has been smooth/playable until I found out about RetroArch and its awesomeness. After some research it looks like I missed the window to upgrade to OS 6.1.2 on my iPad2 and now I’m stuck at 5.1.1. I’m not sure how much work it would be to make it backwards compatible, but a lot of people would greatly appreciate it. Thanks for all the work you guys put into this!
Oh, and do you think it would be better to upgrade to 6.1.3 or stay at 5.1.1? My only interest is getting the psx emulator working. More specifically, is it more likely that RetroArch will become compatible with 5.1.1 or 6.1.3?
Since you are most interested in the PSX emu, the question comes down to what will be supported by that core. PCSX ReARMed requires a jailbreak that allows for dynamic code execution. Just because RetroArch gets “supported” for a version/jailbreak, does not mean PCSX RA core will even work. Stay away from tethered jailbreaks, for instance. And there are some untethered ones that still don’t get deep enough to allow dynarch.
Don’t blame your installation issues on us. RetroArch iOS works just fine for the vast majority of people.[/quote]
Same problem with pcsx reARMed, i also have untethered evasi0n jailbreak on my Ipad 4 ios 6.0.1. My PSX ISO files is good, they worked with psx4all emulator. All bios files in right place, they on blue background in core info page. There are more reports of this issue here and everywhere, for example: http://translate.google.ru/translate?hl=ru&sl=auto&tl=en&u=http%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D467347%26st%3D160), All with ios 6.0.1, is it unsupported? If my iOS device failed the dynarec test, why is nds emulator working? I heared it uses dynarec too. Maybe something wrong with pcsx reARMed?
I can only verify that the jailbreak for iOS 6.1.2 from evasi0n is fully working with regards to its dynarec capabilities. As for the others - you are on your own.
This information must be included in retroarch pcsx rearmed description: “For IOS 6.1+ only!!!”. Then will be no complains. The rest of retroarch is really great, thanks for all your hard work.
Don’t blame your installation issues on us. RetroArch iOS works just fine for the vast majority of people.[/quote]
Same problem with pcsx reARMed, i also have untethered evasi0n jailbreak on my Ipad 4 ios 6.0.1. My PSX ISO files is good, they worked with psx4all emulator. All bios files in right place, they on blue background in core info page. There are more reports of this issue here and everywhere, for example: http://translate.google.ru/translate?hl=ru&sl=auto&tl=en&u=http%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D467347%26st%3D160), All with ios 6.0.1, is it unsupported? If my iOS device failed the dynarec test, why is nds emulator working? I heared it uses dynarec too. Maybe something wrong with pcsx reARMed?[/quote]
DeSmuME x86 uses JIT for x86. I don’t think the DeSmuME core for libretro uses an ARM JIT.
A separate emu, ppsspp uses ARM JIT as well. You have to enable JIT in it’s settings menu. Would be a good test. If it doesn’t work there, it’s your jailbreak. If it does, then the core may only work on 6.1-ish. Although, I’m pretty sure people were switching jailbreaks to/from lime on 6.0 to get dynarch … Maybe I rember wrong.