« previous next »
Pages: [1] 2 3 4   Go Down

Author Topic: MAPTRIANGLE in 3D  (Read 26612 times)

0 Members and 1 Guest are viewing this topic.

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
MAPTRIANGLE in 3D
« on: June 25, 2018, 04:08:57 pm »
Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(1024, 768, 32)
  3. img& = _COPYIMAGE(im&, 33)
  5. SX0 = 0: SY0 = 0: SX1 = 0: SY1 = _HEIGHT: sx2 = _WIDTH: sy2 = 0: sx3 = _WIDTH: sy3 = _HEIGHT
  6. DX0 = -2: DY0 = 2: DX1 = -2: DY1 = -2: DX2 = 2: DY2 = 2: DX3 = 2: DY3 = -2
  7.  
  8. tt = .01: t = .1
  10.     e& = ell&
  12.     Mx = _MOUSEX: My = _MOUSEY
  13.     StredX = Mx
  14.     t = t + tt: IF t > _PI(2) OR t < -_PI(2) THEN tt = tt * -1
  15.     RR = SIN(t) - 4
  16.     SS = COS(t) - 10
  17.     R = -SIN(t) * -2
  18.     s = -COS(t) * 2
  19.  
  20.     _MAPTRIANGLE (SX0, SY0)-(sx3, sy3)-(SX1, SY1), e& TO(DX0 * R, DY0 * s, RR)-(DX3 * R, DY3 * s, SS)-(DX1 * R, DY1 * s, RR), 0, _SMOOTH
  21.     _MAPTRIANGLE (SX0, SY0)-(sx3, sy3)-(sx2, sy2), e& TO(DX0 * R, DY0 * s, RR)-(DX3 * R, DY3 * s, SS)-(DX2 * R, DY2 * s, SS), 0, _SMOOTH
  22.     _DISPLAY
  23.     _FREEIMAGE e&    
  24.     _LIMIT 30
  26.  
  27.  
  28.  
  30.  
  31.     SHARED vx, vy, Mxx, Myy
  32.     LOCATE 1, 1: PRINT "This is Software Screen."
  33.     V& = _NEWIMAGE(1024, 768, 32)
  34.     _DEST V&
  35.     W = 1024: H = 768
  36.     IF Mxx = 0 THEN Mxx = 10: Myy = 10
  37.     vx = vx + Mxx: IF vx > W OR vx < 0 THEN Mxx = Mxx * -1
  38.     vy = vy + Myy: IF vy > H OR vy < 0 THEN Myy = Myy * -1
  39.     CLS , _RGB32(1, 55, 132)
  41.     LOCATE 11, 30: PRINT "This is Hardware Screen"
  42.     FOR d = 0 TO _PI / 2 STEP .2
  43.         LINE (vx - SIN(d) * 50, vy - COS(d) * 50)-(vx + SIN(d) * 50, vy + COS(d) * 50), , BF
  44.     NEXT d
  45.     _DEST 0
  46.     ell& = _COPYIMAGE(V&, 33)
  47.     _FREEIMAGE V&
  49.  
« Last Edit: November 03, 2018, 03:24:49 pm by Petr »
Logged

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #1 on: June 25, 2018, 04:14:07 pm »
Previous source code repaired, because now is this possible :-D
« Last Edit: November 03, 2018, 03:25:54 pm by Petr »
Logged

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #2 on: November 03, 2018, 03:32:50 pm »
I working on another program for a long time. It has been literally worm by my neck, so I needed to relax. So, What about, projected a normal 2D image in the form of a pyramid in 3D?

