I just found out about this while installing retroarch on my tablet, super impressed with it, i really hope this will be included into retropie sometime soon.
Thanks for the instructions of adding it ourselves.
@shift I don't have dedicated threads for each individual lr-mess system I run, but the short answer is "more-or-less all of them".
Just to rattle off some of the ones I've tried on my Pi, with decent-to-perfect performance:
Epoch Super Cassette Vision
Various plug-and-play systems (both "official" and bootlegs)
Fujitsu FM Towns
Once you get down how the core works (which admittedly is a bit of a nightmare), it's insanely versatile since it runs all the same systems as modern standalone MAME (according to the current docs, that's roughly 32,000; that link at the top is a good few years out of date). Arguably the most powerful core in all of RetroPie.
Many thanks for your advice @BuZz. I modified the startup script as you mentioned and it still works.
My understanding is that BasiliskII should ever load the 'keycodes' file so the host keyboard layout (the one configured in Raspbian/RetroPie, here) is taken into account, whatever international layout it is. Without the 'keycodes' file, only US-layout would be recognized and typing from another host keyboard layout (i.e French AZERTY, German QWERTZ...) under Basilisk would produce weird result. If I understand well, the keycodes file contains the USB keycode for any environment BasiliskII has been built for (so, the Linux framebuffer, here).
By the way, loading or not this keycodes files every time BasiliskII starts is not necessarily the most important point. With your permission, I would rather suggest that there is something to fix somewhere, since BasiliskII doesn't open this file when it is told to do so from its basiliskii.cfg config file.
Nuance barely worked properly on Windows back in 2007. Unless someone's been working on making it work a lot better and on ARM, I don't see that happening. You'd have a better chance of hoping MAME handles it soon.