@reruns_towel it makes perfect sense to me :P you want to add fake overscan to your screen. you can do that in the way i instructed, and that would apply to the whole system. the way you've previously done it is to add overscan to the console (command line) only, and then adjust each bit of software to solve the issue, which as you've found, isn't always possible.

@oleguer said in Cant load MTV Celebrity Deathmatch on Pcsx-rearmed: I "read" the game cant load becuase have in the name "deathmatch" Really?? xDD No, it's not because of the game name. The crash means the ROM is either invalid or not supported by the emulator. Check if your disc image is correct - the .cue file should contain a reference to the .bin file, from your log it looks like the .cue file might be incorrect ? That being said, there are a few PS1 games that are not working on pcsx_rearmed - I think this particular game might fall into that category, see this topic.

This info is covered already in the Docs - including where to copy the BIOS files, since RetroPie already configures RetroArch. Note that some games have issues when the 'boot to BIOS' option is selected in lr-pcsx-rearmed.

After an evening of pondering this, I have figured out what I did to screw it up. I have created multiple images of RetroPie setups that were reasonably customized and saved piles of things I referred to as "Clean" associated with those. (For example, known good ROMS, BIOS, and Meta Data like Scraper results.) What happened was that I missed a step trying to recreate my steps. So here's the abbreviated version of what I did that messed it up. Wrote the correct, unaltered, unupdated 4.5.1 image to the SD card (I really couldn't believe I would have written the wrong image). Copied vast amounts of "Clean" altered configs (for a setup that was designed for SNES controller compatibility, and thus didn't use PSX). Boomie. (At this point, I believe my copying of configs was all it took to scramble it up.) It should have been obvious when the pixel art launch screens came up (part of the config I just copied), but I honestly recall thinking "Oh cool, 4.5.1 uses the same pixel art things I liked for launching games." Thus, to your point, I had 4.5.1, with a bunch of 4.4 config wedged in manually after the fact. Worse, because my previously configured system never used PSX (not enough RasPi power when I created it, and not enough buttons when using SNES controllers), I had no idea that there might have been a bug with it that had been hiding in what I was copying. Thanks for the feedback.

Wow... So far indeed solved... Followed : https://www.reddit.com/r/retroflag_gpi/comments/c1psvj/dpad_not_working_in_pcsxrearmed_and_gpsp/ .... and played crash bandicoot fullspeed !

@backstander Never has purple been so perfectly personified.

@hhromic said in How to configure controller for pcsx-rearmed (pi3) ?: @Efriim @Duxa I don't know how to force bios, other than by suggesting to the lr-core by removing the other bios options, and I haven't tested this, or known any priorities other than it prefers scph101.bin The search order for BIOS files is fixed: https://github.com/hhromic/pcsx_rearmed/blob/588bf7918460109815d5cc505ada4334a4c5a791/frontend/libretro.c#L1934-L1939 const char *bios[] = { "SCPH101", "scph101", "SCPH5501", "scph5501", "SCPH7001", "scph7001", "SCPH1001", "scph1001" }; @Duxa Quick Menu -> Options -> Enhanced Resolution (slow) - disabled Quick Menu -> Options -> Enhanced Resolution speed hack - disabled Both of these were enabled by default. Are you 100% sure these are enabled by default? As far as as I know that is not true. From the source code: https://github.com/libretro/pcsx_rearmed/blob/588bf7918460109815d5cc505ada4334a4c5a791/frontend/libretro.c#L495-L497 It can be seen that these options are defaulted to disabled, and as far as I remember they are disabled on fresh install of the core. Fairly sure, I certainly didnt set them, maybe some other setting set these? Although if I select to Load Defaults, it still sets these to Enabled. Which is a good thing for 99% of other games, because it does make them look better. Its just these two games need a custom config added or something to future builds.

@webodan EDIT: OK, so I double-checked the md5s of the bios files that i have downloaded BEFORE and AFTER sending them to the pi (just in case they would get corrupted as they were sent or something) they matched on winmd5 just fine. lr-pcsx-rearmed can use only scph5501.bin from the list of BIOS files you have, and that file has a wrong MD5 in your screenshot - it's not what's in the docs or what the core expects. Unfortunately I can't get a copy of the game to test, but can you just get a RetroArch log file and put it on pastebin.com - enable Verbose logging in the Runcommand launch menu, run the game for a while, then upload the /dev/shm/runcommand.log log file to pastebin.com and paste the URL here.

@Pierouge I managed to resolve this issue by changing the Joypad settings (Hotkey + X) to default for Joypad 1 (no analogue). You can still use analogue sticks with the game even with this setting turned off. The game loads up and plays normally (at first). It also looks great with enhanced graphics. I hope this helps However I now have a new problem. The game freezes (just the game, I can still Hotkey quit out of the game) when I meet the two wolves after the first save point.

It seems like the multiplier is locked. I think I was able to track down a reasonably priced 3.1 ghz core 2 to replace it with. Once I upgrade the graphics card in my main PC, I'll probably put the geforce 570 in there, too.

Today, I have some great news :) The emulator is now fully functional. The only thing you need to do is to update git repository line in RetroPie-Setup/scriptmodules/emulators/pcsx-rearmed.sh from gitPullOrClone "$md_build" https://github.com/notaz/pcsx_rearmed.git to gitPullOrClone "$md_build" https://github.com/timemaster5/pcsx_rearmed.git saio and then run update pcsx-rearmed from source in retropie-setup script Then you will be able to run this emulator without performance issues but only with USB keyboard. I am now struggling with key bindings, I am not able to bind UP/DOWN/LEFT/RIGHT buttons of GBZ SAIO.. probably because they are not buttons but hat... I don't know now. Another issue is with the mouse cursor being visible in some games, but this could be hopefully easily fixable. And for the record, the main problem has been caused by one commit to libpicofe adds SDL_DOUBLEBUF flag.

Have a small update. I have verified that HDMI output works. Something is going on with how the LCD screen on my Freeplay Zero handles the resolution of the emulator. I wanted to see if I could change it in the emulator, but there are no options for resolution. :/

@edmaul69 You can. There are really some rom sharing pages, mentioning clearly those eboots are from official sony psn store. They decrypt it with tools. Another thing is, you are unable to revert back those files to bin/cue/iso files. They are generated from pkg files downloaded raw from sony psn.

@DarioRomero said in Hoto: use Gameshark cheats for the PSX: I followed the instructions closely but when I bring up the emulator menu theres no directory called Extra Stuff. What am I missing or how can I fix this? Are you sure you are using pcsx-rearmed and not lr-pcsx-rearmed? That last one is the default if I'm not mistaken. In pcsx-rearmed the menu opens when I press Escape on a keyboard. If it doesn't then you might be using the LibRetro version of PCSX (i.e. the mentioned lr-pcsx-rearmed). Confusing, isn't it? Good luck! :)

@scyllabus also, retropad isnt a part of the issue.

@mitu I've already reinstalled retropie like 4 times and I swear, every time I touch the controls and attempt to enable the analog stick on FF7, the controls just break forever. Even if I don't save anything. It's so incredibly weird. I've reinstalled for the fourth time and it's working (without analog) on FF7, so I'm just going to not even touch the settings. I really don't want to redo my RetroPie image anymore. I'm just honestly baffled I'm the only person that's ever had this problem with FF7 on RetroPie.