sysgodmin / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Mupen64plus controls aren't working #592

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Describe your system:
 - Operating System (be specific): Max OS X Mavericks
 - Machine type (32-bit or 64-bit):64
 - Mupen64Plus version: 1.99.5
 - Plugins used:n/a

For visual artifacts, give:
- game name and CRC/MD5 hash (printed on console)
- description of the artifact (missing polygons, flashing, wrong colors,
etc)

Describe the problem:
When I first tried working with the game, it wouldnt detect my PS3 controller. 
The keyboard controls would work so I could play the games. Suddenly they 
stopped working. I messed with the config files and got both the keyboard and 
PS3 controller to work. All of a sudden they both stopped working, but the 
other keyboard controls (i.e. volume, save, load, pause, etc.) do work. 

My terminal reads this: 
 __  __                         __   _  _   ____  _             
|  \/  |_   _ _ __   ___ _ __  / /_ | || | |  _ \| |_   _ ___ 
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|  
| |  | | |_| | |_) |  __/ | | | (_) |__   _|  __/| | |_| \__ \  
|_|  |_|\__,_| .__/ \___|_| |_|\___/   |_| |_|   |_|\__,_|___/  
             |_|         http://code.google.com/p/mupen64plus/  
Mupen64Plus Console User-Interface Version 1.99.5

UI-console: attached to core library 'Mupen64Plus Core' version 1.99.5
            Includes support for Dynamic Recompiler.
Core: Goodname: Legend of Zelda, The - Majora's Mask (U) [!]
Core: Name: ZELDA MAJORA'S MASK
Core: MD5: 2A0A8ACB61538235BC1094D297FB6556
Core: CRC: 5354631c 3a2def0
Core: Imagetype: .z64 (native)
Core: Rom size: 33554432 bytes (or 32 Mb or 256 Megabits)
Core: Version: 144b
Core: Manufacturer: Nintendo
Core: Country: USA
UI-Console: Cheat codes disabled.
UI-console: using Video plugin: 'Mupen64Plus OpenGL Video Plugin by Rice' 
v1.99.5
UI-console: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v1.99.5
Input: N64 Controller #1: Using stored config for SDL joystick 0 
('PLAYSTATION(R)3 Controller')
Input: N64 Controller #2: Using stored config for SDL joystick 1 
('PLAYSTATION(R)3 Controller')
Input Warning: N64 Controller #3: Disabled, SDL joystick 2 is not available
Input Warning: N64 Controller #4: Disabled, SDL joystick 3 is not available
UI-console: using Input plugin: 'Mupen64Plus SDL Input Plugin' v1.99.5
UI-console: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP 
Plugin' v1.99.5
Input: N64 Controller #1: Using stored config for SDL joystick 0 
('PLAYSTATION(R)3 Controller')
Input: N64 Controller #2: Using stored config for SDL joystick 1 
('PLAYSTATION(R)3 Controller')
Input Warning: N64 Controller #3: Disabled, SDL joystick 2 is not available
Input Warning: N64 Controller #4: Disabled, SDL joystick 3 is not available
Input: 2 controller(s) found, 2 plugged in and usable in the emulator
Input: Mupen64Plus SDL Input Plugin version 1.99.5 initialized.
Video: SSE processing enabled.
Video: Found ROM 'ZELDA MAJORA'S MASK', CRC 1c635453f0dea203-45
Video: Enabled hacks for game: 'ZELDA MAJORA'S MASK'
Video: Initializing OpenGL Device Context.
Core: Setting 32-bit video mode: 813x612
Video: Using OpenGL: Intel Inc. - Intel HD Graphics 4000 OpenGL Engine : 2.1 
INTEL-8.18.29
Video: OpenGL Combiner: Fragment Program
Audio: Initializing SDL audio subsystem...
Core: Starting R4300 emulator: Dynamic Recompiler
Core: R4300: starting 64-bit dynamic recompiler at: 0x1047e8200

I have the default config files downloaded with mupen64+ (attached in case)

Please provide any additional information below.
 PLEASE HELP GET MY CONTROLLER WORKING AGAIN! 

Original issue reported on code.google.com by Pano.Pap...@gmail.com on 9 Jan 2014 at 11:39

Attachments:

GoogleCodeExporter commented 8 years ago
First thing: You are using a rather old version of mupen64plus.

