/vr/ - Retro Games

>>1691109

Its mapped to a standard dual analog controller like how it was mapped to a Gamecube controller in the Ocarina of Time rerelease, with the Z trigger being mapped to left trigger (L2) and L being mapped to left shoulder button (L1), R being mapped to right trigger (R2), C buttons mapped to right analog stick, while the N64 analog is mapped to left analog, and B and A are mapped to X and O respectively (which can be swapped to □ and X optionally with a core option)

This seems to be pretty optimal for most N64 games to me and how I've always done it in other emulators. You can remap the controls in RetroArch then save it to another config, just keeping in mind remapping its "A" or "B" buttons will affect menu controls.

>>1691338
Is there a way to set it to only use that input setup for one core?
I've tried enabling an option that was "Each core gets it's own config" or something but it didn't seem to effect input keys

>>1691375

I think you have to load a game with that core, then make changes for that core's config to stick.

>>1691379
thanks much

I always thought you had to save a separate config file and add "-c [your config].cfg" to the shortcut/command. I guess it's more convenient than I thought.

My question is how do per-game controller mappings work in Retroarch, since basically anything but an N64 pad will require a different setup for every game.

How come everytime I try and play psx games on retroarch it instantly closes. I don't get any error or anything. I put SCPH1001, SCPH7003, and renamed a copy of SCPH7003 to SCPH5001 in the system folder.

>>1692224
I took some screengrabs of it crashing and it helped a little, I threw the bios into the same folder as the image and now some open.
All of my psx images have bin and cue files. How do I know what ones will work when I download them? I have limited bandwidth so I download these at a buddies place so it's not easy for me to just keep downloading them until I find ones that stick.

>>1692224
It will definitely be a BIOS problem. Start retroarch via the command line with these options to get an error log "--verbose --menu"

>>1692224
The bios must be named 5501 not 5001.

Are there any up to date versions of phoenix? I picked up a retroarch-phoenix bundle and I really like the front end, but it looks like its depreciated now. I can still add cores manually from downloading them off the internet, but there's no more automatic updates or core repository I can download them from in the program.

>>1691632
SP thinks every controller out there follows the 360 pad layout, what he calls 'retro pad', so it's not going to work

>>1693125

What are you talking about? The "retro pad" is an internal abstraction for intefacing with the cores, you can map your actual gamepad to it any way you want.

That seems like the right place to ask. The PSX dumps from Nitroroms are working quite well for me, but there are a few games (Armored Core and Tomb Raider 2, for example) which don't run no matter what I try. The cuesheets seem to be okay though so I have no clue why they don't work. Simple mednafen compatibility issue or are the dumps bad after all?

>>1692224

Mednafen is very picky about the bios, even if they appear to be the "right" files, madnafen still mind find some issues with them. Try this pack
http://www.mediafire.com/download/y8w1wd7j25rhqfc/RetroArch+BIOS.rar

>>1691109
>I recently started using retroarch and I like it a lot.

>>1693050
Retroarch comes with all of the cores now, so you won't need to download any new ones. I've had a hell of a time getting Phoenix to work on newer versions, so I eventually gave up and started using RGUI and saving different configs. It's actually not so bad, once you get it set up. Operating the emu interface with the controller is great.

>>1693148
What he's saying is that not every console had 4 face buttons, 4 shoulder buttons, start, select, a D pad, and two analog sticks. They still correspond to N64 controls in some arbitrary way and can be mapped as such, but it's really inconvenient to trial and error to figure out what Z or the C buttons are supposed to be EVERY TIME you play a different game because the N64 design just does not have anything resembling a 1:1 relationship with the "retro pad."

>>1691109

>RetroArch

>>1694738
I don't know if you're just being facetious because "retroarch shills" is almost at meme level on /vr/, but seriously, the reason people talk about it so much is because it really is a great setup for a lot of people. Nobody's making any money, and in fact I'm pretty sure there's a huge rant against selling software on the RA homepage.

There are a few things retroarch allows consistently, through all of its cores, that you can't necessarily do on every standalone emulator.

>>1694754

Don't respond, just report. He won't shut up if you give him attention.

>>1694754
>>1694758

>>1693125
Yeah fuck this gives me the shits. FUCK.

Is there anyway to fix the menus/screen transitions in paper mario. I know it uses mupen64 but I can't seem to find anyway to clean it up. Reminds me a lot of ff9.