>i3-6100
Much better. I ran a i3-6100U on one of my setups before, so I know they run fine with older NVidia and Intel HD graphics. However, as you are probably aware, NVidia's closed-set drivers support for Linux isn't the best, especially with newer cards. You might be better served with going with the Intel HD graphics for now: http://www.lakka.tv/doc/Hardware-support/
From the lakka.tv website:
> Lakka is the official Linux distribution of RetroArch and the libretro ecosystem.
Lakka is a custom Linux distribution for running RetroArch.
I'm guessing the mounted folder is causing the problems. Try looking inside the playlist file and see what the rom's folder location gets set to, and manually entering the correct location if necessary. The playlist format is documented here.
Otherwise you could try locally storing the roms on the RPi3, which should work without any complications.
I use the HP Mini PC's. You can upgrade them with lots of storage and RAM, out have multiple drives installed if you want to carry a massive collection.
You can get something like this: https://www.amazon.ca/HP-EliteDesk-Computer-Windows-Renewed/dp/B07Q1DL6LV/ref=mp_s_a_1_6?dchild=1&qid=1627366067&refinements=p_89%3AHP&s=pc&sr=1-6
I paid a bit more for mine, but got the i7 6700 processor with 16gb of RAM, but even what I outlined above will handle titles up to the PS2 without really any issues. It does slow down with PSP a little bit, but if you muck with the settings enough you can usually get something very close to full speed. GameCube seems to work perfectly, same with PS2.
I can recommend RetroPie, they have a nice script to handle easy installation, config and even things like samba shares.
https://retropie.org.uk/docs/Debian/
Batocera is also a nice alternative if you want the "console" feel out of the box.
I purchased the original Retroid Pocket, it's okay, but in hindsight I think it would have been better to build something myself.
The hardware recommended by recalbox below would probably support lakka?
Check this link out . I know you probably wanted this to be plug and play, but I think as of now Lakka is not the best for beginners.
Look, it's a bit of trouble to go hunting for solutions when you have no idea what you're looking for. I think you should look around for other emulation distros, maybe you'll have more luck going for something else instead of tinkering with partitions. However, you can also see this as a chance to learn a bit more about computers - I sure did when fussing around work Linux a few years ago.
Anyways, have fun!
RetroPie minus the faff. Basically all the settings are optimised straight out the box and if you want to tweak them further you do so in the UI, not a CFG file.
Can be dual booted on a PC too.
Thanks, do you know where i can download the last version suppported for wetek play? Searching the web the old link for wetek is dead http://www.lakka.tv/get/linux/wtk/
Do you think 3.0 is a great improvement since 2.3?
A couple of things:
1) Your CPU has no integrated graphics, so forget trying to use your motherboard's HDMI/DisplayPort out. Not going to use what isn't there.
2) An RTX 2070? Use the NVidia version, if you're not already. The flower usually indicates that your graphics card/drivers/chipset isn't compatible. The quickest way to find this out is, of course, is a log of what the program does when you try to use it. This might help: http://www.lakka.tv/doc/Troubleshooting-Lakka/
3) It has nothing to do with your ROMs or drives until you can't find your games, then it becomes a problem.
http://www.lakka.tv/doc/Network-settings/
follow the wifi command line instructions, obviously you have to be connected via ethernet first. this works BUT the setting doesnt seem to stick after a reboot. not sure why. after i reboot the pi/lakka i run the command "agent on" after entering the connmanctl prompt and it says "agent registered". i run it again immediately and it says "agent already registered" which means it is not registering after a reboot hence why the wifi adapter doesnt have an ip after a reboot.
You can (you can also access the filesystem by plugging the USB drive on a computer running Linux). I wonder if there's performance penalty, though...
my pi is running lakka. So it could also be related to how well Lakka is made.
You could try installing Lakka to a usb stick and see how it runs. Maybe windows(?) is just slowing down your computer too much.
I don't know how comfortable you are with compiling your own lakka version, but here it goes: http://www.lakka.tv/doc/Packaging-a-libretro-core-for-Lakka/
It's not easy, but maybe you'll find some solution out of it. Good luck!
Lakka uses a curated ROM set list. There is a database of "good" ROM titles for each emulated system - that database is based on the "No Intro" ROM packs you can find on line - they do this because the No Intro ROM packs are verified and follow a standard naming convention.
When you scan your ROMs, Lakka checks the name of the ROM against the database so see if it is a known-good ROM. If it is, it is added to the playlist for the Emulator that supports it. You can find the database files for the different emulators here:
https://github.com/libretro/libretro-database/tree/master/dat
Make sure you download the latest No Into packs you can find to maximize the chances of making a match when scanning ROM directories to build the playlists for each system. Sometimes you just have to change the name of your ROM to match the name in the database and rescan the file - check the size of the ROM vs the size listed in the DB to make sure you use the right name. Sometimes this doesn't work and you have to add the ROM into the playlist manually.
If you have odd or custom ROMs or ROMS that just can't be matched, you can edit the playlist for each system to add them in. They are located in the /Playlists directory. The documentation and format for the playlist files is found here:
http://www.lakka.tv/doc/Playlists/
You have to use a UNIX editor like VI or VIM to edit the playlist files because using a windows txt editor will result in unsupported characters breaking the file. Just follow the format you see for working ROMs to create entries for other ROMS. I have found that you can usually us DETECT for the emulator fields and that the checksum field is not really checked.
It's a known issue, unfortunately: https://github.com/libretro/Lakka-LibreELEC/issues/54
You can manually pair a PS4 controller using the instructions here: http://www.lakka.tv/doc/Wireless-Dualshock/
I've had some weird latency issues with PS4 controllers and the Odroid C2. It seems to only be an issue if you have more than one paired, though. Good luck!
> Main usage: NES, SNES, Sega Mega Drive/Genesis and possibly DOS emulation
this setup should work well for the platforms you list. you may have trouble with Playstation and N64, especially 3D heavy games.
> Is it a good idea to install Lakka on the internal flash memory and play games form a mounted USB drive?
This setup will work. Even the 4GB of flash memory should be able to store a lot of games on the platforms you listed.
Get some joypads and you'll be ready to enjoy some retro-fun!
The instructions worked for me: http://www.lakka.tv/doc/Wireless-Dualshock/
BUT: A and X Button are recognized as Up and Right, even after manual input assignment. No idea how to get the A Button recognized as the A-Button...
Still not working. Wired is the only way I can play. In one of the more recent updated they said With the money from the donations, I bought a wired Xbox One controller and a Dualshock 4. Both are now officially supported by Lakka, and have been tested on all the computers. Wireless support will come in a second time.
There has been an update after that, but it was to bring RetroArch 1.3.6 to the table, so in 1-2 more updates we may have wireless! (purely speculation on my part)
I would like to get eMMC because of the improved read/write but eMMC is also much more expensive than an SD card. I suppose once I get around to buying it I'll try out a 128GB microSD and report back with what happens.
As far as Bluetooth goes, I was curious about it because of the latest update: http://www.lakka.tv/articles/2016/05/03/new-major-release/
"The famous PS3 game controller becomes easier to use in Lakka. You can now use it wirelessly over bluetooth without having to go through that complex command line pairing anymore. Just enable bluetooth in the services, plug your controller once, wait a few seconds and unplug it. It should automatically pair and become usable to control the menu and play games."
This should still work even if I'm using a Bluetooth dongle in theory, right?
Oh, I do use the "Shutdown" option on the menu to power the unit off every time. But the problem is, the only way to restart it is to unplug and plug back in the usb cable, which is a pain in the ass and could possibly prematurely wear out the connection on the motherboard or the cable. That's why a switch on the cable is so handy - you just turn the switch off after shutdown, and simply turn the switch on again to start the Pi back up next time I fee like some retro gaming.
I ended up ordering this yesterday - hopefully it won't trigger the undervoltage warning.