@mitu i figured it out/ remembered for the slow speed issue

for anyone with the Nespi4 enclosures you gotta add
usb-storage.quirks=152d:0562:u

to the /boot/cmdline.txt file adding it at the beginning..

so instead of 3 min 30 seconds to load up the configuration files before it shows up the retropie screen.. now it only takes 28 seconds to sit at the loading configuaration

and now i get 80meg/s instead of the 5meg/s

gonna write steps in a text file the procedure so i can remember next time the orders and what to add if i format or build another one of thess

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

i don't think there's much point testing lr-mupen64plus-next as it's going to be slower than standalone, but there's a few settings you can change:

native resolution factor = 1x Overscan = Disabled

be mindful to change only these, and exactly these. some others are named similarly.

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

comparing what to what? please be specific. if it's to lr-mupen64plus-next, again this is not optimal. use mupen64plus-gliden64

Hello,

thanks to all of you.

Now I nderstand that I dont need to edit emulator.cfg, just lanch runcommand.

Thanks

Francesco

@mitu Thanks for confirming. I thought this was the case. Unfortunate. Would be cool to use it. I may just have to add a couple of small buttons for navigating the ui.

@keeks said in pi4 and memory:

@busywait I should have searched for RAM rather than Memory :)

:)

I run a Pi4 4GB behind my TV set. Sometimes I start the Pi Desktop and more RAM might help in that situation. (Browser with too many tabs, ... ?) But if you're sticking to just game emulation, sounds like you can save a little money \o/

Spending the saved cash on a good heatsink case (or case heatsink) would be sensible to stop the Pi getting too hot, and allowing more aggressive overclocking.

@mitu so these aren't official retropie images found on this site; https://retropie.org.uk/download/ ???

NVM: solved it now. Didn't have parse gamelist off in settings.

@kn4thx thanks for the reply. The pi does have power - red light is on. I’m going to try the config you mention.

@billy said in Can't access Retroarch (while in a game):

@dankcushions i'm not sure i know what you mean by that. I checked the /dev/shm/ folder and it's empty. So i don't know what verbose login means.
The issue i have is the bezels around the games, so the show overlapping the edges of the games. In some of them you can't see important information of the game. So it's either reducing the bezel frame or reducing the game to fit into the bezel space.

read my link carefully. it explains what a log is, and how to produce one.

@cthulhus You can edit the es_inputs.cfg and disable the start and select buttons so you can't access to that menu until you replace the original es_inputs again.

... typos fixed above

@kikus said in lr-pcsx-rearmed loads but freezes at "Paused." black screen:

Built From: Started from Nachos 64GB image but updated all package from source recently

We don't support 3rd party images. Ask the author(s) of the image for support or use the image from retropie.org.uk/download.

I have set up a new retropie with two xbox one wireless controllers. Both have worked perfectly.
Then, after weeks of intense use, the left on the right joystick stopped working on the first controller. But Ok I just used the second controller for that single game where I need both analogue joysticks. Today after month of intense use the same thing appeared on the second controller. The left on the right joystick stopped working. I have tested the controllers on another linux using jstest-gtk, they are in perfect condition.
Just that single left axis on the right analogue joystick is affected. everything else is still working. strange.

@azurden it’s trivial to acquire mame roms of a certain version, but we can’t assist as per the rules. do not try and find roms and then determine their version after the fact - hundreds of mame rom versions so it will almost certainly be wrong. find the version you need.

You should post issues with beta firmware on the Raspberry Pi forums, since you'll get better support there. If you want to get back to a working EEPROM, I suggest you use Raspberry Pi Imager and flash the latest stable EEPROM image.

@dreamcastkid got it. thanks again. Think I am all set here. Appreciate it.

Sorted it

Pressed hotkey and X

Went into options
then controls
the changed auto 3 (key x) to fire

problem solved!

@chris3535 as @mitu said, I needed to go into the retroarch settings for lr-fuse and set the control 3 option to keyboard, works fine now.

@awe3

And make sure you are not trying to play a Dreamcast WINCE game ... because they won't work in any Dreamcast Emulator in the Raspberry Pi.