Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • robboman
    Participant
    Post count: 8

    To all.. THANKS! I found all my remaining answers in this thread.

    I’ve been struggling for a while to get trackball and spinner to both work. They now both work perfectly, just the way I want. And btw.. they work in Mame4All too, as well as AdvMame.

    For starters, Mame4All is coded to prevent mouse from working at all when there is a js (gamepad, joypad, etc) connected to the system. I don’t use any gamepads (this is an arcade cab). I expected my Ipac2 to appear as a keyboard and mouse ONLY, but for some reason it was causing a js0 device to appear in /dev/input, along with mouse0 and mouse1. When js* is present, there is NO way to get a Mame4All mouse device working.

    AdvMame doesn’t care if there’s a js0 present, so that’s one workaround.

    But Andy Warne from Ultimarc was quick to respond to my emails, and today he emailed me a different firmware for my IPac2 that completely removes the js0. I flashed it with Winipac utility. Now my Ipac appears as just a keyboard and 2 mouse like I want, no js0. Mame4All FINALLY works with my trackball and spinner without changing anything else!

    I found right away that Mame4All just sums together both mouse0 (trackball) and mouse1 (spinner).. I loaded up Arkanoid and both controls work at the same time, which might be OK but is is not exactly what I want.

    I noticed that in AdvMame 0.94, Arkanoid worked with my trackball.. the spinner did nothing. I wanted the spinner for Arkanoid, and the tball to do nothing. I was able to make this happen by editing the advmame .rc file:

    device_mouse raw

    device_raw_mousedev[0] /dev/input/mouse0
    device_raw_mousedev[1] /dev/input/mouse1
    device_raw_mousetype[0] ps2
    device_raw_mousetype[1] ps2

    … then down in the input_map section…

    input_map[p1_dialx] mouse[1,x]
    input_map[p1_dialy] mouse[1,y]

    … dial = spinner of course. Arkanoid, Tempest, etc use the ‘dial’ control. This specifies p1 dial to be mouse1 (because mouse0 is my trackball)

    … I also changed these to specify mouse0 (trackball) where needed:

    input_map[p1_mousex] mouse[0,x]
    input_map[p1_mousey] mouse[0,y]
    input_map[p1_trackballx] mouse[0,x]
    input_map[p1_trackbally] mouse[0,y]

    Now, if I load up Centipede or Missile Command the trackball works and the spinner does nothing. Vice\Versa when I load Ark or Tempest.

    Perfection!!!

    Summary:

    1). Mame4All: If you are using gamepads, no trackball/spinner for you. Keyboard and multiple mice works fine. If you have no gamepad and still don’t have any mouse, check to see if you have a mystery js0 or js1 entry in /dev/input. If you do,

    sudo rm js*

    But if the js0 comes right back when you reboot, and you happen to have an Ultimarc interface.. check with Ultimarc, this can be fixed in firmware.

    2). Confirm all your mouses, tballs, spinners actually work on your PI, and figure out which is mouse0, which is mouse1, etc.

    cat /dev/input/mouse0

    …then move the control you think is mouse0 to confirm, it should generate characters onscreen until you ctl-c to quit. Repeat for mouse1, etc.

    You can also try this command:

    ls -l /dev/input/by-id

    This will show you the device IDs and which mouse each one relates to.

    3). AdvMame: edit your /opt/retropie/configs/mame-advmame/(filename).rc to specify which controls are default for each function (as per above).

    A note about editing the .rc file for newbies:
    Make a backup file first (save with a new name). If you have even one character out of place it will prevent AdvMame from running at all.

    robboman
    Participant
    Post count: 8

    I’ve been running my RP 3 for days on end, no freezes here.

    robboman
    Participant
    Post count: 8

    [quote=120616]Yeah that explains it. Problem is dependencies for omxplayer aren’t being met before its called to run resulting in a dbus error. Putting a sleep parametre on omxplayer is a simple workaround for it at least until logic in the code is improved.

    [/quote]

    Thanks, it worked! I put one new line just before the onxplayer line in etc/init.d/asplashscreen:

    sleep 5

    Now my splashscreen video plays flawlessly every boot. And just as importantly it is no longer continuously writing 5 lines per second into var/log/syslog indefinitely, while onxplayer is still consuming resources. It opens, plays and closes cleanly as it should, and the last related line in the log file is:

    Mar 17 01:09:32 retropie asplashscreen[83]: have a nice day ;)

    Nice. I am having a nice day :)

    robboman
    Participant
    Post count: 8

    [quote=120562]If it is indeed a boot sequence issue a simple workaround would be to add a sleep parametre to the asplashscreen script to delay calling omxplayer.

    Without any boot logs though I can’t advise.

    [/quote]

    My /var/log/syslog is MASSIVE and contains the following line, repeating 4 times a second for hours on end.. this is thousands of log lines

    Mar 16 01:25:00 retropie asplashscreen[82]: waiting for dbus address to appear

    Are there any other logs I should look at? I don’t know much.. just browsing around

    robboman
    Participant
    Post count: 8

    There’s another thread about this:
    http://www.petrockblock.com/forums/topic/splash-video-not-loading-anymore/

    …And to be thorough, here’s a copy of my long post for this thread:

    Just chiming in.. I’m having all the same issues on 3.6.

    I have an old Pi B+, and a spanky new Pi 3. I tested on both, and it seems the problem is worse on the Pi 3.

    On the old Pi, I noticed the video would mostly work, but occasionally fail to play, and sometimes it would play but with no audio. I also noticed that when it failed, it was always on cold powerup. When I’d warm reboot the Pi it would always work.

    On the new Pi 3, it worked once I think.. then it failed every time, cold boot or warm reboot.

    So my un-technical noob theory is it has something to do with the start sequence and various things not firing up in expected, perfect order. Worse on the 3 because everything loads so much faster.

    Hope the devs can fix it, because it’s pretty cool when it all works :)

    EDIT: MORE info.. maybe related?

    First.. I switched to a static picture splashscreen due to the above issue. Now when I boot the Pi 3, I see the 4 berrys, a few lines, then my splashscreen pic, then the Emulationstation loading screen. It all appears fine, but if I IMMEDIATELY navigate into a system menu and load up a rom, I see my splash pic pop up again before the rom loads. Then the controls freeze up and the screen goes BLACK with only this text in the upper left:

    map: vt02 => fb0

    If the rom is making sound, I hear it playing in the background, so I know MAME is still running, but I have no keyboard or control input. I was able to SSH in, but sudo reboot now did NOTHING. So I had to yank the plug.

    After reboot, if I give it a couple minutes after the menu loads before launching anything, everything seems stable.

    robboman
    Participant
    Post count: 8

    Just chiming in.. I’m having all the same issues on 3.6.

    I have an old Pi B+, and a spanky new Pi 3. I tested on both, and it seems the problem is worse on the Pi 3.

    On the old Pi, I noticed the video would mostly work, but occasionally fail to play, and sometimes it would play but with no audio. I also noticed that when it failed, it was always on cold powerup. When I’d warm reboot the Pi it would always work.

    On the new Pi 3, it worked once I think.. then it failed every time, cold boot or warm reboot.

    So my un-technical noob theory is it has something to do with the start sequence and various things not firing up in expected, perfect order. Worse on the 3 because everything loads so much faster.

    Hope the devs can fix it, because it’s pretty cool when it all works :)

    EDIT: MORE info.. maybe related?

    First.. I switched to a static picture splashscreen due to the above issue. Now when I boot the Pi 3, I see the 4 berrys, a few lines, then my splashscreen pic, then the Emulationstation loading screen. It all appears fine, but if I IMMEDIATELY navigate into a system menu and load up a rom, I see my splash pic pop up again before the rom loads. Then the controls freeze up and the screen goes BLACK with only this text in the upper left:

    map: vt02 => fb0

    If the rom is making sound, I hear it playing in the background, so I know MAME is still running, but I have no keyboard or control input. I was able to SSH in, but sudo reboot now did NOTHING. So I had to yank the plug.

    After reboot, if I give it a couple minutes after the menu loads before launching anything, everything seems stable.

    robboman
    Participant
    Post count: 8

    3rd this.. I spent a lot of hours repairing my old Happ trackball and wiring it up only to find it doesn’t work – do I need to run a different MAME emulator besides MAME4ALL?

    Thanks

Viewing 7 posts - 1 through 7 (of 7 total)