Collision Detection

[johnno56]

GDK?

[Petr]

Thank you, I'm glad to look at it. I'm not an undergraduate, so I first had to find out what you mean by the triangular / circle method. I found this in a bachelor's thesis on this subject, so again i know more.

Hi Johhno56, GDK is Unseen Machine´s library downloadable here: https://www.qb64.org/forum/index.php?topic=284.0;topicseen

[Petr]

A little beyond the thema - function for detecting collisions between point and ellipse:

Code: QB64: [Select]

1. 'elipse collision detection for point
2. SCREEN 13
3. LET CenterX = 160: LET CenterY = 100: LET A = 40: LET B = 20
4.  
5. FOR F = 0 TO _PI(2) STEP .01
6.     PSET (CenterX + SIN(F) * A, CenterY + COS(F) * B)
7. NEXT F
8.  
9. DO
10.     WHILE _MOUSEINPUT: WEND
11.     LOCATE 1, 1: PRINT Ellipse(_MOUSEX, _MOUSEY, CenterX, CenterY, A, B)
12. LOOP UNTIL _KEYHIT = 27
13. END
14.  
15.  
16. FUNCTION Ellipse (X&, Y&, CX&, CY&, A&, B&)
17.     XY## = (((X& - CX&) ^ 2) / A& ^ 2) + (((Y& - CY&) ^ 2) / B& ^ 2)
18.     IF XY## <= 1.1 THEN Ellipse = 1 ELSE Ellipse = 0
19. END FUNCTION
20.  
21.  

[TempodiBasic]

IMHO
GDK, maybe is it Game Development Kit ?  Like that other library of Terry Ritchie.
They have different structures and GDK has maintenance, about Terry Ritchie's Library it seems discontinued....
I have a previous old version of these library on my Pc (TOSHIBA)

'\\ UnseenGDK Core v1.4 - Updated March 3rd 2015
'// Created By John Onyon a.k.a Unseen Machine
'// Optimistation by CodeGuy
'// ScanKeys% function by Cypherium
'// Image rotation function by Galleon
'// Rotated rectangle collisions by Richard Notley

from Unseen was coming also VQB02 in the same package...
(IMHO  Visual QB??? but there is nothing like mouseBuilding Interface or Structure of a program...)
a library to build application windowing and manage input from mouse and keyboard
and a demo .... MacDock.BAS

'// VQB v.02 - By John Onyon a.k.a Unseen Machine
'// VQB_01 programs are NOT comaptible with this version.

.... I don't know if this project is still in being or discontinued.... but of his child must talk at first the father if he will!

[bplus]

GDK, maybe is it Game Development Kit ? 

Dang! That's a great theory even if it were incorrect.

No, it's too good to be wrong? :D

[bplus]

The flaw of this theory is this:

Why name it with _Dev for .bm file?

but in fact in the last posting he had removed _Dev from the library file name. In fact, I had to fix my copy of his code to match the first .bm I downloaded.

[bplus]

I suppose these are developments from having your skull on fire!

BTW, VQB does sound like another excellent name of something!

[TempodiBasic]

Hi Petr
fine your sample but so much static....
so I have added a little movement in it

see here
 

Code: QB64: [Select]

1. 'elipse collision detection for point
2. SCREEN 13 'w320xh200 I don't remember well dimensions of old legacy screen mode :-)
3. LET CenterX = 80: LET CenterY = 100: LET A = 40: LET B = 20
4. LET MoveX = 1: LET MoveY = 1
5.  
6. DO
7.     WHILE _MOUSEINPUT: WEND
8. ' output engine (Not mine) :-)
9.     FOR F = 0 TO _PI(2) STEP .01
10.         PSET (CenterX + SIN(F) * A, CenterY + COS(F) * B)
11.     NEXT F
12.  
13. ' refreshing after an elapsed time  
14.     _DELAY 0.02
15.     CLS
16. ' logic engine to let stay ellipse in the screen
17.     IF (CenterX - A <= 0) THEN
18.         MoveX = 1
19.     ELSE
20.         IF (CenterX + A >= 320) THEN MoveX = -1
21.     END IF
22.  
23.     IF (CenterY - B <= 0) THEN
24.         MoveY = 1
25.     ELSE
26.         IF (CenterY + B >= 200) THEN MoveY = -1
27.     END IF
28. ' logic engine calculating new position of ellipse
29.     CenterX = CenterX + MoveX 'centerx++/centerx--
30.     CenterY = CenterY + MoveY 'centery++/ centery--
31.  
32.     LOCATE 1, 1: PRINT Ellipse(_MOUSEX, _MOUSEY, CenterX, CenterY, A, B)
33. LOOP UNTIL _KEYHIT = 27
34. END
35.  
36.  
37. FUNCTION Ellipse (X&, Y&, CX&, CY&, A&, B&)
38.     XY## = (((X& - CX&) ^ 2) / A& ^ 2) + (((Y& - CY&) ^ 2) / B& ^ 2)
39.     IF XY## <= 1.1 THEN Ellipse = 1 ELSE Ellipse = 0
40. END FUNCTION
41.  