It is also rather normal that keyboards don't work when you have no 
Input-SDL-Control* section with keyboard settings like described in 
https://code.google.com/p/mupen64plus/wiki/KeyboardSetup (you have currently 
two sections with PS3 controller - device id 1 and 2)

The default settings can for example be found at 
https://github.com/mupen64plus/mupen64plus-input-sdl/blob/master/data/InputAutoC
fg.ini#L3

When you update then also read 
https://code.google.com/p/mupen64plus/wiki/InputPluginUsage (the important part 
is the "mode" setting which you may want to change to 0 for the kebboard device 
to avoid reconfiguration of your keyboard input device)

Original comment by s...@narfation.org on 10 Jan 2014 at 7:18

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
OK, I finally got it to work (even got highres and AA working which is fucking 
awesome!) I'll delete my previous posts and just post some highlights:

1) OS X loads both USB and bluetooth devices if you have your controller paired 
and plugged in. If you do this, the USB device doesn't work. Just use one or 
the other (disable bluetooth if you have to when using USB). 

2) I had to delete everything and start fresh to get things to work. I can't 
explain why, but somehow a fresh install including a new mupen64plus.cfg 
(located in ~/.config/mupen64plus/) helped.

(I don't know if this is necessary, but I didn't use the InputAutoCfg.ini 
supplied with the OS X bundle, but used the latest one on the git.)

3) In the cfg, I used mode = 0 for fully manual. I used testjoystick to get the 
button numbers. Here are my configs:

[Input-SDL-Control1]

# Mupen64Plus SDL Input Plugin config parameter version number.  Please don't 
change this version number.
version = 2
# Controller configuration mode: 0=Fully Manual, 1=Auto with named SDL Device, 
2=Fully automatic
mode = 0
# Specifies which joystick is bound to this controller: -1=No joystick, 0 or 
more= SDL Joystick number
device = 0
# SDL joystick name (or Keyboard)
name = "PLAYSTATION(R)3 Controller"
# Specifies whether this controller is 'plugged in' to the simulated N64
plugged = True
# Specifies which type of expansion pak is in the controller: 1=None, 2=Mem 
pak, 5=Rumble pak
plugin = 2
# If True, then mouse buttons may be used with this controller
mouse = False
# Scaling factor for mouse movements.  For X, Y axes.
MouseSensitivity = "2.00,2.00"
# The minimum absolute value of the SDL analog joystick axis to move the N64 
controller axis value from 0.  For X, Y axes.
AnalogDeadzone = "4096,4096"
# An absolute value of the SDL joystick axis >= AnalogPeak will saturate the 
N64 controller axis value (at 80).  For X, Y axes. For each axis, this must be 
greater than the corresponding AnalogDeadzone value
AnalogPeak = "32768,32768"
# Digital button configuration mappings
DPad R = "button(3)"
DPad L = "button(2)"
DPad D = "button(0)"
DPad U = "button(1)"
Start = "button(3)"
Z Trig = "button(8)"
B Button = "button(15)"
A Button = "button(14)"
C Button R = "axis(2+)"
C Button L = "axis(2-)"
C Button D = "axis(3+)"
C Button U = "axis(3-)"
R Trig = "button(9)"
L Trig = "button(8)"
Mempak switch = """"
Rumblepak switch = """"
# Analog axis configuration mappings
X Axis = "axis(0-,0+)"
Y Axis = "axis(1-,1+)"

4) Maybe some extra voodoo. *shrug*

Original comment by deadba...@gmail.com on 19 May 2015 at 8:25

GoogleCodeExporter commented 8 years ago
deadballo, I see a couple of problems with this configuration.  You have the Z 
trigger and Left trigger mapped to the same button (#8), and you also have the 
right D-pad button and the Start button mapped to the same button (#3).

Original comment by richard...@gmail.com on 2 Jun 2015 at 3:49

GoogleCodeExporter commented 8 years ago
You are using a very old version of our emulator (v1.99.5).  Please use the 
latest (2.5).  I tried on a Mac OSX 10.9 system with your configuration (using 
the latest, v2.5) and the mappings which you have given do not work.  The D-Pad 
buttons are 4-7, not 0-3.

Original comment by richard...@gmail.com on 3 Jun 2015 at 5:54