@VictimRLSH Hm, a quick test shows it's not working at runtime (i.e. without rebooting the device). Maybe fiddling with tvservice would allow this - I'll have a to check more.

thank you
its greatly apreciated !

@sushisan I do agree with that. The code that fails was added later and I guess wasn't tested on older cmake. We can bump the cmake version but I don't mind if someone wants to make it work on older cmake too so long as it's easily maintainable. Eg Not having to adjusting the JSON cmake files if we upgrade that component to keep compatibility. Easier just to require a newer cmake.

@BuZz
I write the solution for my case. Maybe it could help someone

Pi4 model b
access point: TP-LINK RE450

Retropie, any version for some strange reason does not connect to the access point.

SOLUTION: I had to install an OPEN-WRT custom firmware on the access point.

Once rebooted and configured, everything works.

The strange thing, that the first time, with the firmware stock was connected perfectly, then you can not.

I'll try it again when I have access to several browser and back on my other computer.

Weird.

Hi mitu. Good info. Gives me an idea after all.

Also, being a moderator would you mind fixing the code quotes in my previous post? Sorry... when trying to edit it is saying I am spam.

It works, brilliant job thank you!

@iamoasis said in Double Dragon (MAME):

some spreadsheets that show games that have been tested on different emulators

Some entries in those spreadsheets are wrong though, because some of the testers didn't follow the "pick an emulator then pick the right romsets for that emulator" rule.

You're not running into issues with building the N64 emulator mupen64plus? It's only happening on Debian Stretch (x86-64) but it could be my setup so that's why I'm asking. It's requiring a newer version of cmake than what's available:

/home/pi/RetroPie-Setup/tmp/build/mupen64plus/GLideN64/projects/cmake /home/pi/RetroPie-Setup/tmp/build/mupen64plus /home/pi/RetroPie-Setup CMake Error at CMakeLists.txt:1 (cmake_minimum_required): CMake 3.9 or higher is required. You are running version 3.7.2

@mitu ah yeah, my bad. Guess I'll have to wait for the next version for source to be 1.8.5, or I'll have to modify the setup script.

@SolemnSpirit Thanks that helped!, the moment i remove the key_mgmt, i was able to connect to the wireless! :D i appreciate you posting this!

@mitu Never used Reset, at least that I know of. But thanks for that tip. I'll be sure to avoid it.

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices.
Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working.

Okay. I can see that now, with access to the computer again. (Remember, it's in a different place than my desktop, that I use for posting.) Thanks!

Now I have the primary Mini PAC set in Keyboard Mode and I see that it recognizes the Mini PACs as devices, but also recognizes the devices on them separately. It looks like keyboard in the Mini PAC gets an event node. Interestingly, the Ultimarc SpinTrak (the spinner) gets Event 5, not 6. When I test with cat /dev/input/event6 I get input from the spinner and I don't with event5.

But this shows me that some of the devices are broken down into multiple devices and explains why something else is "in between" the trackball and the spinner.

As a side note, even though this is a built in function for RetroArch, I've now done what the manufacturer claims can't be done. Xtensions claims that, in D Input Mode, you can only have one mouse device, so you can have the trackball (somehow that always ends up as the one to take priority) but not the spinner in that mode. I'll be writing them about that!

When I have all my questions worked out, I'm going to either write up a few blog pages or make a few videos for others with the same issues. I'm hoping that they will use the so their other customers can get this working, too.

Running in a desktop environment is not supported on a Pi - I guess the relevant topic is https://retropie.org.uk/forum/topic/3/read-this-first:

Do not report issues with running on a RPI4 - it's not yet officially supported, and there are many 3rd party guides with incorrect instructions out there.

If you have a Pi4, you can install manually over Raspbian Lite - https://retropie.org.uk/docs/Manual-Installation/ - but remember that Pi4 support is a work in progress.

@dalekman27 Good to hear! Enjoy :)

Thanks!

I never played fighting games much - always liked the spaceship games - so that explains why I didn't even think of that.

@felifel We don't support 3rd party images - is clearly outlined in the https://retropie.org.uk/forum/topic/3/read-this-first topic.
Use the image from retropie.org.uk/download to install, update your RetroPie installation and try again installing the emulator.

Haha yes, it works :D Simple solution is:

First of all - if you have your copy of .sav file (or any other containing your save state), backup it to have an original one in case of losing all saved data.

Open rom in Visual Boy Advance, restore you save and create save state using built in saving mechanism.
Now close the game and remove in-game save file - file which is a copy of your original state file.
Next open game in Visual Boy Advance and load state saved in built it saving mechanism.
Go to VBA Options > Emulator > Save Type and change it to SRAM
Perform in-game saving. New .sav file will be created in folder when your game was stored.
Rename file with extesion for "your_game_name.srm".
Copy it to Retropie.

After these steps I was able to open my save state from Pocket-Go on my GPICASE :)

BTW:
There is a possibility that @lostless sugesstion will work to but if not, you need to perfrom above steps.

BTW2:
Visual Boy Advance saves in-game states files as a .sav file, so you are able to copy you states from VBA to Retroflag also.

Thank you guys!

The blueooth packages are part of the OS (Raspbian) - they can be upgraded if a new version is released by the upstream Raspbian project and can be installed with the apt utility, or just choosing to update your OS packages from RetroPie-Setup when you do an upgrade.