Thanks @ian57 for the clarification.

Kodi and Samba 1.0 could be the issue. I can't find out what smb-version my NAS (a LaCie 5big network 2) has on board. Though I don't have any issues connecting Win10, Mac Catalina or Ubuntu Focal to it, which seems strange is smb 1.0 is such a big problem.

exFat is actually good news, concerning bigger files. But even on exfat it is not possible to have multiple files with the same name but different uppercase/lowercase letters - they would still be treated as the same file! (unlike on linux filesystems for example).
So giving errors for not finding files according to different case sentitivity is simply a dumb design decision.

Perhaps I will go through all the pain again and try to set up recalbox 7.1 on my pi. Lockdown gives me plenty of time anyway. Just looking for the good (no, I don't say "positive" ) things.

Danke @Strykjar für die Lösung! Hatte das selbe Problem und habs jetzt nach deiner Anleitung geändert und jetzt funktioniert wieder alles!

@zing
That did it. Using Select as Hotkey resolves the "slow motion after loading state" problem.

Thanks for the tips.

Still, the gamelist.xml in my ports folder resets at each power cycle.

It only contains the preset info (which is Doom 1, Sigil and Wolfenstein).
Quake 1 does not show up at all.
Quake mission packs, Doom 2 and Flashback (which are all listed) have no icon and no description. I can scrape them, or set the info by hand, but after the next power cycle of Recalbox, the info is gone for good...

Concerning the save problem: I actually did a fresh install without my previous settings - except the media and gamelist.xml files containing my rom infos (which should not interfere with gameplay itself, 'cause there are no gameplay settings stored in these). I disabled overlay, rewind, shaders, etc. No change.

I still have to press for state load 2 times: 1st it loads the state and stutters. 2nd it does not load anything but stuttering is gone.

However: I set Hotkey to R3. This means, loading a state is R3+X. Does this combination do anything else in a vanilla installation? Like starting recording or something? Perhaps thats my issue.

So, after a lot of tinkering, my Recalbox 7.2.1 is now running games smooth again on my Raspberry Pi 3B+.
I had to force it to 720p and change the audio_pwm_mode in /boot/recalbox-user-config.txt by adding:

hdmi_group=1
hdmi_mode=4
audio_pwm_mode=0

(I don't know if the audio_pwm_mode setting was really necessary, but afterwards it ran smoothly, while before even SNES was barely playable)

Now 2 primary issues remain:

• I tried to add some games to the /roms/ports folder, like Doom II and the Mission Discs from Quake 1 (I own all of these).
  The games run fine, however, the gamelist.xml is always reset after a system reboot and does not save my entries about these games.
  Why is that so?

• Also, I don't want to see all the preinstalled games (I don't care for the Atari and Sinclair things), except the "ports" (especially cave story). Is that somehow possible? By hiding preinstalled games everything is hidden...

• The other issue is, If I load a state save in any game (independent of emulator; I tried SNES, PSX, etc.) the game begins to stutter, until I press the "load save state" button combination a second time! Instead of (re-)loading the state, the game now runs smoothly.
  Why do I have to do these double-pressing of the button combination?

Thanks a bunch!

Thanks @ian57 for the clarification.

Kodi and Samba 1.0 could be the issue. I can't find out what smb-version my NAS (a LaCie 5big network 2) has on board. Though I don't have any issues connecting Win10, Mac Catalina or Ubuntu Focal to it, which seems strange is smb 1.0 is such a big problem.

exFat is actually good news, concerning bigger files. But even on exfat it is not possible to have multiple files with the same name but different uppercase/lowercase letters - they would still be treated as the same file! (unlike on linux filesystems for example).
So giving errors for not finding files according to different case sentitivity is simply a dumb design decision.

Perhaps I will go through all the pain again and try to set up recalbox 7.1 on my pi. Lockdown gives me plenty of time anyway. Just looking for the good (no, I don't say "positive" ) things.

No upgrade path from 6.x is very sad
Tried a new install of 7.1 anyway.

• a lot of my bios files which did fine on 6.1 are now invalid - because 7.1 looks for CASE SENSITIVE FILENAMES! Why would you do that on a FAT file system, which has no real case sensitivity? After renaming them, most work. Some are still invalid (PCEngine for example)
• Kodi 18.9 does not connect to my samba share. I don't know why, it works fine with Kodi 17 on RecalBox 6.1...
• My IR remote does not work in Kodi any more (again). Going through the whole IR setup process is too much work for me now ...

so, in the end, too much work for no apparent gain. I'll pass this release. Thanks anyway for the effort.

File found. Edited. Everything fine! Thanks again for the help!

Ah, so it was relocated! Perfect, will test this as soon as possible!

I am missing the file .\share\system.emulationstation\es_systems.cfg

this file defined which emulator or file types get used for the different platforms. It was able to edit this file to, for example, exclude certain file types from the automatic detection (important for PSX-games with individual audio track files, so they are not scraped multiple times) or for defining specific emulator cores for certain platforms (I did that for MAME, so i could combine my arcade and neogeo collections)

Has es_systems.cfg just been relocated or was it removed from the new release on purpose?

@paradadf said in Kodi 17 IR Remote:

@fonzman would you mind creating a Merge Request (MR) on gitlab to add those missing parameters by default?

https://gitlab.com/recalbox/recalbox/blob/master/board/recalbox/fsoverlay/recalbox/scripts/kodilauncher.sh#L49

done

Thank you paradadf, I know this faq.
I followed it some time ago when I configured lirc for Kodi 15 (back with recalbox 3.x or 4.0?), and made updates to Kodi 16.2 (with recalbox 4.1).
As I said, buildroot OS is recognizing my IR inputs also in Recalbox 6.0.
See this from my current setup:
irw
0000000077e1d0e4 00 KEY_UP Appleremote
0000000077e1d0e4 01 KEY_UP Appleremote
0000000077e1b0e4 00 KEY_DOWN Appleremote
0000000077e1b0e4 01 KEY_DOWN Appleremote
0000000077e1e0e4 00 KEY_RIGHT Appleremote
0000000077e1e0e4 01 KEY_RIGHT Appleremote
0000000077e110e4 00 KEY_LEFT Appleremote
0000000077e110e4 01 KEY_LEFT Appleremote
0000000077e110e4 02 KEY_LEFT Appleremote
0000000077e120e4 00 KEY_PLAY Appleremote
0000000077e120e4 01 KEY_PLAY Appleremote
0000000077e140e4 00 KEY_MENU Appleremote
0000000077e140e4 01 KEY_MENU Appleremote

only in Kodi no button presses are registered. And as I wrote in my last post, Kodi 16.2 (on Recalbox 4.1) has these 2 lines in the kodi.log:
14:03:48 T:1836053472 INFO: LIRC Process: using: /var/run/lirc/lircd
14:03:48 T:1836053472 INFO: LIRC Connect: successfully started

But they are missing from the kodi.log in Kodi 17.6 under Recalbox 6.0!

For me it seems Kodi starts without LIRC support. Can I somehow enable it? What does Recalbox exactly do when I press "Start Kodi" in the emulationstation-menu?

SOLVED!!

On Recalbox 6.0 Kodi 17.6 does ACTUALLY start without IR support! To rectify this, follow these steps:

• ssh to your recalbox
• make your system writeable with mount -o remount,rw /
• edit line 49 in /recalbox/scripts/kodilauncher.sh to look like this (changes are bold):
  LD_LIBRARY_PATH="/usr/lib/mysql" /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /var/run/lirc/lircd
• restart