2ND button joystick on a real Amiga

[Hungry Horace]

this is the test i've always used for Button 2 in joyport 1, which is well known to work!
It's effectively checking the Right mouse button in the joystick port.

		btst.b	#14,$DFF016		; test second button (joy 1)
		bne	.finish

here is from Galahad's Alien 3 (i think?) whd slave, which "megadrive C" is tested.

		dc.l	$0839000e		;btst #$e
		dc.l	$dff016
		bne.s	not_megadrivec

$E = 14 , so the check is identical. All this answers, is that any pad not sending the same signal as megadrive-C, isnt doing a genuine second button press imo.

[Toni Wilen]

Originally Posted by Hungry Horace

this is the test i've always used for Button 2 in joyport 1, which is well known to work!
It's effectively checking the Right mouse button in the joystick port.

Yes, it is correct but it does only work if DFF034 direction bit and data bit is set to one (as explained in HRM).

!!NOTE!! some "non-standard" joysticks/pads/mice (some Amiga/Atari ST switchable mouse for example) can have pullup resistors in button lines and they will work when direction=input. This can cause confusion. Of course in this mode normal non-pullup firebuttons won't work..

		btst.b	#14,$DFF016		; test second 
button (joy 1)

which is actually "illegal" instruction. yes it works but it should be btst.b #14-8,$dff016. btst and friends use byte accesses to memory, not word. (this is very common "bug" in blitter wait too..)

[Retro-Nerd]

Originally Posted by Retro-Nerd

BC Kid doesn't work with the MD pad, but with the Tecno Plus. Not sure about YoJoe, have to test it.

Correction: BC Kid C-button jump works with the MD pad, BUT only in standstill. You can't move and jump at once. No probems with the TP pad.

YoJoe: Works with both pads i have.

Correction2: Now i've plugged the TP pad and then the MD pad again and it works fine with BC Kid. Strange, but true.

[Fabie]

Originally Posted by Retro-Nerd

Correction: BC Kid C-button jump works with the MD pad, BUT only in standstill. You can't move and jump at once. No probems with the TP pad.

YoJoe: Works with both pads i have.

thanks for all Retronerd !!!!!!

it seems that some games were developed for many different pads?

btw..2ND button joystick is really an issue on games on real Amiga and WINUAE

YOJOE 2ND button works with with my pad but 2nd button doesn't works on WINUAE

however BCKID 2nd button and Bubble & squeak works on WINUAE but not on my pad

[TCD]

Originally Posted by Fabie

YOJOE 2ND button works with with my pad but 2nd button doesn't works on WINUAE

Hmm, the 2nd button works fine here in WinUAE without tweaking anything. Not sure why it doesn't for you.

[Hungry Horace]

Originally Posted by Toni Wilen

which is actually "illegal" instruction. yes it works but it should be btst.b #14-8,$dff016. btst and friends use byte accesses to memory, not word. (this is very common "bug" in blitter wait too..)

well, it has been explained to me how it is not the "correct" way of writing it, but i have real trouble understanding how something could be illegal when it compiles/runs/operates 100%... it seems barfly is kind enough to not complain too much when compiling

to me a "bug" produces errors. this does not, it just (really) upsets a few purists!

[StingRay]

Originally Posted by Hungry Horace

this does not, it just (really) upsets a few purists!

As said on IRC already (and yes, I HAVE to repeat it here!), this has NOTHING to do with being purist or not, this code is just incorrect! I agree 100% with Toni!

[pmc]

@ Sting - Yes! \o/

I was only explaining this to someone the other day who sent me some code that had a btst #10 in it.

btst is for BYTES!!

Where's bit 10 in an 8 bit byte!? It's NOT THERE that's where!

[Hungry Horace]

each to their own. I however, am only really interested in the result, and i do get the result i want even with the incorrect code.

i must have learnt it from someone else who was also fond of such bad habits!

[pmc]

Come on HH - why use bad habits? Soon or later your code will FAIL

[Hungry Horace]

Originally Posted by pmc

Come on HH - why use bad habits? Soon or later your code will FAIL

my code fails all the time. (I am very new at asm) - I just correct what is needed to make it work

i will correct this one in my current source, out of gratitude

[pmc]

Originally Posted by HungryHorace

my code fails all the time.

LOL. Doesn't everyone's? Well, not Sting's obviously.

Originally Posted by HungryHorace

i will correct this one in my current source, out of gratitude

Good for you - you know it makes sense.

[Fabie]

Originally Posted by TheCyberDruid

Hmm, the 2nd button works fine here in WinUAE without tweaking anything. Not sure why it doesn't for you.

it doesn't works here....I just checked YoJoe whdload and winuae 160 and 161...the hero can't jump using 2nd button
but I will check Yojoe floppy version later

[TCD]

Originally Posted by Fabie

it doesn't works here....I just checked YoJoe whdload and winuae 160 and 161...the hero can't jump using 2nd button
but I will check Yojoe floppy version later

I think I know the problem then
From the WHDLoad readme :

- Added CUSTOM2 to control how the 2nd joystick button works:
- CUSTOM2=0 (default) disables the 2nd fire button on both joysticks
- CUSTOM2=1 to enable player 1's jump button only
- CUSTOM2=2 to enable player 2's jump button only
- CUSTOM2=3 to enable both players jump buttons

Set Custom2 and it should work.

[prowler]

So, what's the difference between the signals generated by pressing a joystick's 2nd button that invokes no response and pressing some other joypad's button that is detected normally?

Would incorporating a buffer circuit similar to this one (with autofire disabled) into the errant joystick cure the problem when used with a real Amiga?

[Fabie]

Originally Posted by TheCyberDruid

I think I know the problem then
From the WHDLoad readme :

Set Custom2 and it should work.

you are right !!!
it works now !!!

thanks !!!

[TCD]

You're welcome