@BlackLord
note : my understanding is that this modified genplus-gx core is breaking some stuff, so it is not recommended to replace the original genplus-gx core by it (which is probably what you did)

I have updated the script and the database.

@DTEAM
I have update the database, partly in the new way with the AWK script and I added the categories from progettosnaps on top of it.
The data is probably OK but can you do some checks too ?

@gvx64

My screen is 800x480 and my "emulator resolution" is 640x480

[Layout] anaglyph_shader_name=rendepth (builtin) anaglyph_shader_name\default=true custom_bottom_height=480 custom_bottom_height\default=true custom_bottom_width=640 custom_bottom_width\default=true custom_bottom_x=80 custom_bottom_x\default=true custom_bottom_y=500 custom_bottom_y\default=true custom_portrait_bottom_height=480 custom_portrait_bottom_height\default=true custom_portrait_bottom_width=640 custom_portrait_bottom_width\default=true custom_portrait_bottom_x=80 custom_portrait_bottom_x\default=true custom_portrait_bottom_y=500 custom_portrait_bottom_y\default=true custom_portrait_top_height=480 custom_portrait_top_height\default=true custom_portrait_top_width=800 custom_portrait_top_width\default=true custom_portrait_top_x=0 custom_portrait_top_x\default=true custom_portrait_top_y=0 custom_portrait_top_y\default=true custom_second_layer_opacity=100 custom_second_layer_opacity\default=true custom_top_height=480 custom_top_height\default=true custom_top_width=800 custom_top_width\default=true custom_top_x=0 custom_top_x\default=true custom_top_y=0 custom_top_y\default=true factor_3d=0 factor_3d\default=true filter_mode=true filter_mode\default=true large_screen_proportion=4 large_screen_proportion\default=true layout_option=0 layout_option\default=true mono_render_option=0 mono_render_option\default=true pp_shader_name=None (default) pp_shader_name\default=false render_3d=0 render_3d\default=true screen_bottom_leftright_padding=0 screen_bottom_leftright_padding\default=true screen_bottom_stretch=false screen_bottom_stretch\default=true screen_bottom_topbottom_padding=0 screen_bottom_topbottom_padding\default=true screen_top_leftright_padding=0 screen_top_leftright_padding\default=true screen_top_stretch=false screen_top_stretch\default=true screen_top_topbottom_padding=0 screen_top_topbottom_padding\default=true small_screen_position=2 small_screen_position\default=true swap_eyes_3d=true swap_eyes_3d\default=false swap_screen=false swap_screen\default=true upright_screen=false upright_screen\default=true

@Lolonois said in usb boot from 5tb hdd:

@korn16ftl3 Looks correct, except you are missing one hex-number in the product ID (should be :25ee and not :5ee).

The quiet parameter is double but it does not have an impact: The kernel parameters are parsed left to right and the last one wins, if there are two identical parameters.

My new question is since we are playing with the cmdline.txt, what are the other parameters that are there?

The kernel parameters are documented in the kernel documentation, in the raspberry pi documentation, and the kernel parameter of plymouth and info about plymouth itself are documented for example in the Arch wiki,

i made the previously mentioned changes to the cmdline.txt and am getting the same error readouts.

im starting to think/wonder if the GPT portion of thi is what is causing some of my problems as retropie its self if i understand correctly was written for MBR and everything boots just fine in MBR and GPT when everything is <2tb the second i convert the GPT partition manually (before initial retropie boot and partition resize) everything ceases toi load/boot.

im going to remove the

quiet init=/usr/lib/raspi-config/init_resize.sh

from the cmdline.txt since perhaps it is hanging on attempt to resize a partition that has already been resized for one and for two is GPT and not sure how to handle it.

lets see what that does i suppose.

also debating on wiping everything abd starting over using gparted and specifically raspberry pi os to try to set tis up as well maybe that ii yield different results.

will report back after a little bit of experimenting and a bit more research.