@Bplus
hey boy but  are you talking about my brain or my skull? :-(( For now weather is hot but not such so hot!

I suppose these are developments from having your skull on fire!

a skull can be a head without a brain into it.... just a zombie head :-)
I cannot imagine what can be thought in a head on fire... and moreover in a skull on fire....
like this https://tse3.mm.bing.net/th?id=OIP.tONt-rsCjWByGGeqc9QaiQHaHa&pid=15.1&P=0&w=300&h=300
or this one http://www.desktopanimated.com/img/Preview/FireSkull3.jpg
or just this last http://3.bp.blogspot.com/_6GGcln-fE78/TCXYCwNk2NI/AAAAAAAAAWk/mwmCK9izrG0/s1600/Fire+Skull.jpg

Ok I have found the just SkullOnFire... it is attached

[Petr]

Hi TempoDiBasic, thank you. Now it's nicer. I've been looking at your source, and I have never seen the skull picture now, so I say, what it would be. BPlus had some sort of muse :-D mood today, as I read on the forum. He gave his passage full of muse. And my muse is sleeping today: -D

[bplus]

For burning skull, I was talking about unseen machine's latest avatar!

We were talking about the naming of his GDK system and I was wondering why he named his .BM file unseenGDK_Dev.bm which translates to unseen Game Develoment Kit _ Development.bm the word "development" looked a bit redundant.

[Unseen Machine]

_DEV is cause it is the Development version, being edited, its so i dont get confused!

VQB is now moving into v.4, ill be putting it out soon.

Unseen

[bplus]

;-))  I see, very logical, now.

Very curious about VQB!

[Petr]

This is only the final part of the program, which I will release as long as I finish:

WARNING FOR BPLUS! FULLSCREEN IS USED :-D

Code: QB64: [Select]

1. 'IF o theraphy :-D (how, for hell write correct conditions?)
2.  
3. object0: '0 are empty places, 1 are points
4. DATA 0,0,0,0,0
5. DATA 0,1,1,1,1
6. DATA 0,0,0,0,1
7. DATA 1,1,1,1,1
8. DATA 1,0,0,0,0
9.  
10. DIM O(4, 4)
11. 'load object data to array for this example. This values return next program i send here soon as possible.
12. FOR ObjectLoad = 0 TO 24
13.     READ value
14.     O(x, y) = value
15.     x = x + 1: IF x > 4 THEN x = 0: y = y + 1
16. NEXT
17.  
18. SCREEN _NEWIMAGE(320, 240, 256): _FULLSCREEN
19. 'show what is in array
20. FOR y = 0 TO 4
21.     FOR x = 0 TO 4
22.         IF O(x, y) = 1 THEN PSET (160 + x, 100 + y), 14
23. NEXT x, y
24.  
25. 'now own collision detection form. If Object 1 is in quad Object 2 or above, then:
26. 'example - first row: first row is 5 x empty pixel. Let say, object 2 is comming to this area to third pixel:
27.  
28. 'original: 0,0,0,0,0    new: 0,0,1,0,0 - beacause in this row for Object1 are zeros, is none collision.
29.  
30. 'If object1 go next 1 pixel down, second row for Object1 is: 0,1,1,1,1 - and now is comming to third position where but is 1. Also is object collision.
31.  
32. 'so this programmable:
33. Object1X = 160
34. Object1Y = 100
35. _MOUSEHIDE
36. DO
37.     WHILE _MOUSEINPUT
38.         Object2X = _MOUSEX
39.         Object2Y = _MOUSEY
40.     WEND
41.     CLS
42.     FOR y = 0 TO 4
43.         FOR x = 0 TO 4
44.             IF O(x, y) = 1 THEN
45.  
46.                 PSET (Object1X + x, Object1Y + y), 14
47.                 PSET (Object2X + x, Object2Y + y), 15
48.             END IF
49.     NEXT x, y
50.  
51.  
52.     coll = 0
53.     'first standard QUAD condition and THEN detail comparation:  (both objects are 5 x 5 pixels)
54.     IF Object2X >= Object1X - 5 AND Object2X <= Object1X + 5 THEN
55.         TTT = TIMER
56.         IF Object2Y >= Object1Y - 5 AND Object2Y <= Object1Y + 5 THEN
57.             LOCATE 1, 1: PRINT "In collision area "
58.             FOR TY = Object1Y TO Object1Y + 4
59.                 FOR TX = Object1X TO Object1X + 4
60.  
61.                     FOR tTY = Object2Y TO Object2Y + 4
62.                         FOR tTX = Object2X TO Object2X + 4
63.                             IF O(TX - Object1X, TY - Object1Y) = 1 AND O(tTX - Object2X, tTY - Object2Y) = 1 AND TX = tTX AND TY = tTY THEN coll = 1: GOTO E ELSE coll = 0
64.                             'Of course, for a higher program speed, it's better to use a step higher than 1 for the shape of the object. Let's assume that your character is 60 pixels high,
65.                             ' moving in one step by 10 pixels. Then, the enemy moves with a 10-pixel pitch, so only every ten of the pixel per circuit character is needed.
66.             NEXT tTX, tTY, TX, TY
67.         END IF
68.         LOCATE 3, 1: PRINT TIMER - TTT
69.     END IF
70.     E:
71.     IF coll THEN LOCATE 2, 1: PRINT "Is collision " ELSE LOCATE 2, 1: PRINT "Not collision"
72.     _DISPLAY
73. LOOP UNTIL _KEYHIT = 27
74.  

[bplus]

Thanks for warning, I am now armed with Alt+F4 and ready for no escape. ;)

This seems like allot of work and works!

[Petr]

Divide and rule. The digital monster was stubborn, so I had to divide it. :-D