Hardware collision detection

[nandius_c]

I'm making a simple hardware collision detection test. I've read about it through the AHRM and Amiga System Programmers Guide but I still can't make it work. I've got a 4-colour playfield, sprite 0 pointing to some data and the other 7 sprites pointing to null sprites. I thought that to detect collision between sprite 0 and playfield 1, CLXCON would have to be $0000, meaning: no interested in detecting collision for odd sprites, no required values for any bitplane. Sprite 0 is positioned over an area of the playfield filled with colour 0. If I set it that way CLXDATA is always $81fe, meaning that every hw sprite is colliding with both playfields (¿?). If I set some mask bits on CLXCON it does detect collision over the masked colour.

Isn't it possible to detect collision between a hw sprite and any non transparent pixel of the playfield?

I would appreciate any advice to point me in the right direction.

NOTE: I'm thinking mostly in a dual-playfield scenario where PF1 is in front of PF2 and colour 0 is transparent. I remember Toni saying there was some little differences between single and dual-playfield, and even reading a piece of pseudocode explaining how WinUAE deals with all this but I didn't understand that completely though.

NOTE2: I'm reading again this thread (http://eab.abime.net/showthread.php?p=1335382&nojs=1) and I think it's not possible to do what I wanted. It still surprises me that you cannot set a value in CLXCON to detect collisions with any non transparent pixel of PF1, at least in dual-playfield mode. Please, correct me if I'm wrong...

Thanks!

[nandius_c]

I found this text in the specs doc for Denise:


"NOTE: Disabled Bit Planes cannot prevent collisions. Therefore if all Bit Planes are disabled, collisions will be continuous, regardless of the match values."


That's exactly what I get, but then again: how do you detect collision with ANY non-transparent pixel of the playfield? Isn't it possible?

[mcgeezer]

Originally Posted by nandius_c

I'm making a simple hardware collision detection test. I've read about it through the AHRM and Amiga System Programmers Guide but I still can't make it work. I've got a 4-colour playfield, sprite 0 pointing to some data and the other 7 sprites pointing to null sprites. I thought that to detect collision between sprite 0 and playfield 1, CLXCON would have to be $0000, meaning: no interested in detecting collision for odd sprites, no required values for any bitplane. Sprite 0 is positioned over an area of the playfield filled with colour 0. If I set it that way CLXDATA is always $81fe, meaning that every hw sprite is colliding with both playfields (¿?). If I set some mask bits on CLXCON it does detect collision over the masked colour.

Isn't it possible to detect collision between a hw sprite and any non transparent pixel of the playfield?

I would appreciate any advice to point me in the right direction.

Thanks!

So when I read the HRM and I want to detect collisions between sprite 0 and bitplanes 1 & 2 (4 colours) then I would set CLXCON to $10c3.

I haven't tried it but this would match:
Bit 12 for Enable Sprite 0 & 1.
Bits 6 & 7 for enable bitplanes 1 & 2
Bits 0 & 1 for match required on bitplanes 1 & 2

Geezer

[nandius_c]

Originally Posted by mcgeezer

So when I read the HRM and I want to detect collisions between sprite 0 and bitplanes 1 & 2 (4 colours) then I would set CLXCON to $10c3.

I haven't tried it but this would match:
Bit 12 for Enable Sprite 0 & 1.
Bits 6 & 7 for enable bitplanes 1 & 2
Bits 0 & 1 for match required on bitplanes 1 & 2

Geezer

With that CLXCON value it only detects the collision when the sprite is over the colour with index 3 (plane 1 = 1, plane 2 = 1), because those are the required values (bits 0 & 1 in CLXCON). As an example, if you keep bits 6 & 7 set, but clear 0 & 1, I guess it will signal a collision when the sprite touches the colour with index 0. That doesn't make much sense to me as why would you want to check collisions against colour 0? Sprites don't collide on their transparent colours. This part of the amiga hardware is somehow weird .

[Auscoder]

Originally Posted by nandius_c

With that CLXCON value it only detects the collision when the sprite is over the colour with index 3 (plane 1 = 1, plane 2 = 1), because those are the required values (bits 0 & 1 in CLXCON). As an example, if you keep bits 6 & 7 set, but clear 0 & 1, I guess it will signal a collision when the sprite touches the colour with index 0. That doesn't make much sense to me as why would you want to check collisions against colour 0? Sprites don't collide on their transparent colours. This part of the amiga hardware is somehow weird .

Yep! Unfortunately can only match against a specific bit set, can’t match against any combo. Means you need to author essentially a collision plane to be super accurate. Annoying and lacking imo.