Code: QB64: [Select]
  1. image = _LOADIMAGE("dyne01.jpg", 32)
  2. imag = _NEWIMAGE(1024, 768, 32)
  3. _PUTIMAGE (_WIDTH(image), _HEIGHT(image))-(0, 0), image, imag ' downsizing image to one size
  4.  
  5. imh& = _COPYIMAGE(imag, 33) '      hardware image are need for real 3D maptriangle use
  7.     X AS SINGLE
  8.     Y AS SINGLE
  9.     Z AS SINGLE
  11.  
  12.  
  13. W = _WIDTH(imag)
  14. H = _HEIGHT(imag)
  15.  
  16. prvkuX = 60 '                       image "compression" ratio (do quads in this steps)
  17. prvkuY = 80
  18.  
  19. pX = W / prvkuX
  20. pY = H / prvkuY
  21. DIM V(4) AS V '                              SOFTWARE IMAGE ARRAY
  22.  
  23. SCREEN _NEWIMAGE(W * 2, H * 2, 32)
  25.  
  26. camX = 0
  27. camY = -300
  28. camZ = -3000
  29.  
  30.  
  31. DO UNTIL camZ > 5
  32.     camZ = camZ + 2
  33.  
  34.     FOR y = 0 TO H - 1 STEP pY
  35.         FOR x = 0 TO W - 1 STEP pX
  36.  
  37.             vyska = 115 '                   upper vertex for pyramide
  38.             dno = 100 '                     bottom vertexes for pyramide
  39.  
  40.             '                               2D Sources
  41.             V(0).X = x - (pX / 2) '         middle
  42.             V(0).Y = y - (pY / 2)
  43.  
  44.             V(1).X = x - pX '               left upper vertex '           1+--------------+2
  45.             V(1).Y = y - pY '                                              |\     d     / |
  46.             '                                                              |   \  0  /    |
  47.             V(2).X = x '                    right upper vertex  '          | a    +    c  |
  48.             V(2).Y = y - pY '                                              |   /    \     |
  49.             '                                                              |/     b    \  |
  50.             V(3).X = x '                    right bottom vertex           4+--------------+3
  51.             V(3).Y = y
  52.  
  53.             V(4).X = x - pX '               left bottom vertex
  54.             V(4).Y = y
  55.  
  56.  
  57.             'recalculating for 3D _MAPTRIANGLE use
  58.  
  59.             DIM VV(4) AS V '                 HARDWARE IMAGE ARRAY
  60.  
  61.             VV(0).X = W / 2 - V(0).X + camX '   middle vertex
  62.             VV(0).Z = H / 2 - V(0).Y + camZ
  63.             VV(0).Y = vyska + camY
  64.  
  65.  
  66.             VV(1).X = W / 2 - V(1).X + camX '   left upper vertex
  67.             VV(1).Z = H / 2 - V(1).Y + camZ
  68.             VV(1).Y = dno + camY
  69.  
  70.             VV(2).X = W / 2 - V(2).X + camX '   right upper vertex
  71.             VV(2).Z = H / 2 - V(2).Y + camZ
  72.             VV(2).Y = dno + camY
  73.  
  74.             VV(3).X = W / 2 - V(3).X + camX '   right bottom vertex
  75.             VV(3).Z = H / 2 - V(3).Y + camZ
  76.             VV(3).Y = dno + camY
  77.  
  78.             VV(4).X = W / 2 - V(4).X + camX '   left bottom vertex
  79.             VV(4).Z = H / 2 - V(4).Y + camZ
  80.             VV(4).Y = dno + camY
  81.  
  82.  
  83.             '3D with _MAPTRIANGLE is based on OpenGL, so coordinates here are 0,0,-1 in middle screen, to left is X negative, to right is X positive, for up is Y positive, for down is Y negative,
  84.             'for inward is Z negative (to -10000) and for outward is bigger to -1. If is Z higher than -1, is unvisible, is out of the screen.
  85.  
  86.  
  87.  
  88.  
  89.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(4).X, V(4).Y)-(V(0).X, V(0).Y), imh& TO(VV(1).X, VV(1).Y, VV(1).Z)-(VV(4).X, VV(4).Y, VV(4).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'a
  90.             _MAPTRIANGLE (V(4).X, V(4).Y)-(V(3).X, V(3).Y)-(V(0).X, V(0).Y), imh& TO(VV(4).X, VV(4).Y, VV(4).Z)-(VV(3).X, VV(3).Y, VV(3).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'b
  91.             _MAPTRIANGLE (V(3).X, V(3).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(VV(3).X, VV(3).Y, VV(3).Z)-(VV(2).X, VV(2).Y, VV(2).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'c
  92.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(VV(1).X, VV(1).Y, VV(1).Z)-(VV(2).X, VV(2).Y, VV(2).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'd
  93.         NEXT x
  94.     NEXT y
  95.     _DISPLAY
  96.     _LIMIT 50 'if you use higher resolution (more quads) in lines 19, 20, maybe delete or overwrite this limit.
  98.  
dyne01.jpg
* dyne01.jpg (Filesize: 57.5 KB, Dimensions: 640x426, Views: 601)
Logged

Offline bplus

  • Global Moderator
  • Forum Resident
  • Posts: 8053
  • b = b + ...
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #3 on: November 03, 2018, 04:26:56 pm »
Petr, this is interesting, is there a way to tilt top end toward viewer leaving bottom edge the same?

press esc to quit:
Code: QB64: [Select]
  1. image = _LOADIMAGE("dyne01.jpg", 32)
  2. imag = _NEWIMAGE(1024, 768, 32)
  3. _PUTIMAGE (_WIDTH(image), _HEIGHT(image))-(0, 0), image, imag ' downsizing image to one size
  4.  
  5. imh& = _COPYIMAGE(imag, 33) '      hardware image are need for real 3D maptriangle use
  7.     X AS SINGLE
  8.     Y AS SINGLE
  9.     Z AS SINGLE
  11.  
  12.  
  13. W = _WIDTH(imag)
  14. H = _HEIGHT(imag)
  15.  
  16. prvkuX = 60 '                       image "compression" ratio (do quads in this steps)
  17. prvkuY = 80
  18.  
  19. pX = W / prvkuX
  20. pY = H / prvkuY
  21. DIM V(4) AS V '                              SOFTWARE IMAGE ARRAY
  22.  
  23. SCREEN _NEWIMAGE(W * 2, H * 2, 32)
  25.  
  26. camX = -180
  27. camY = -200
  28. camZ = -500
  29.  
  30. dir = 1
  31. DO UNTIL _KEYDOWN(27) <> 0
  32.     camZ = camZ + 2 * dir
  33.     IF camZ > -400 THEN dir = -dir: camZ = -400: camX = camX - 4
  34.     IF camZ < -500 THEN dir = -dir: camZ = -500: camY = camY - 4
  35.  
  36.  
  37.     FOR y = 0 TO H - 1 STEP pY
  38.         FOR x = 0 TO W - 1 STEP pX
  39.  
  40.             vyska = 118 '                   upper vertex for pyramide  115
  41.             dno = 110 '                     bottom vertexes for pyramide 100
  42.  
  43.             '                               2D Sources
  44.             V(0).X = x - (pX / 2) '         middle
  45.             V(0).Y = y - (pY / 2)
  46.  
  47.             V(1).X = x - pX '               left upper vertex '           1+--------------+2
  48.             V(1).Y = y - pY '                                              |\     d     / |
  49.             '                                                              |   \  0  /    |
  50.             V(2).X = x '                    right upper vertex  '          | a    +    c  |
  51.             V(2).Y = y - pY '                                              |   /    \     |
  52.             '                                                              |/     b    \  |
  53.             V(3).X = x '                    right bottom vertex           4+--------------+3
  54.             V(3).Y = y
  55.  
  56.             V(4).X = x - pX '               left bottom vertex
  57.             V(4).Y = y
  58.  
  59.  
  60.             'recalculating for 3D _MAPTRIANGLE use
  61.  
  62.             DIM VV(4) AS V '                 HARDWARE IMAGE ARRAY
  63.  
  64.             VV(0).X = W / 2 - V(0).X + camX '   middle vertex
  65.             VV(0).Z = H / 2 - V(0).Y + camZ
  66.             VV(0).Y = vyska + camY
  67.  
  68.  
  69.             VV(1).X = W / 2 - V(1).X + camX '   left upper vertex
  70.             VV(1).Z = H / 2 - V(1).Y + camZ
  71.             VV(1).Y = dno + camY
  72.  
  73.             VV(2).X = W / 2 - V(2).X + camX '   right upper vertex
  74.             VV(2).Z = H / 2 - V(2).Y + camZ
  75.             VV(2).Y = dno + camY
  76.  
  77.             VV(3).X = W / 2 - V(3).X + camX '   right bottom vertex
  78.             VV(3).Z = H / 2 - V(3).Y + camZ
  79.             VV(3).Y = dno + camY
  80.  
  81.             VV(4).X = W / 2 - V(4).X + camX '   left bottom vertex
  82.             VV(4).Z = H / 2 - V(4).Y + camZ
  83.             VV(4).Y = dno + camY
  84.  
  85.  
  86.             '3D with _MAPTRIANGLE is based on OpenGL, so coordinates here are 0,0,-1 in middle screen, to left is X negative, to right is X positive, for up is Y positive, for down is Y negative,
  87.             'for inward is Z negative (to -10000) and for outward is bigger to -1. If is Z higher than -1, is unvisible, is out of the screen.
  88.  
  89.  
  90.  
  91.  
  92.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(4).X, V(4).Y)-(V(0).X, V(0).Y), imh& TO(VV(1).X, VV(1).Y, VV(1).Z)-(VV(4).X, VV(4).Y, VV(4).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'a
  93.             _MAPTRIANGLE (V(4).X, V(4).Y)-(V(3).X, V(3).Y)-(V(0).X, V(0).Y), imh& TO(VV(4).X, VV(4).Y, VV(4).Z)-(VV(3).X, VV(3).Y, VV(3).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'b
  94.             _MAPTRIANGLE (V(3).X, V(3).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(VV(3).X, VV(3).Y, VV(3).Z)-(VV(2).X, VV(2).Y, VV(2).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'c
  95.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(VV(1).X, VV(1).Y, VV(1).Z)-(VV(2).X, VV(2).Y, VV(2).Z)-(VV(0).X, VV(0).Y, VV(0).Z) 'd
  96.         NEXT x
  97.     NEXT y
  98.     _DISPLAY
  99.     _LIMIT 50 'if you use higher resolution (more quads) in lines 19, 20, maybe delete or overwrite this limit.
  101.  
  102.  
Logged

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #4 on: November 03, 2018, 07:06:48 pm »
Hi Bplus. Thank for your interest. Is it so enough?

Code: QB64: [Select]
  1. image = _LOADIMAGE("dyne01.jpg", 32)
  2. imag = _NEWIMAGE(1024, 768, 32)
  3. _PUTIMAGE (_WIDTH(image), _HEIGHT(image))-(0, 0), image, imag ' downsizing image to one size
  4.  
  5. imh& = _COPYIMAGE(imag, 33) '      hardware image are need for real 3D maptriangle use
  7.     X AS SINGLE
  8.     Y AS SINGLE
  9.     Z AS SINGLE
  11.  
  12.  
  13. W = _WIDTH(imag)
  14. H = _HEIGHT(imag)
  15.  
  16. prvkuX = 150 '                       image "compression" ratio (do quads in this steps)
  17. prvkuY = 150
  18.  
  19. pX = W / prvkuX
  20. pY = H / prvkuY
  21. DIM V(4) AS V '                              SOFTWARE IMAGE ARRAY
  22. DIM px(4), O(4) AS V
  23.  
  24. SCREEN _NEWIMAGE(W * 2, H * 2, 32)
  26.  
  27. camX = -200
  28. camY = -100
  29. camZ = -800
  30.  
  31.  
  33.  
  34.     FOR y = 0 TO H - 1 STEP pY
  35.         FOR x = 0 TO W - 1 STEP pX
  36.  
  37.             vyska = 125 '                   upper vertex for pyramide
  38.             dno = 100 '                     bottom vertexes for pyramide
  39.  
  40.             '                               2D Sources
  41.             V(0).X = x - (pX / 2) '         middle
  42.             V(0).Y = y - (pY / 2)
  43.  
  44.             V(1).X = x - pX '               left upper vertex '           1+--------------+2
  45.             V(1).Y = y - pY '                                              |\     d     / |
  46.             '                                                              |   \  0  /    |
  47.             V(2).X = x '                    right upper vertex  '          | a    +    c  |
  48.             V(2).Y = y - pY '                                              |   /    \     |
  49.             '                                                              |/     b    \  |
  50.             V(3).X = x '                    right bottom vertex           4+--------------+3
  51.             V(3).Y = y
  52.  
  53.             V(4).X = x - pX '               left bottom vertex
  54.             V(4).Y = y
  55.  
  56.  
  57.             'recalculating for 3D _MAPTRIANGLE use
  58.  
  59.             DIM VV(4) AS V '                 HARDWARE IMAGE ARRAY
  60.  
  61.             VV(0).X = W / 2 - V(0).X + camX '   middle vertex
  62.             VV(0).Z = H / 2 - V(0).Y + camZ
  63.             VV(0).Y = vyska + camY
  64.  
  65.  
  66.             VV(1).X = W / 2 - V(1).X + camX '   left upper vertex
  67.             VV(1).Z = H / 2 - V(1).Y + camZ
  68.             VV(1).Y = dno + camY + 10
  69.  
  70.             VV(2).X = W / 2 - V(2).X + camX '   right upper vertex
  71.             VV(2).Z = H / 2 - V(2).Y + camZ
  72.             VV(2).Y = dno + camY + 10
  73.  
  74.             VV(3).X = W / 2 - V(3).X + camX '   right bottom vertex
  75.             VV(3).Z = H / 2 - V(3).Y + camZ
  76.             VV(3).Y = dno + camY
  77.  
  78.             VV(4).X = W / 2 - V(4).X + camX '   left bottom vertex
  79.             VV(4).Z = H / 2 - V(4).Y + camZ
  80.             VV(4).Y = dno + camY
  81.  
  82.  
  83.             '3D with _MAPTRIANGLE is based on OpenGL, so coordinates here are 0,0,-1 in middle screen, to left is X negative, to right is X positive, for up is Y positive, for down is Y negative,
  84.             'for inward is Z negative (to -10000) and for outward is bigger to -1. If is Z higher than -1, is unvisible, is out of the screen.
  85.  
  86.             rotation = rotation + .0001
  87.  
  88.             sinr! = SIN(-rotation / 57.2957795131): cosr! = COS(-rotation / 57.2957795131)
  89.             FOR i& = 0 TO 4
  90.                 x2& = ((VV(i&).X * cosr!) + (sinr! * VV(i&).Z)) + VV(i&).X
  91.                 y2& = ((VV(i&).Z * cosr!) - (VV(i&).X * sinr!)) + VV(i&).Z
  92.  
  93.                 O(i&).X = x2& + VV(i&).X
  94.                 O(i&).Z = VV(i&).Z + y2&
  95.                 O(i&).Y = VV(i&).Y - 200
  96.             NEXT
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(4).X, V(4).Y)-(V(0).X, V(0).Y), imh& TO(O(1).X, O(1).Y, O(1).Z)-(O(4).X, O(4).Y, O(4).Z)-(O(0).X, O(0).Y, O(0).Z), _SMOOTH 'a
  105.             _MAPTRIANGLE (V(4).X, V(4).Y)-(V(3).X, V(3).Y)-(V(0).X, V(0).Y), imh& TO(O(4).X, O(4).Y, O(4).Z)-(O(3).X, O(3).Y, O(3).Z)-(O(0).X, O(0).Y, O(0).Z), _SMOOTH 'b
  106.             _MAPTRIANGLE (V(3).X, V(3).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(O(3).X, O(3).Y, O(3).Z)-(O(2).X, O(2).Y, O(2).Z)-(O(0).X, O(0).Y, O(0).Z), _SMOOTH 'c
  107.             _MAPTRIANGLE (V(1).X, V(1).Y)-(V(2).X, V(2).Y)-(V(0).X, V(0).Y), imh& TO(O(1).X, O(1).Y, O(1).Z)-(O(2).X, O(2).Y, O(2).Z)-(O(0).X, O(0).Y, O(0).Z), _SMOOTH 'd
  108.         NEXT x
  109.     NEXT y
  110.     _DISPLAY
  111.     _LIMIT 20 'if you use higher resolution (more quads) in lines 19, 20, maybe delete or overwrite this limit.
  113.  
Logged

Offline bplus

  • Global Moderator
  • Forum Resident
  • Posts: 8053
  • b = b + ...
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #5 on: November 03, 2018, 08:53:37 pm »
It is moving fastest when it is largest and best chance to see details is lost.
Logged

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #6 on: November 04, 2018, 03:21:04 am »
Yeah. With close proximity, the GPU has fewer computations and increases speed. Well, I will write something similar and try it better :-D
Logged

Offline TempodiBasic

  • Forum Resident
  • Posts: 1792
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #7 on: November 04, 2018, 08:55:18 am »
It is a good Halloween animation!
:-)
Logged
Programming isn't difficult, only it's  consuming time and coffee

Offline Ashish

  • Forum Resident
  • Posts: 630
  • Never Give Up!
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #8 on: November 05, 2018, 01:12:21 am »
Hi Petr!
Nice work on this!
For speed, you can try doing this in OpenGL (using array buffers).
Logged
if (Me.success) {Me.improve()} else {Me.tryAgain()}


My Projects - https://github.com/AshishKingdom?tab=repositories
OpenGL tutorials - https://ashishkingdom.github.io/OpenGL-Tutorials

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #9 on: November 05, 2018, 03:19:29 pm »
Hi Ashish. I like to see you here after a long time! Yes, with OpenGL the solution is here. I'm sure I'll go back to him, but I'll still be doing some attempts with _MAPTRIANGLE. I assume that QB64 problems with OpenGL will worsen over time (because OpenGL is no longer supported by some OS, instead of Vulkan) so we maybe may see Vulcan in QB64 :-D. Yeah, it's more like a dream.
Logged

Offline SMcNeill

  • QB64 Developer
  • Forum Resident
  • Posts: 3972
    • View Profile
    • Steve’s QB64 Archive Forum
Re: MAPTRIANGLE in 3D
« Reply #10 on: November 05, 2018, 03:53:06 pm »
Molten might be the way for us to go in the future:  https://moltengl.com

Quote
Molten GL provides the power to transform your graphics applications and games on iOS and macOS platforms. This premier product from the developers of MoltenVK will run your OpenGL ES 2.0 application or game on iOS or macOS using Metal — and faster!

No need to rewrite rendering logic and shaders for different platforms or abandon the familiar OpenGL ES 2.0 API. Applications built for OpenGL ES 2.0 can use MoltenGL to run on top of Metal, to gain the additional graphic performance of Metal today, and to protect your investments in OpenGL ES into the future!
« Last Edit: November 08, 2018, 08:33:10 am by SMcNeill »
Logged
https://github.com/SteveMcNeill/Steve64 — A github collection of all things Steve!

Offline Ashish

  • Forum Resident
  • Posts: 630
  • Never Give Up!
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #11 on: November 08, 2018, 08:21:02 am »
Quote from: Petr on November 05, 2018, 03:19:29 pm
Hi Ashish. I like to see you here after a long time! Yes, with OpenGL the solution is here. I'm sure I'll go back to him, but I'll still be doing some attempts with _MAPTRIANGLE. I assume that QB64 problems with OpenGL will worsen over time (because OpenGL is no longer supported by some OS, instead of Vulkan) so we maybe may see Vulcan in QB64 :-D. Yeah, it's more like a dream.
If OpenGL is going to be loose its support from some OS then, _MAPTRIANGLE will also not work, since _MAPTRIANGLE itself uses some GL commands internally.
Logged
if (Me.success) {Me.improve()} else {Me.tryAgain()}


My Projects - https://github.com/AshishKingdom?tab=repositories
OpenGL tutorials - https://ashishkingdom.github.io/OpenGL-Tutorials

FellippeHeitor

  • Guest
Re: MAPTRIANGLE in 3D
« Reply #12 on: November 08, 2018, 08:24:58 am »
We're not removing OpenGL support. Also, everything indicates we'll be back as normal in macOS in the upcoming 10.14.2 version of their OS.
Logged

Offline Ashish

  • Forum Resident
  • Posts: 630
  • Never Give Up!
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #13 on: November 08, 2018, 09:47:58 am »
Quote from: FellippeHeitor on November 08, 2018, 08:24:58 am
We're not removing OpenGL support. Also, everything indicates we'll be back as normal in macOS in the upcoming 10.14.2 version of their OS.
Thank God! :)
Logged
if (Me.success) {Me.improve()} else {Me.tryAgain()}


My Projects - https://github.com/AshishKingdom?tab=repositories
OpenGL tutorials - https://ashishkingdom.github.io/OpenGL-Tutorials

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
    • View Profile
Re: MAPTRIANGLE in 3D
« Reply #14 on: November 08, 2018, 12:55:33 pm »
I  also like restoring QB64 functionality to all supported systems. I will add to this thread the transcript of these OpenGL samples in the future. (so if we take Galleon's pattern, it will never be :-D) The display principle is the same (the OpenGL and 3D MAPTRIANGLE coordinate system), of course for 3D MAPTRIANGLE it is necessary to add a lot of already completed functions that OpenGL internally supports, such as a color transition from top to top, or _glrotatef (through modified ROTOZOOM), and I'm not talking about lighting. Again, using _MAPTRIANGLE, it is easier to perform texture than opens in OpenGL, where I have not yet come up with the reason why freeing texture work not right (with gl statement) and where I am very sorry for the miserable internal GLUT support. The tea pot, she sent me to the ground. The reason for her removal is..... and cause UNCOMPATIBILTY....  no, better no comment.

Problem with the buffer and speed, pointed out by BPlus, I assume that the _DEPTHBUFFER command should resolve this issue.

I do not want to hurt anyone here who is trying to support the flourishing QB64. I'm glad for it. Teapot is the only thing I do not take as a step forward. Well, gentlemen, I'm going to go into the depths of the code, I did not have time. I had to change the gutter on the roof. He was already very rusted Yeah. I sometimes do this too.
« Last Edit: November 08, 2018, 12:56:41 pm by Petr »
Logged
Pages: [1] 2 3 4   Go Up
« previous next »