Main > Raspberry Pi & Dev Board

Does the Ultrastik 360 work with a Pi?

<< < (6/9) > >>

soonerdoc:

--- Quote from: ZoOl007 on May 26, 2017, 07:08:48 am ---Hi,

I uploaded 0.4.0.3 beta1. It contains restrictor support for U360's.
The documentation is in the xml file. Be sure to read the change log. It contains important information concerning the process monitoring that could impact pre 0.4.0.3 beta1 users.
No big deal, just important.

kind regards.

--- End quote ---

You all are amazing.  Uninstalled 0.4.0.1 that I had on there and installed 0.4.0.3.  Qbert still seems to be working well.  Getting a second stick and restrictor plates on tuesday and will get them installed.

Was a little confused about the process monitoring regarding emulation station.  Everything seems to be working correctly.  Is there anything I am supposed to be doing extra with 0.4.0.3 regarding the discussion in the .xml file about it recognizing emulationstation vs. emulationstatio ?

Thanks again for all your help.

ZoOl007:
 Is there anything I am supposed to be doing extra with 0.4.0.3 regarding the discussion in the .xml file about it recognizing emulationstation vs. emulationstatio

-> No. I adapted the xml accordingly in advance. I just wrote that to emphasize the fact that the process monitoring sees (a minority of) processes differently than before and 'emulationstation' just happens to be one of those processes.

soonerdoc:
Still getting this tweaked, but have a question.  Everytime I am finished and go to shutdown system option, when system shuts down a message pops up that says:

"A stop job is running for RGBcommander arcade led and joystick daemon" with a 1min 30s timer.

Do I need to wait the minute and a half when shutting down everytime?  Don't want to corrupt the memory card or something.

Thanks

ZoOl007:
No you don't have to wait. I am not sure what happens. I had the same from time to time when I used the init.d system. that's why 0.4.0.3 beta1 doesn't use that any more so it should not happen I guess.
Maybe something has been left over from the 0.4.0.1 beta1 you were using...

open a root prompt and type 'update-rc.d rgbcmdd remove' - that should get rid of the old system should it still be in place... you always have to deinstall - you shouldn't just install a new release over an existing one atm (should you have done that)

it is also safe to remove the automatically generated rgbcmdd.service file should it still exist (systemd acts as a wrapper around old init.d scripts and created the rgbcmdd.service file without the user knowing).
You can search for it by 'find / -name rgbcmdd.service'

0.4.0.3 beta1 uses systemd now so the following commands should give you some insight and they should respond correctly :
systemctl -l status rgbcommander.service
systemctl -l start rgbcommander.service
systemctl -l stop rgbcommander.service

see if this helps you any furhter

brett4got:
Hoping someone can help me identify what I am doing wrong. I have 2 U360's plugged in to a Pi3 running RetroPi 4.2, when EmulationStation launches it sees 2 gamepads and when I hold a button down it recognizes the controller as an UltraStik 360. The problem is it then tries to configure the controller by having me map the d-pad, and buttons but no matter what I do by moving the joystick OR hitting any of the buttons, the setup screen does not respond and I ultimately have to hit F4 to exit ES to the command prompt.

I have RGBCommander and when I run jstest on the controllers it sees the button presses and joystick directions perfectly.

So what can I do to get ES to configure the U360's? Ideally I want to be able to use the controller to navigate the menus inside EmulationStation as well.

Thanks for any insight.

Navigation

[0] Message Index

[#] Next page

[*] Previous page