Posts made by rsn8887

@voljega: Nice job getting this to work.

I am pretty sure some of the whdload .lha files often have amiga filenames that can only be uncompressed correctly in an Amiga filesystem.

So, ideally, I think the emulator should take the .lha file as a launch argument and automatically uncompress into a .hdf file to ensure filenames are all correct. No need for .uae file then. It could be read automatically for custom config if it exists, but that's it. This was already solved by FS-UAE.

I also think that a virtual keyboard, analog stick mouse control and gamepad control of the menu are necessary for this to become usable in a typical Pi setting in front of the TV.

I don't think many users have a keyboard and mouse connected to their Pi. It seems the spirit of recalbox is very much to have everything controllable with a gamepad. I for sure don't have a keyboard and mouse connected, that's really the last thing I want when I am in front of my TV.

BTW: Shameless plug, but for anyone who has a cfw VitaTV, UAE4All2 is also a nice alternative for Amiga emulation on the TV. It already has a virtual keyboard, analog joystick mouse, custom control configs for four controllers, etc. etc.

I am now on latest 4.1.0 downloaded .img. And I am getting the "wi-fi password turns into gibberish after re-boot" bug. The wifi password automatically gets corrupted everytime I reboot.

In recalbox.config, it becomes "enc:somegibberish" The funny thing is, I just rebooted and even though the pw is gibberish, my recalbox did connect succesfully to wi-fi!

Hmm after re-burning the latest .img it seems to work now, and I did get the changelog display about the newest manager, as I should, and I could select OK and the controller (PS3 Dualshock) is now working.

Maybe the problem was that I was not using the very latest unstable build.

My updates are set to "unstable".

• Recalbox tells me there is an update.
• I go to update in the menu
• "working" for 30 minutes
• tells me it needs to reboot
• after reboot, tells me there is an update
• controllers don't work I cannot click OK
• keyboard doesn't work
• recalbox host not accessible on network (network connection not working)
• taking out sd card, and using Applie-Pie, burn latest img.
• it works again

This happened to me twice. First it happened two weeks ago, and now again just yesterday.

Extremely annoying.

Oh and I have a USB stick connected that has all my roms on it, so re-burning the .img is not SUCH a big deal luckily. This is a raspberry Pi 3.

I get the img from https://archive.recalbox.com/updates/v1.0/unstable/

The changelog here
https://github.com/recalbox/recalbox-buildroot/blob/32cd9deafb9870a5e6b5ef056dfefae08f07c860/CHANGELOG.md
seems very broken. It doesn't have changes for 4.0.0 stable, 4.0.1 stable or 4.0.2 stable, but then it DOES list all of the changes for [unreleased][unreleased]????

Is there an up-to-date changelog? Maybe it should be a link on the main webpage, so users can quickly see new changes.

Why isn't the changelog on the wiki here https://github.com/recalbox/recalbox-os/wiki

When I updated my recalbox, a changelog was briefly shown. Where is that on the web?

Since Bubble Bobble (Arcade) emulation in Mame is only accurate since 0.107u3 or later (2006+), the version currently in recalbox is inaccurate.

See the entry for Bubble Bobble by Nicola Salmoria in Mameinfo.dat (search for $info=bublbobl and read the entry under "- 5th August 2006")

Is there a way to play the accurate emulation in recalbox?

I looked at the source of Bubble Bobble in Final Burn and it looks like it might be also be a hack with wrong monster behaviour etc, like in the old Mame, because it uses the MCU 68705 chip (the wrong chip).

Yes I found this old issue on Github:

https://github.com/recalbox/recalbox-os/issues/914

It basically explains it: Mame buttons are inconsistently assigned and weird inside the mame drivers itself.

One would think that after decades of development, the Mame coders would have figured this stuff out and standardized it. But no...

At least is is correct in Finalburn.

I noticed the buttons are assigned differently in Finalburn (libretro) and Mame (libretro).

I played Rainbow Islands. In Finalburn, B is jump and Y is shoot. In Mame B is shoot and Y is jump? Finalburn is the way it should be. Mame feels very awkward/wrong.

Is there any way to make these assignments consistent between the emulators?

I suspect it might just be some wrong button assignment in the Mame core...

@rsn8887 I fixed it by login into recalbox via ssh and editing my config.txt file, uncommenting the hdmi_group line as detailed here:
https://github.com/recalbox/recalbox-os/wiki/Video-configuration-detailled-(EN)

I have three TVs with HDMI in, two of them display the recalbox picture just fine, but the third one does not. The picture is completely off center (see attached photo) with a large black bar on the left.

Is there an advanced configuration option in Recalbox to center the picture somehow. I now the TV works fine with Vita TV, another 720p source, so I am pretty sure it is a bug in the video out in recalbox. Maybe it is using some non-standard resolution?

I am using Recalbox 4.0.0 on Rpi3 (release version).

Is there a linux module to have a virtual keyboard that is system-wide and controllable just with a gamepad?

This would be a great feature for recalbox. Of course, some hotkey combo is needed to enable the virtual keyboard.

Especially with several computer emulations that will soon be added, such a virtual keyboard would take care of those.

Of course, a virtual keyboard service needs to exist. I did a quick google search but found nothing. But I would hope such a thing already exists, at least as a kind of accessibility feature?

Well, I was a bit fast now there are problems with N64 scraping. It gives "unknown image format" errors. Worked fine 2 hours ago.

"GDB" scraping works fine, so it is again some problem with "ss" (maybe ss ist just inherently unstable?)

Yup it works just fine again

@paradadf
Other systems show the same problem, but some don't. For example gb scraped fine completely through all roms, but gba and n64 didn't. I tried to remove a few roms where the error appears, but then it just happens at a later rom. Judging from that 504 error message, it seems to have something to do with mirror.screenscraper.fr . As I said it all worked perfectly on the weekend a few days ago.

Worked two days ago, now broken:
ERR: error processing H:\EmuRoms\Recalbox\recalbox\roms\gba\2 Game Pack! - Matchbox Missions - Emergency Response + Air, Land and Sea Rescue (USA).zip: 504 from $s%!(EXTRA string=http://mirror.screenscraper.fr/api/mediaJeu.php?crc=&devid=&devpassword=&jeuid=83014&maxwidth=400&md5=&media=ss&mediaformat=png&sha1=&softname=sselph%2Fscraper&systemeid=12)
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x14 pc=0x408fe7]

goroutine 31 [running]:
panic(0x7e9580, 0x1137e030)
/usr/local/go/src/runtime/panic.go:500 +0x331
main.crawlROMs.func2(0x120b29d0, 0x11dcb540, 0x0, 0x120b29c0, 0x1287e0c0, 0x1287e040)
/home/sselph/go/src/github.com/sselph/scraper/scraper.go:295 +0x527
created by main.crawlROMs
/home/sselph/go/src/github.com/sselph/scraper/scraper.go:328 +0xbd7

I already have preview images for all my games. They are named the same name as the game rimfile but with a different ending.

Is there a way to display these without editing any game list and without scraping. The scraper is super slow and doesn't recognize most of my games. I would rather use my own preview images.

Can I rename all my images to some standard names and put them in a certain folder?

Will recalbox display those images or is there no way around entering each image filename in the gamelist?