alternatively i have seen some things online that enable UEFI booting ( [https://www.linux.it/~ema/posts/secure-boot-rpi/](link url) , [https://github.com/pftf/RPi4](link url) ) would this be any help with trying to boot from >2TB partitions as UEFI booting supports it? would there be any drawbacks or risks to experimenting with these options?

@Striderx99 thanks. thats the same thing i got also. im going to try a clean install on my pi4 at some point to see what i can figure out. maybe see if i can pin point something i can give the dev

@Folly said in Tutorial: Handheld and Plug & Play systems with MAME:

@DTEAM said in Tutorial: Handheld and Plug & Play systems with MAME:

playmaker -> classich

Looked at it again.
When starting it does nothing.
Looks like it uses cartridges so I added one in the mame ui.
It kinda worked after a while.
Not sure now if we should add it.
I can filter on media so it will not be added.
What do you think.

I got my infos from here:
http://adb.arcadeitalia.net/dettaglio_mame.php?game_name=playmaker &arcade_only=0&autosearch=1

I'll test it tomorrow

New edit : works well on my side and looks like what presented here :
http://adb.arcadeitalia.net/dettaglio_mame.php?game_name=playmaker &arcade_only=0&autosearch=1

Here's an UPDATED Tutorial on how to add my Bezels to Retroarch
using the the Mega Shader

@roslof Do you have a folder with "lr-mame" 0.278 for rpi5 64bit that you can share? Thanks

@danturn said in < 30 FPS, Can't get games running smoothly on Raspberry pi 5 (Rodland, Gods, New Zealand story):

@RapidEdwin08 ok thanks, i might check this out... did you change due to issues with amiberry?

Yes actually, and I was only playing SuperOffRoad and Lemmings...

I found an older Binary I built on RPi5 Bookworm back in December.
Maybe give this a try and see if the results are better than what you're getting now...

Amiberry v5.7.2 202412

pkg_origin="source" pkg_date="2024-08-05T16:57:07-04:00" pkg_repo_type="git" pkg_repo_url="https://github.com/BlitterStudio/amiberry" pkg_repo_branch="v5.7.2" pkg_repo_commit="d4418a16827d0edd619874405d990725b908b82a" pkg_repo_date="2024-06-06T16:22:44+02:00" pkg_repo_extra=""

Just replace the files as needed and make the binary/sh executable (chmod 755).
I have not gone back and tried this binary myself, but curious what your results are if you do.

Here's an older Module script for v5.6.6 too if you want to try (don't forget the amiberry/*.diffs)
RetroPie 4.8.6 Amiberry v5.6.6 Setup Script

Edit: To be clear I've been using [video=HDMI-A-1:1920x1080@60D] in my cmdline.txt since day 1 on RPi5

@mitu Thanks for the comment!! Of course I will mention to whom it corresponds! And I will gladly agree to improve whatever they want and is within my reach, such as the theme of Pajarorrojo, who is aware of my adaptation of his theme for retropie

@gvx64 Thanks for your reply! Do you perhaps have a resource where I could read about the memory allocation of the pi?

I still wonder why running in lower resolutions seems to help then.

Unfortunately, your suggestions do not apply to me.

I run it in stock version. Let me know if there are more diagnostics I could provide you though! I monitored the CPU usage via htop but I do not know how to do the same for the GPU. I have the 8 gigabyte version, that should be plenty right? While monitoring with htop there seemed to be enough headroom.

Well, the OP should just move to MAME current tbh, not only it has support for TATE in both directions, but it probably also has better support for cocktail mode (i highly doubt all cocktail fixes from the past 22 years were backported to MAME2003+).

As for FBNeo, it is not suitable at all for cocktail setups : some games had their 2P mode and cocktail mode tied together, and ended up being un-cocktail-ified so that 2 players could play them without requiring a cocktail setup.

@gilllig said in Retropie doesnt boot with changed config:

Ive installed raspOS and retropie, but now they dont even run))

What exactly does this mean - they're both not running ?

I tried to choose emulationstation at the settings, I tried to add line "/usr/bin/emulationstation" in the /home/pi/.bashrc, but its not working...
I cant understand how to make autostart for raspOS or for retropie

You're running in an unsupported configuration, as I mentioned in my previous post, so you should not use the normal RetroPie auto-start options from the menu.

If you have installed the RaspiOS with Desktop, then just use the default option to boot to the Desktop. You can start EmulationStation from a terminal by typing emulationstaton. If you wish to automatically start Emulationstation after the boot to desktop is done, then

create the $HOME/.config/autostart folder add a .desktop file with the command to start the terminal and EmulationStation (lxterminal -e emulationstation).

It seems that Retropie does not currently handle dual monitors. I am going to try a few different options. Maybe loading the Pi right into Mame, or maybe start an OS with retroarch and load a core.

More to come….

@mitu I don't remember I haven't booted Linux on arcade in a while. Sorry.

@Moulinex glad it worked
I'm not sure what was going on with what you where trying.
It possible you missed a step
I haven't used that way since this was made

neither of these things (permissions or starting clean) seemed to resolve. I also @ByteThis did not seem to rectify this by only configuring player 1 (but good idea) With a clean install and remapping all the input settings I am getting to where the select and start button only work in the retropie menu (scrolling diffrent consoles exploring settings etc.... But when I launch a rom NONE of the bottons work.

I ran some more jstest output today....

davis@raspberrypi:~ $ jstest --normal /dev/input**/js0**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

davis@raspberrypi:~ $ jstest --normal /dev/input**/js1**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

So it sees both controllers, but does not detect any button or axis input events. I think It is time to just replace them. Ive had them over a year and the more I think about it the more I think I possibly damaged these things. They used to be mounted in a metal cabinet and the opening I cutout for the control panel was very tight. (see attached called "old") old.jpg

New cabinet.......

new.jpg

I think its time to just replace the usb encoders.

Thank you!!!

@mitu Oh that's good to know ! I tried running it on the non-Lite, thinking I wanted to avoid missing libraries and the likes (and that for my box64 testing purposes, it was probably best to have a full GUI available), but it probably created issues instead. I'll definitely do that then, project's back on track :) Main issue I had was when compiling MAME libs, any idea if it's still a massive RAM hog ? (if so I had precompiled them anyway, but the compile is probably quite outdated now)

Also just realized, had I double posted ? My first attempt to submit left the page blank and hanging, and when I clicked back to the forum's main page, I was shown my own post, still ready to submit, so I assumed it was a saved draft, sorry for that if it ended up being a double !

@Lolonois Thanks for the guide link too :) Gonna come in handy !

@mitu thank you problem solved:
Deleted 1st partition (unused 16mb)
And now /dev/sda1 is correctly mounted ...on my hdd2...465gb
Retropie boots quickly and without warnings.
Thanks

@Folly said in Streets of Rage Remake 5.2 on Retropie 4.8.8 Issue:

Which file is it ?

It's in the main RetroPie repository now, hence has been removed from the extras.