Bugs in 8 beta 9
  • nachito83
    Hello,
    At first congratulation for your great work with piplay.
    I have 2 problems with the new beta 9:
    - The joystick doesn't work in mame4all. I look up in the code and I think the is no transformation file for this emulator.
    - The wifi configuration doesn't have sudo permissions to overwrite the wifi config files and It doesn't work. I have solved it executing the script as sudo.
  • mholgatemmholgatem
    mame4all is an exception to the controller setup utility. it has it's own built-in controller setup. When you run a game, you need to press 'tab', then you can set up controls.
  • krayzielilsmoki
    I haven't done extensive testing but I think the genesis controller setup doesn't completely work. The start button got mapped right but when I try to press the B or C button it doesn't work. Maybe it's just me.
  • candyman
    My son and I are just starting to setup a reto gaming machine with our B+ pi. piplay is pretty awesome, so kudos to all the hard work you've done. I just started hacking today, so I apologize if some of these are know/covered elsewhere.

    - I also ran into the wifi bug and also solved it by running the script with sudo like nachito83. I suspect having the launcher run it with sudo would be an easy fix.
    - Using a mouse in launchmenu.py can crash it randomly. My fix was to just disconnect the mouse.
    - I'm having some trouble using a wired xbox 360 controller. Running toggle_xbox_controller.sh allows me to use the controller in launchmenu.py, but it does not setup the emulators. If I hit "Tab" and configure "nes" (fceux) manually I get the following behaviors:
    1. No matter what button I pick for A or B it seems to always set
    SDL.Input.GamePad.0A = 0
    SDL.Input.GamePad.0B = 1
    SDL.Input.GamePad.0TurboA = 0
    SDL.Input.GamePad.0TurboB = 0

    This seems to have the effect of always making the NES "B" button a "turbo B" button.
    2. Attempting to set *EXIT_PROGRAM to any joystick button results in a scenario where I can't escape fceux back to piplay's launchmenu.py. If I press ESC (the default keymap 27) on the keyboard when I get to that step I can still use the keyboard to escape.
    3. The D-PAD buttons don't work if I attempt to configure them from inside launchmenu.py. Instead I can only configure the left analog stick. However, I can get them to be recognized if I run controller_setup/configure.py if I exit to the shell and have console access (didn't work via SSH since I didn't have X-Fowarding or $DISPLAY set).

    If there are some docs that you could point me at that would be awesome. Also if you've just fixed a bunch of bugs and I should pull the code from github I'm cool with that too.
  • mholgatemmholgatem
    -The wifi bug will get fixed in the next update. I'm not sure why it used to work but now it doesn't.
    -I fixed the error with the mouse (although right now the mouse isn't 100% usable, it doesn't work in popup menus yet)
    -I'll have to look into the xbox 360 controller setup. I think that I have a spare one sitting around somewhere.

    Some of the emulators only support keyboard keys for functions like 'esc'. we plan on going through the emulators and trying to somewhat standardize them relatively soon.

    I'll take a look into what the difference is between controller_setup/configure.py and what is in piplay. I have the feeling that it has to do with the pygame JOYHATMOTION

    Thanks for the thorough list, I'll let you know what I come up with. Shea is at PyCon until monday, so it's just me for the weekend.
  • mholgatemmholgatem
    @candyman - I did some testing. I don't think that your xbox controller is getting activated. With the normal 'toggle controller', it add a line to your .profile that looks like this:
    sudo xboxdrv --silent --config /home/pi/pimame/config/xboxdrv_mapping.cfg --dbus session &
    I had to add an extra flag to get mine to connect properly
    sudo xboxdrv --detach-kernel-driver --silent --config /home/pi/pimame/config/xboxdrv_mapping.cfg --dbus session &

    When mine wasn't connected properly, I got the exact same output that you posted earlier. Once I connected correctly and restarted my system, it mapped correctly (although I think some buttons in /home/pi/pimame/config/xboxdrv_mapping.cfg need to be re-configured)
  • candyman
    @mholgatem adding --detach-kernel-driver activated the controller. Thanks! Now I just have to fix all the buttons in xboxdrv_mapping.cfg since as you noted they're not quite right.
Add a Comment