GUOCHAOLANG / quake2android

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

Keyboard binds for Look up and Down will not work #19

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Bind "+lookdown" and "+lookup" to keys but they won't work

2.
3.

What is the expected output? What do you see instead?

Keys should allow you to look up and down. I tested my original Q2 and it 
worked fine

I am using a Phonejoy and have it working except for this. I hope you will fix 
it.

What version of the product are you using? On what operating system?

release 1.91

Android 4.0.3

Please provide any additional information below.

Original issue reported on code.google.com by jwilso...@gmail.com on 8 Jul 2012 at 1:34

GoogleCodeExporter commented 8 years ago
I can confirm this exact behaviour. PLEASE look into a fix, as it is the last 
step from me getting to play Quake 2 perfectly using the Sixaxis app + 
controller!

LOVE the port too, it runs perfectly smooth and crisp!

Original comment by scar45 on 5 Oct 2012 at 5:08

GoogleCodeExporter commented 8 years ago
*EDIT* - After playing around more with the Sixaxis app, I was able to set a 
Touch Profile for the Right Stick to where the on-screen area is for 
looking/aiming. "Relative Mode" must be enabled for the button, and you may 
have to play with the Sensitivity (in Sixaxis --> Edit Touch Profile --> Edit 
Button).

I think this is why +lookup and +lookdown do not work, as maybe the dev had to 
disable them to get this touchscreen format working? Regardless, what would be 
MORE than great is to have native gamepad support, possibly tied into the "use 
joystick" support (based on DirectInput) that Quake 2 has natively.

With my current setup above, I have also set Sixaxis to behave NOT like a 
native Android gamepad, but rather just bound keys to the buttons, then bound 
them again within Quake 2. It's not ideal, as the "Touch Emulation" mode of 
Sixaxis doesn't feel  right, but it's about the best solution I've come up with 
for controller support.

Original comment by scar45 on 5 Oct 2012 at 6:18