@dankcushions said in Issue with some psx games:

but your log is for tomb raider?

My read is that 'all games from MGS till the end' are not working, hence it's not just a single game.
Otherwise, yes, it looks like a bad disc dump or corrupted file. Try with simple .cue/.bin images that you can validate against redump.org's database.

Looks like the performance is pretty poor, even without sound. What emulators are you running and what resolution are you using ?
Can you run with verbose logging enabled (switch it on in the Runcommand launch menu) and then post the log from /dev/shm/runcommand.log ?

sudo apt-get install ubuntu-desktop

Resolved the issue, and PS2 appears in the EmulationStation frontend.
.bash_history doesn't show any evidence of the desktop environment being removed - by way of shell command.

I got it working!
I previously disabled the runcommand launch menu, so I re-enabled it.
Then, choosing the lowest resolution provided by @quicksilver, it works!

Thank you guys!!

I don't have any issues with Dosbox using the dev branch on a PI4 - did you set any special resolution for it through the Runcommand launch menu ? I just installed it from scratch and it's using the default configuration file installed by the scriptmodule.

Same thing with dosbox-sdl2 - it's working just after installed with the default configuration.

@AlphaBetaPie said in Easiest Way to Remove Key Bindings?:

Would kiosk mode work equally well?

Yes, that's also an option.

@BJRetro I hope once the pi 4 is fully supported this game works well on Dreamcast without the current work around. It's a shame it has issues for Dreamcast, dosbox and psx.

@BuZz It's definitely spam, the Reddit forum creation account is now deleted.

@Dinsdale ah got it! Well glad it works now sounds like a really neat set up. On the other hand I would have never thought to use an Alexa powered outlet so I guess teamwork!

@Brownmonster

Hi Ste,

Thanks for the update, I have downloaded the new version and Amiberry but I am having trouble getting Amiberry to regonise Retroarch Keyboard as Joystick for custom mappings.

My Ipac2 is set up with player one's control as gamepad inputs, this is recognised as "Ultimarc Ipac 2"and I can use custom controls with this, the "r" indicating a retroarch controller shows next to the input box.

Player two is set up with keyboard inputs, this is recognised by Amibery as "Retroarch Keyboard as Joystick [#1]", but for some reason I cannot use custom mappings, and there is no "r" in the input box and it states "Not a valid Input Controller for Joystick Emulation".

It does recognise the standard joystick controls "left, right, up, down and fire button 1" which are mapped via my retroarch.cfg (this is placed in opt/retropie/configs/amiga/amiberry/conf/ directory, so the second player controls are working, I just can't get custom mappings to work.

Any ideas why?

OK, I reset the default.cfg in mame2003 -folder, now the TAB is working and I can change the

I change the sensitivity in the menu,
seems for Centipede it's not going "faster",
because in Marble Madness or Missile Command the control is running faster after the changes !

Thx!

Hmmm im getting to a point that i think Reinstalling retropie will maybe help
what do you think about reinstalling ?

@raibura hi, did you ever find a solution for this?

Sorry for asking in such an old thread but you are the only person I have found with the same problem as me. Thank you

I used a teensy 3.2 with an xbox(ish) setup, the only difference being the r2 and l2 are buttons not analog triggers. This would also apply to the teensy LC which is similar.

Here's a couple pics of the handheld I made, I'm just getting the controls working and all the emulators setup and having a blast!

handheld1.jpg

handheld2.jpg

@dankcushions said in Pcsx_rearmed ignores the offset settings:

@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.

Sorry for the late response, That's why I made my changes:
Github issue

I forgot to post the following entry in my config.txt:

dpi_timings=320 0 10 10 10 **512** 0 5 2 5 0 0 0 60 0 9600000 2 pi@retropie:~ $ vcgencmd dispmanx_list display:0 format:XRGB8888 transform:1 layer:-127 src:0,0,448,320 dst:48,0,448,320 cost:338 lbm:0 display:0 format:RGBA32 transform:20001 layer:10000 src:0,0,512,320 dst:0,0,512,320 cost:374 lbm:0 display:0 format:RGBA32 transform:1 layer:20100 src:0,0,15,9 dst:463,2,15,9 cost:98 lbm:0

it is possible to pass the following mode in run-onstart.sh for pcsx-rearmed:
display:0 format:XRGB8888

@top-specci a pi 2 image will work on a 3b+ as long as it's an image based on raspbian stretch. If it's an older retropie version then it will not work on the 3b+.