Delete all *.hi and *.nv-files in the ~/hi and ~/nvram folders of your mame4all-directory.

If you meant the default scores which are given by the developers of the arcade-machines: you cannot reset them, they are hardcoded.

I was seeing the same and it was the errors being thrown by the audio issues introduced with Raspbian Buster: https://retropie.org.uk/forum/topic/26628/audio-issues-after-latest-raspbian-updates

@mitu said in Widescreen mod for gemrb on arm?:

@quicksilver said in Widescreen mod for gemrb on arm?:

The issue with the window not scaling properly is a quirk of the pi 4 and the fkms driver. I have run into this same issue with dosbox and other emulators.

No, it's not and I would appreciate if you would stop saying that.

Yikes. My apologies, obviously I am mistaken.

Hi Eisbergsalat

I bought an EasySMX controller recently for retropie use, but I can't for the life of me get retropie to recognise it at all. Did you do anything different to get it recognised, i.e. load any additional modules etc?

Thanks

Evan

Open the options on the Retroarch menu and there's an option whose label I forget that will "map directions to digital" instead of analog. It's set to analog by default. I had to do it a few days ago.

See if it works.

@lupsyn This post can be close solution can be found here : https://retropie.org.uk/forum/topic/24544/reicast-mapping-controllers-2020-version-stuck/20

@mitu Ok, now i just heard that i did have sound on my previews, even when i select games! It is just veeeeery low. The screensaver sound is still on the right volume level, so do not know why they differ, but i vill try to investigate.

@psb The poster hasn't been on this forum for 1 year and bumping old topics is bad forum etiquette. If you have a question, then open a new topic and ask away - don't re-open years old topics.

@AdamBeGood said in How to Install Previous Version of mupen64plus to get Super Mario Star Road working:

Mystical Ninja Starring Goeman excepted.

What is the issue with this game? Is it just slow or other issues?

@lostless Thanks for all. Yesterday I bought two controls and for now they work, I have not been able to test them much. In time I will see how it works.

@mitu - thanks for the reply.

To answer your questions:

Are you sure ? Do you have the latest RetroPie-Setup version installed ?

Yep, absolutely. I downloaded the standard image from the site, deployed it, checked and it says 'installed from source'. I then updated the setup script and it stays the same.

Manual installation will not install the package - it's installed explicitely on the Pi images.
But, about the installation from source - are you looking at the same platform (Pi) when comparing the available options ?

Yep, same platform (my Picade), Rpi 3. The buster image I used on this was from back in Jan and was from the weekly builds, so it was an image (not manual). I have two SD cards - one which is 'production' (which has been subsequently updated) originally deployed back in Jan with a buster weekly image - and another SD with a brand new image which I put on there yesterday to test. So am using exactly the same hardware and setup. In theory, the buster image back from Jan should have installed usbromservice as it wasn't a manual install. It also had the source files in the tmp/build folder, but the script was suggesting it wasn't installed. Perhaps I removed it but I don't think so. This isn't an issue though, as we are only really fussed with how the 'current' image behaves.

To replicate the source install thing, all I need to do is deploy a fresh image (current is April 28, 2020, Pi 2/3 variant) and that's it (updating script post install doesn't change anything). You can then see in the package manager that usbromservice appears to be 'installed from source'. You can also click 'update from source' and it'll update. However, as I mentioned above, if you remove it, the install from source option goes away, and you can then only install via pre-compiled binary, which I assume is what it should be displaying in the first place.

Yes, that's an oversight, should be fixed.

Great, no worries!

There are other modules that are binary only, but they're not packaged since there's no point in doing so (i.e. ports that install through .deb files or 3rd party emulatorts which supply binaries). It's normal.

I see. Currently my picade is only running the main/core packages, nothing 3rd party nor any ports. I only mention because none of the other binary packages installed on the system display like this, they all say 'you are running the latest binary'. This one is the only exception in terms of showing the message 'Binary update may be available (Unable to check for this package)'. So I wanted to ask, just in case that was another bug of sorts.

@retroprogrammer How do you select "Exit: save for all games"?

@BeanFT And... Drastic has an interface that is lagging one frame, which means that the “real” selected menu item isn’t what is shown on the screen. It’s the previous item that is shown. You’ll figure it out when you’re there.

@danyo
Got it running. Thanks!

Aha!

So it works, thank you very much for your guidance, Rascas!

So, for future Googlers who may be having this same issue (Missing the PVR's in Kodi on Retropie), here's the full solution:

Install Retropie, then install Kodi via the "Optional Packages" in the configuration menu.

When you're in Retropie, press F4 on your keyboard to open a Terminal window.

Enter the following commands one at a time (to install the "IPTV Simple PVR"):

apt-cache search kodi-pvr

sudo apt-get install kodi-pvr-iptvsimple

Once complete, type "exit" (without the quotation marks) to get back into Retropie.

Scroll to Ports then choose Kodi.

In Kodi, DO NOT go to PVR's. If you do you will see it is blank and will get angry and think what you did in fact did not work.

Instead, go to "Add-Ons" then "My Add-Ons" and view "All" and you will see the IPTV simple client. Go to it and then Enable it as most likely it will be Disabled to begin with.

Voila!

If you know how to use IPTV then go ahead and set it up.

Take Care!

Hi all.

I'm fairly new to Retropie etc. and I realise this is an old thread, but just in case this helps someone else. I have been trying to run vice xvic with 16k expansion as some ROMs seemed to require this, they were just failing to load and showing error. I read a bunch of posts on the forum suggesting that a separate run command could be placed in emulators.cfg file with a command line switch (https://retropie.org.uk/forum/topic/1052/vic20-cartridge-launching/3) but everything I tried failed except this:

vice-xvic = "/opt/retropie/emulators/vice/bin/vice.sh xvic %ROM%"
vice-xvic-expanded = "/opt/retropie/emulators/vice/bin/vice.sh xvic %ROM% -memory all"
vice-xvic-cart = "/opt/retropie/emulators/vice/bin/vice.sh xvic %ROM% -cartgeneric"

This was added to my /opt/retropie/configs/vic20/emulators.cfg file and now my vic20 ROMs load (once I select vice-xvic-expanded on the load screen.) Any Vic 20 ROMS that don't like the memory expansion should use the default vice-xvic.

It seems the issues with some of the command line switch suggestions I was copying from the forum were that single quotes don't work in these commands e.g. = "/opt/retropie/emulators/vice/bin/vice.sh 'xvic -cartgeneric' %ROM% " and %ROM% should come before the switch i.e. %ROM% -memory all .... not .... -memory all %ROM%

If anyone is wondering how I have a separate vic20 folder instead of this just being under the default c64, I followed these instructions: https://ianwilliamhill.co.uk/c16rp/index.php

I hope this helps!

I solved the issue.

If anyone else has this problem, you need to make sure which WM you're using. Apparently if your WM is Wayland, and RetroPie tries to use X11 to run the game, it won't work. Disabling Wayland solves this particular issue. To do so do the following:

sudo /etc/gdm3/custom.conf

Find

#WaylandEnable=false

And uncomment it by changing it to

WaylandEnable=false

Save, exit, and reboot and Ubuntu will use X11 instead of Wayland and that solved the problem for me. I'm not sure that this is a common problem, and I'm not entirely sure how I ended up using Wayland, but if anyone else has this problem the solution will be here.