Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1. #1
    EmuTalk Member
    Join Date
    Jun 2008
    Posts
    2

    A few imput questions...

    Hi, I'm currently running Mupen64Pls 1.4 under Ubuntu 8.04 and I'm wondering about the basic input plugin.

    I can't seem to find the start button, the d-pad (for Kirby), and Z. Any help?



    • Advertising

      advertising
      EmuTalk.net
      has no influence
      on the ads that
      are displayed
        
       

  2. #2
    Mupen64Plus Dev.
    Join Date
    Oct 2007
    Location
    Michigan (United States of America)
    Posts
    448
    Basic Input isn't going to get you very far. Use blight, even for keyboard input (Keyboard is in the list of devices, just click the box on the top right until it says "Keyboard")

  3. #3
    Moderator
    Join Date
    Oct 2007
    Posts
    473
    Quote Originally Posted by Ciell View Post
    Hi, I'm currently running Mupen64Pls 1.4 under Ubuntu 8.04 and I'm wondering about the basic input plugin.

    I can't seem to find the start button, the d-pad (for Kirby), and Z. Any help?
    As nmn said, I would recommend to use blight_input instead of mupen64_input and configure your controller with the blight input GUI.

  4. #4
    EmuTalk Member
    Join Date
    Jun 2008
    Posts
    2
    I can't get the blight plugin to show up on the config screen, so I dl'ed it online.

    But now, when I press a key, it automatically holds it down. Even when I let go.

  5. #5
    EmuTalk Member
    Join Date
    Apr 2004
    Posts
    50
    I believe you may need to add a dependency to get Blight to show up in the config screen...I can't remember what one off the top of my head, but a quick search will turn it up, or if someone else chimes in...
    Specs:
    Mupen64plus v1.99.3
    Geforce 7600GT
    Nvidia 195.36.08
    AMD 64 3000+, 2GB, Arch Linux x86

  6. #6
    Mupen64Plus Dev.
    Join Date
    Oct 2007
    Location
    Michigan (United States of America)
    Posts
    448
    Use the included blight input. If the GUI never shows up, be sure SDL-ttf is installed. Various distros have different packages for this. I'm not an ubuntu user so bare with me but i believe you want to do this:

    Code:
    sudo apt-get install libsdl-ttf2.0-0

    I'm most worried i got the package name wrong, but i think that would be it. Anyways, you do that on a terminal and then try running Mupen64Plus and configuring regular blight (included with M64P) and you should be good to go. If not let us know what else goes wrong.


    <slightly offtopic> Can't we statically compile to SDL-ttf to avoid this?

  7. #7
    Mupen64Plus Dev.
    Join Date
    Jul 2006
    Location
    Middletown, CT
    Posts
    130
    Removing the SDl_tff dependency was on the TODO list since 1.2. Its only used to draw Blight's SDL GUI, which was agreed should be replaced with either a Gtk or KDE4/Qt GUI (ideally both, one for each GUI). Ebenblues was working on this, but hasn't been around recently.

  8. #8
    Moderator
    Join Date
    Oct 2007
    Posts
    473
    Maybe we can use freetype instead of SDL_ttf. Freetype is already needed by the core for the OSD anyway.

  9. #9
    Mupen64Plus Dev.
    Join Date
    Feb 2008
    Location
    USA
    Posts
    144
    Quote Originally Posted by Tillin9 View Post
    Removing the SDl_tff dependency was on the TODO list since 1.2. Its only used to draw Blight's SDL GUI, which was agreed should be replaced with either a Gtk or KDE4/Qt GUI (ideally both, one for each GUI). Ebenblues was working on this, but hasn't been around recently.
    Yeah, I haven't been able to contribute for a little while, but I'm still around. I think the best solution is still converting the blight config gui to gtk, which would remove the SDL_ttf dependency.
    "The humble learn the fastest because they don't waste time on defending a false image."

  10. #10
    Mupen64Plus Dev.
    Join Date
    Oct 2007
    Location
    Michigan (United States of America)
    Posts
    448
    In order to do this reliably, we still need an SDL window, so i'm guessing we'll still need to use at least freetype so we can display the message to enter a key. We could possibly avoid it, but in it's current state it would be better if we could show what button they are assigning (especially since the axis's are now split)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •