Text Only | Text with Attachments

QB64.org Forum

Active Forums => Programs => Topic started by: SMcNeill on November 19, 2019, 06:25:58 am

Title: Isometric Mapping Demo
Post by: SMcNeill on November 19, 2019, 06:25:58 am
I was thinking of working up a simple little game which utilizes isometric mapping to create a pseudo-3d environment, and I couldn't find a demo of anything similar on the forums.  So, in the spirit of "can do", I did, and here's what I came up with:

Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(1024, 720, 32)
  3.  
  4. DIM SHARED GridSize AS INTEGER
  6. CONST Red = &HFFFF0000, Green = &HFF00FF00
  7. GridSize = 16 'My demo map is only going to be 16x16 pixels
  8.  
  9.  
  10. DIM grid(9, 9) AS _BYTE 'create a grid to layout our map
  11.  
  12. FOR i = 0 TO 9 'and let's create that map.  It's just going to be 4 walls and a floor...
  13.     grid(i, 0) = 1 'wall
  14.     grid(i, 9) = 1
  15.     grid(0, i) = 1
  16.     grid(9, i) = 1
  18.  
  19. FOR y = 1 TO 8
  20.     FOR x = 1 TO 8
  21.         grid(x, y) = 2 'floor
  22.     NEXT
  24.  
  25.  
  26. 'Now, let's just draw grids one at a time to compare.
  27. _PRINTSTRING (100, 80), "Normal 2D grid"
  28. FOR y = 0 TO 9
  29.     FOR x = 0 TO 9
  30.         'normal grid first
  31.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  32.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  33.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  34.         LINE (xpos, ypos)-(xpos2, ypos2), Kolor, BF
  35.         LINE (xpos, ypos)-(xpos2, ypos2), &HFFFFFFFF, B
  36.         'and that's all it takes for the normal grid.  Can't get any simpler for 2d maps!
  37.     NEXT
  39.  
  41.  
  42. _PRINTSTRING (350, 80), "Normal 2D grid in Isometic Perspective"
  43. FOR y = 0 TO 9
  44.     FOR x = 0 TO 9
  45.         'And now, let's do the same thing with our isometic map.
  46.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  47.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  48.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  49.         IsoLine xpos, ypos, xpos2, ypos2, 500, 0, Kolor
  50.         'And that's basically all the takes to rotate our map to make it a 2D isometic perspective
  51.     NEXT
  53.  
  55.  
  56. _PRINTSTRING (350, 360), "Normal 2D grid in 3D Isometic Perspective"
  57. FOR y = 0 TO 9
  58.     FOR x = 0 TO 9
  59.         'And here, I'm going to make it a 3D isometic map
  60.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  61.         IF grid(x, y) = 1 THEN z = 16 ELSE z = 0 'Give my walls a height of 16, for a cube
  62.  
  63.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  64.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  65.         IsoLine3D xpos, ypos, xpos2, ypos2, z, 500, 300, Kolor
  66.     NEXT
  68.  
  69.  
  70.  
  71.  
  72.  
  73.  
  74.  
  75.  
  76.  
  77. FUNCTION CX2I (x AS LONG, y AS LONG) 'Convert Cartesian X To Isometic coordinates
  78.     CX2I = x - y
  80.  
  81. FUNCTION CY2I (x AS LONG, y AS LONG) 'Convert Cartesian Y To Isometic coordinates
  82.     CY2I = (x + y) / 2
  84.  
  85. SUB IsoLine (x, y, x2, y2, xoffset, yoffset, kolor AS _UNSIGNED LONG)
  86.     'since we're drawing a diamond and not a square box, we can't use Line BF.
  87.     'We have to manually down the 4 points of the line.
  88.     LINE (CX2I(x, y) + xoffset, CY2I(x, y) + yoffset)-(CX2I(x2, y) + xoffset, CY2I(x2, y) + yoffset), kolor
  89.     LINE -(CX2I(x2, y2) + xoffset, CY2I(x2, y2) + yoffset), kolor
  90.     LINE -(CX2I(x, y2) + xoffset, CY2I(x, y2) + yoffset), kolor
  91.     LINE -(CX2I(x, y) + xoffset, CY2I(x, y) + yoffset), kolor
  92.     PAINT (CX2I(x, y) + xoffset, CY2I(x, y) + 4), kolor 'and fill the diamond solid
  93.     LINE (CX2I(x, y) + xoffset, CY2I(x, y) + yoffset)-(CX2I(x2, y) + xoffset, CY2I(x2, y) + yoffset), &HFFFFFFFF
  94.     LINE -(CX2I(x2, y2) + xoffset, CY2I(x2, y2) + yoffset), &HFFFFFFFF
  95.     LINE -(CX2I(x, y2) + xoffset, CY2I(x, y2) + yoffset), &HFFFFFFFF
  96.     LINE -(CX2I(x, y) + xoffset, CY2I(x, y) + yoffset), &HFFFFFFFF
  98.  
  99. SUB IsoLine3D (x, y, x2, y2, z, xoffset, yoffset, kolor AS _UNSIGNED LONG)
  100.     'Like IsoLine, we're going to have to draw our lines manually.
  101.     'only in this case, we also need a Z coordinate to tell us how THICK/TALL/HIGH to make our tile
  102.  
  103.     'Let's just do all the math first this time.
  104.     'We need to turn those 4 normal points into 4 isometric points (x, y, x1, y1)
  105.  
  106.     TempX1 = CX2I(x, y) + xoffset: TempY1 = CY2I(x, y) + yoffset
  107.     TempX2 = CX2I(x2, y) + xoffset: TempY2 = CY2I(x2, y) + yoffset
  108.     TempX3 = CX2I(x2, y2) + xoffset: TempY3 = CY2I(x2, y2) + yoffset
  109.     TempX4 = CX2I(x, y2) + xoffset: TempY4 = CY2I(x, y2) + yoffset
  110.  
  111.     'The top
  112.     LINE (TempX1, TempY1 - z)-(TempX2, TempY2 - z), kolor 'draw the diamond
  113.     LINE -(TempX3, TempY3 - z), kolor
  114.     LINE -(TempX4, TempY4 - z), kolor
  115.     LINE -(TempX1, TempY1 - z), kolor
  116.     PAINT (TempX1, TempY1 - z + 4), kolor 'and fill the diamond solid
  117.     LINE (TempX1, TempY1 - z)-(TempX2, TempY2 - z), -1 'and redraw the grid
  118.     LINE -(TempX3, TempY3 - z), -1
  119.     LINE -(TempX4, TempY4 - z), -1
  120.     LINE -(TempX1, TempY1 - z), -1
  121.  
  122.     IF z <> 0 THEN 'no need to draw any height, if there isn't any.
  123.         'the left side
  124.         LINE (TempX4, TempY4 - z)-(TempX4, TempY4), kolor 'draw it
  125.         LINE -(TempX3, TempY3), kolor
  126.         LINE -(TempX3, TempY3 - z), kolor
  127.         LINE -(TempX4, TempY4 - z), kolor
  128.         PAINT (TempX3 - 2, TempY3 - z + 2), kolor 'fill it
  129.         LINE (TempX4, TempY4 - z)-(TempX4, TempY4), -1 'redraw the grid lines
  130.         LINE -(TempX3, TempY3), -1
  131.         LINE -(TempX3, TempY3 - z), -1
  132.         LINE -(TempX4, TempY4 - z), -1
  133.         'and then for the right side
  134.         LINE (TempX3, TempY3 - z)-(TempX3, TempY3), kolor 'draw it
  135.         LINE -(TempX2, TempY2), kolor
  136.         LINE -(TempX2, TempY2 - z), kolor
  137.         LINE -(TempX3, TempY3 - z), kolor
  138.         PAINT (TempX3 + 2, TempY3 - z + 2), kolor 'fill it
  139.         LINE (TempX3, TempY3 - z)-(TempX3, TempY3), -1 'redraw the grid lines
  140.         LINE -(TempX2, TempY2), -1
  141.         LINE -(TempX2, TempY2 - z), -1
  142.         LINE -(TempX3, TempY3 - z), -1
  143.     END IF
  144.  
  145.  
  147.  


It's a simple enough little demo with nothing more than a green floor and red walls, but I think it highlights the process well enough for us.

My question for all you math folks out there: What's a simple little formula to use to get a paint point inside those boxes?  I really don't care for the hardcoded + 2 which I used, as it can paint the wrong things if the user draws a box too small for it.  There should be a simple, failsafe method which we can use that won't paint out of bounds, like this little demo does, but I'll be danged if I can come up with it at the moment.  It's too early in the morning, and I haven't drunk enough coffee, for my brain to work good enough for any more math already...
Title: Re: Isometric Mapping Demo
Post by: STxAxTIC on November 19, 2019, 08:47:55 am
My first thought on this is - what's the end result supposed to look like? That totally influences the beginning...

... Because insert spiel about doing things in proper 3D ... but forgetting that for a second ...

It seems that getting the pseudo-height correct isn't going to be the main problem, but is instead going to be plotting. If you have monsters, projectiles, speech bubbles, or whatever else, the question is how to do draw them in the proper layers so you don't have overlaps? The quick solution I see is to stick your data layers together like a cake, and then slice the scene not horizontally, but in the so-called z-direction (int the screen) from background to foreground. That way, you can just do the painter's algorithm, which is especially easy because of the locked perspective.




Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 19, 2019, 09:09:07 am
You draw it farthest to closest, or, in this case, from 0 to 9.

No need for a spiel on “proper 3D” here; that’s not what we’re doing.  All we’re shooting for here is something like the screenshot below, which is a nice isometric map:

Title: Re: Isometric Mapping Demo
Post by: STxAxTIC on November 19, 2019, 09:27:43 am
If you were just shooting for the screenshot, the project must be finished.

What was the question again?
Title: Re: Isometric Mapping Demo
Post by: Cobalt on November 19, 2019, 10:26:09 am
set your grid size to 10 and you get some issues in the Iso3d view. and the height doesn't seem to be affected by changing the gridsize either.
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 19, 2019, 10:33:31 am
Quote from: Cobalt on November 19, 2019, 10:26:09 am
set your grid size to 10 and you get some issues in the Iso3d view. and the height doesn't seem to be affected by changing the gridsize either.

That’s from the current paint fill routine, as I mentioned above.  I’ll work in a different fill method later, which won’t suffer from that problem.  ;)

(Honestly, I think all I really need to do is draw the grid in a separate step and not during the line drawing/painting process.  It’s those stray white lines that act as a boundary, which I think is the issue.  I’ll do some testing later to see if my assumption is correct, or not.). ;)
Title: Re: Isometric Mapping Demo
Post by: Cobalt on November 19, 2019, 11:23:41 am
Ah, Rereading that its clicking now, must have just been not quite awake the first time through(nightmares of Frost Blossom keeping me up! XD ).

Wonder how hard it would be to make a LINE()-(),,BF that could be used for NON-Square shapes made, which would probably be easier with a TRIANGLE()-()-(), LINECOLOR, FILLCOLOR kind of thing, where FILLCOLOR would act like BF in the line statement so if a fill color is present it would fill otherwise it would just be lines. Would take 2 calls to make a "box" but might be easier in the end. maybe manipulating the image memory directly to fill it.
Title: Re: Isometric Mapping Demo
Post by: Petr on November 19, 2019, 01:21:56 pm
Hi Steve.
Thank you for a nice demonstration. I would solve the textures differently. I would use MAPTRIANGLE 2D because it uses the same coordinate system as normal 2D graphics. I have to study your code deeply because I still miss the Z-axis calculation, even though I'm on steps... At the moment, I have come across the ceiling of my abilities.

I do now some experiments with this total pseudo 3D code:

Code: QB64: [Select]
  1. 'Pseudo3D Cube
  2. SCREEN _NEWIMAGE(640, 480, 32)
  3. 'rotation point is 320, 240. Rotation radius is 100.
  4. 'is needed 8* X, 8* Y, 8* Z
  5.  
  6. DIM X(8), Y(8), Z(8)
  7.  
  8.  
  9. texture = _NEWIMAGE(100, 100, 32)
  10. _DEST texture
  11. CLS , &H0DEED0C4
  12. FOR f = 0 TO 100 STEP 20
  13.     LINE (50 + f, 50 + f)-(50 - f, 50 - f), _RGB32(RND * 255, RND * 255, RND * 255), B
  16. r1 = 100
  17. r2 = 50
  18.  
  20.     i$ = INKEY$
  21.     SELECT CASE i$
  22.         CASE " ": fill = fill + 1: IF fill > 1 THEN fill = 0
  23.         CASE "+": r1 = r1 + 1: r2 = r2 + 1
  24.         CASE "-": r1 = r1 - 1: r2 = r2 - 1
  25.         CASE "*": XX1 = XX1 + 1
  26.         CASE "/": YY1 = YY1 + 1
  27.         CASE "9": XX2 = XX2 + 1
  28.         CASE "8": YY2 = YY2 + 1
  29.  
  30.         CASE "7": XX1 = XX1 - 1
  31.         CASE "6": YY1 = YY1 - 1
  32.         CASE "5": XX2 = XX2 - 1
  33.         CASE "4": YY2 = YY2 - 1
  34.  
  35.  
  36.  
  37.     END SELECT
  38.  
  39.     FOR L = 1 TO 4
  40.         angle = angle + _PI / 2
  41.         X(L) = XX1 + 320 + SIN(angle + r) * r1
  42.         Y(L) = YY1 + 170 + COS(angle + r) * r2
  43.  
  44.         X(4 + L) = XX2 + 320 + SIN(angle + r) * r1
  45.         Y(4 + L) = YY2 + 240 + COS(angle + r) * r2
  46.     NEXT
  47.     angle = 0
  48.     CLS
  49.     SELECT CASE fill
  50.         CASE 0
  51.             FOR d = 1 TO 3
  52.                 LINE (X(d), Y(d))-(X(d + 1), Y(d + 1))
  53.                 LINE (X(d + 4), Y(d + 4))-(X(d + 5), Y(d + 5))
  54.                 LINE (X(d), Y(d))-(X(d + 4), Y(d + 4))
  55.             NEXT
  56.             LINE (X(1), Y(1))-(X(4), Y(4))
  57.             LINE (X(5), Y(5))-(X(8), Y(8))
  58.             LINE (X(4), Y(4))-(X(8), Y(8))
  59.  
  60.         CASE 1
  61.             FOR d = 1 TO 3
  62.                 '   EXIT FOR
  63.                 _MAPTRIANGLE (0, 0)-(99, 0)-(0, 99), texture TO(X(d), Y(d))-(X(d + 1), Y(d + 1))-(X(d + 4), Y(d + 4))
  64.                 _MAPTRIANGLE (99, 0)-(0, 99)-(99, 99), texture TO(X(d + 1), Y(d + 1))-(X(d + 4), Y(d + 4))-(X(d + 5), Y(d + 5))
  65.  
  66.  
  67.             NEXT
  68.  
  69.  
  70.             _MAPTRIANGLE (0, 0)-(99, 0)-(0, 99), texture TO(X(1), Y(1))-(X(4), Y(4))-(X(5), Y(5)) 'last side
  71.             _MAPTRIANGLE (99, 0)-(0, 99)-(99, 99), texture TO(X(4), Y(4))-(X(5), Y(5))-(X(8), Y(8)) 'last side
  72.  
  73.             _MAPTRIANGLE (0, 0)-(99, 0)-(0, 99), texture TO(X(1), Y(1))-(X(4), Y(4))-(X(2), Y(2)) 'ceil
  74.             _MAPTRIANGLE (99, 0)-(0, 99)-(99, 99), texture TO(X(4), Y(4))-(X(2), Y(2))-(X(3), Y(3))
  75.  
  76.             _MAPTRIANGLE (0, 0)-(99, 0)-(0, 99), texture TO(X(5), Y(5))-(X(8), Y(8))-(X(6), Y(6)) 'bottom
  77.             _MAPTRIANGLE (99, 0)-(0, 99)-(99, 99), texture TO(X(8), Y(8))-(X(6), Y(6))-(X(7), Y(7))
  78.  
  79.  
  80.     END SELECT
  81.     r = r + .01
  82.     _DISPLAY
  83.     _LIMIT 25
  85.  

(Use space, +,-,*,/,9,8,7,6,5,4)

Of course, this is just an experimental program, nothing miraculous is expected of it.
Title: Re: Isometric Mapping Demo
Post by: bplus on November 19, 2019, 03:30:38 pm
Nice work Petr! That space option is really cool!

I am trying to find your post on your start to real 3D rendering that STxAxTIC made comment to a month or 2 ago?
Title: Re: Isometric Mapping Demo
Post by: Petr on November 19, 2019, 04:21:17 pm
This? It use hardware images + hardware MAPTRIANGLE https://www.qb64.org/forum/index.php?topic=300.msg102623#msg102623
Title: Re: Isometric Mapping Demo
Post by: bplus on November 19, 2019, 08:22:09 pm
Steve could you just stack cube images, back to front, bottom to top?
Title: Re: Isometric Mapping Demo
Post by: Lucky_Strikez on November 19, 2019, 09:43:28 pm
Super cool work guys! Keep it going
Title: Re: Isometric Mapping Demo
Post by: AndyA on November 19, 2019, 11:29:02 pm
@Steve

The easiest way to do isometric cubes that I can think of is to:

1) Draw an isometric cube, paint the three iso-squares facing viewer with desired color.

2) GET the image.

3) PUT the cubes using grid coordinates plus appropriate X/Y offsets.

Using this method allows you to create as many different colored iso-cubes as desired at run time.

The other thing is that using PUT is a whole lot faster than painting each individual cube face.

Just my 2 cents :)

Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 19, 2019, 11:43:39 pm
What I’ll probably end up using is just a bunch of textures for the walls and then _MAPTRIANGLE them to the proper coordinates.  It seems the fastest/easiest way to go.
Title: Re: Isometric Mapping Demo
Post by: bplus on November 20, 2019, 12:48:37 am
Forget PAINT use fquad (fill quadrilateral) which is just a double ftri (fill triangle):
Code: QB64: [Select]
  1.  
  2. 'this text was fetched
  3. SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  4.     DIM a&
  5.     a& = _NEWIMAGE(1, 1, 32)
  6.     _DEST a&
  7.     PSET (0, 0), K
  8.     _DEST 0
  9.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  10.     _FREEIMAGE a& '<<< this is important!
  12.  
  13. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is diagonal of x4, y4
  14. SUB fquad (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  15.     ftri x1, y1, x2, y2, x4, y4, K
  16.     ftri x3, y3, x2, y2, x4, y4, K
  18.  

Here is demo: https://www.qb64.org/forum/index.php?topic=1905.0
Title: Re: Isometric Mapping Demo
Post by: bplus on November 20, 2019, 02:58:49 pm
Problem gridsize of 10 fixed:
Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(1024, 720, 32)
  3.  
  4. DIM SHARED GridSize AS INTEGER
  6. CONST Red = &HFFFFAACC, Green = &HFF00FF00
  7. GridSize = 10 ' < 10 is causing problems with PAINT
  8.  
  9.  
  10. DIM grid(9, 9) AS _BYTE 'create a grid to layout our map
  11.  
  12. FOR i = 0 TO 9 'and let's create that map.  It's just going to be 4 walls and a floor...
  13.     grid(i, 0) = 1 'wall
  14.     grid(i, 9) = 1
  15.     grid(0, i) = 1
  16.     grid(9, i) = 1
  18.  
  19. FOR y = 1 TO 8
  20.     FOR x = 1 TO 8
  21.         grid(x, y) = 2 'floor
  22.     NEXT
  24.  
  25.  
  26. 'Now, let's just draw grids one at a time to compare.
  27. _PRINTSTRING (100, 80), "Normal 2D grid"
  28. FOR y = 0 TO 9
  29.     FOR x = 0 TO 9
  30.         'normal grid first
  31.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  32.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  33.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  34.         LINE (xpos, ypos)-(xpos2, ypos2), Kolor, BF
  35.         LINE (xpos, ypos)-(xpos2, ypos2), &HFFFFFFFF, B
  36.         'and that's all it takes for the normal grid.  Can't get any simpler for 2d maps!
  37.     NEXT
  39.  
  41.  
  42. _PRINTSTRING (350, 80), "Normal 2D grid in Isometic Perspective"
  43. FOR y = 0 TO 9
  44.     FOR x = 0 TO 9
  45.         'And now, let's do the same thing with our isometic map.
  46.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  47.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  48.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  49.         IsoLine xpos, ypos, xpos2, ypos2, 500, 0, Kolor
  50.         'And that's basically all the takes to rotate our map to make it a 2D isometic perspective
  51.     NEXT
  53.  
  55.  
  56. _PRINTSTRING (350, 360), "Normal 2D grid in 3D Isometic Perspective"
  57. FOR y = 0 TO 9
  58.     FOR x = 0 TO 9
  59.         'And here, I'm going to make it a 3D isometic map
  60.         IF grid(x, y) = 1 THEN Kolor = Red ELSE Kolor = Green
  61.         IF grid(x, y) = 1 THEN z = 16 ELSE z = 0 'Give my walls a height of 16, for a cube
  62.  
  63.         xpos = x * GridSize + 100: ypos = y * GridSize + 100
  64.         xpos2 = xpos + GridSize: ypos2 = ypos + GridSize
  65.         IsoLine3D xpos, ypos, xpos2, ypos2, z, 500, 300, Kolor
  66.     NEXT
  68.  
  69.  
  70.  
  71.  
  72.  
  73.  
  74.  
  75.  
  76.  
  77. FUNCTION CX2I (x AS LONG, y AS LONG) 'Convert Cartesian X To Isometic coordinates
  78.     CX2I = x - y
  80.  
  81. FUNCTION CY2I (x AS LONG, y AS LONG) 'Convert Cartesian Y To Isometic coordinates
  82.     CY2I = (x + y) / 2
  84.  
  85. SUB IsoLine (x, y, x2, y2, xoffset, yoffset, kolor AS _UNSIGNED LONG)
  86.     'since we're drawing a diamond and not a square box, we can't use Line BF.
  87.     'We have to manually down the 4 points of the line.
  88.     LINE (CX2I(x, y) + xoffset, CY2I(x, y) + yoffset)-(CX2I(x2, y) + xoffset, CY2I(x2, y) + yoffset), kolor
  89.     LINE -(CX2I(x2, y2) + xoffset, CY2I(x2, y2) + yoffset), kolor
  90.     LINE -(CX2I(x, y2) + xoffset, CY2I(x, y2) + yoffset), kolor
  91.     LINE -(CX2I(x, y) + xoffset, CY2I(x, y) + yoffset), kolor
  92.     PAINT (CX2I(x, y) + xoffset, CY2I(x, y) + 4), kolor 'and fill the diamond solid
  93.     LINE (CX2I(x, y) + xoffset, CY2I(x, y) + yoffset)-(CX2I(x2, y) + xoffset, CY2I(x2, y) + yoffset), &HFFFFFFFF
  94.     LINE -(CX2I(x2, y2) + xoffset, CY2I(x2, y2) + yoffset), &HFFFFFFFF
  95.     LINE -(CX2I(x, y2) + xoffset, CY2I(x, y2) + yoffset), &HFFFFFFFF
  96.     LINE -(CX2I(x, y) + xoffset, CY2I(x, y) + yoffset), &HFFFFFFFF
  98.  
  99. SUB IsoLine3D (x, y, x2, y2, z, xoffset, yoffset, kolor AS _UNSIGNED LONG)
  100.     'Like IsoLine, we're going to have to draw our lines manually.
  101.     'only in this case, we also need a Z coordinate to tell us how THICK/TALL/HIGH to make our tile
  102.     r = _RED32(kolor): g = _GREEN32(kolor): b = _BLUE32(kolor)
  103.     'Let's just do all the math first this time.
  104.     'We need to turn those 4 normal points into 4 isometric points (x, y, x1, y1)
  105.  
  106.     TempX1 = CX2I(x, y) + xoffset: TempY1 = CY2I(x, y) + yoffset
  107.     TempX2 = CX2I(x2, y) + xoffset: TempY2 = CY2I(x2, y) + yoffset
  108.     TempX3 = CX2I(x2, y2) + xoffset: TempY3 = CY2I(x2, y2) + yoffset
  109.     TempX4 = CX2I(x, y2) + xoffset: TempY4 = CY2I(x, y2) + yoffset
  110.  
  111.     'The top
  112.     'LINE (TempX1, TempY1 - z)-(TempX2, TempY2 - z), kolor 'draw the diamond
  113.     'LINE -(TempX3, TempY3 - z), kolor
  114.     'LINE -(TempX4, TempY4 - z), kolor
  115.     'LINE -(TempX1, TempY1 - z), kolor
  116.     'PAINT (TempX1, TempY1 - z + 4), kolor 'and fill the diamond solid
  117.     fquad TempX1, TempY1 - z, TempX2, TempY2 - z, TempX3, TempY3 - z, TempX4, TempY4 - z, kolor
  118.     '
  119.     'LINE (TempX1, TempY1 - z)-(TempX2, TempY2 - z), -1 'and redraw the grid
  120.     'LINE -(TempX3, TempY3 - z), -1
  121.     'LINE -(TempX4, TempY4 - z), -1
  122.     'LINE -(TempX1, TempY1 - z), -1
  123.  
  124.     IF z <> 0 THEN 'no need to draw any height, if there isn't any.
  125.         'the left side
  126.         'LINE (TempX4, TempY4 - z)-(TempX4, TempY4), kolor 'draw it
  127.         'LINE -(TempX3, TempY3), kolor
  128.         'LINE -(TempX3, TempY3 - z), kolor
  129.         'LINE -(TempX4, TempY4 - z), kolor
  130.         'PAINT (TempX3 - 2, TempY3 - z + 2), kolor 'fill it
  131.         fquad TempX4, TempY4 - z, TempX4, TempY4, TempX3, TempY3, TempX3, TempY3 - z, _RGB32(.25 * r, .5 * g, .75 * b)
  132.         '
  133.         'LINE (TempX4, TempY4 - z)-(TempX4, TempY4), -1 'redraw the grid lines
  134.         'LINE -(TempX3, TempY3), -1
  135.         'LINE -(TempX3, TempY3 - z), -1
  136.         'LINE -(TempX4, TempY4 - z), -1
  137.         'and then for the right side
  138.         'LINE (TempX3, TempY3 - z)-(TempX3, TempY3), kolor 'draw it
  139.         'LINE -(TempX2, TempY2), kolor
  140.         'LINE -(TempX2, TempY2 - z), kolor
  141.         'LINE -(TempX3, TempY3 - z), kolor
  142.         'PAINT (TempX3 + 2, TempY3 - z + 2), kolor 'fill it
  143.         fquad TempX3, TempY3 - z, TempX3, TempY3, TempX2, TempY2, TempX2, TempY2 - z, _RGB32(.75 * r, .3 * g, .3 * b)
  144.  
  145.         'LINE (TempX3, TempY3 - z)-(TempX3, TempY3), -1 'redraw the grid lines
  146.         'LINE -(TempX2, TempY2), -1
  147.         'LINE -(TempX2, TempY2 - z), -1
  148.         'LINE -(TempX3, TempY3 - z), -1
  149.     END IF
  150.  
  151.  
  153.  
  154.  
  155. 'this text was fetched
  156. SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  157.     DIM a&
  158.     a& = _NEWIMAGE(1, 1, 32)
  159.     _DEST a&
  160.     PSET (0, 0), K
  161.     _DEST 0
  162.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  163.     _FREEIMAGE a& '<<< this is important!
  165.  
  166. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is diagonal of x4, y4
  167. SUB fquad (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  168.     ftri x1, y1, x2, y2, x4, y4, K
  169.     ftri x3, y3, x2, y2, x4, y4, K
  171.  
  172.  
  173.  

I also removed all the line drawing for edges and made slight change to red color
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 20, 2019, 03:14:25 pm
Code: [Select]
SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
    STATIC a&
    D = _DEST
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
     _DEST a&
    PSET (0, 0), K
    _DEST D
    _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
END SUB
A few quick changes to the routine which should speed it up just a wee bit.  Speed is one of the primary concerns with any sort of fill routine.  ;)

(Also returned the _DEST to whatever it was previously, and not just the display screen by default.)
Title: Re: Isometric Mapping Demo
Post by: bplus on November 20, 2019, 03:23:38 pm
Quote from: SMcNeill on November 20, 2019, 03:14:25 pm
Code: [Select]
SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
    STATIC a&
    D = _DEST
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
     _DEST a&
    PSET (0, 0), K
    _DEST D
    _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
END SUB
A few quick changes to the routine which should speed it up just a wee bit.  Speed is one of the primary concerns with any sort of fill routine.  ;)

(Also returned the _DEST to whatever it was previously, and not just the display screen by default.)

With STATIC a&, you don't have to _FREEIMAGE a& ?
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 20, 2019, 03:47:25 pm
Quote from: bplus on November 20, 2019, 03:23:38 pm
With STATIC a&, you don't have to _FREEIMAGE a& ?

Nope.  You just make it once, leave it always available, and forget about it.  At its size, what is it?  4 bytes in memory + whatever the internal header structure uses?  Why reserve it, use it, free it, over and over, at that size?
Title: Re: Isometric Mapping Demo
Post by: _vince on November 20, 2019, 04:35:02 pm
Looking good, Steve!
Title: Re: Isometric Mapping Demo
Post by: Cobalt on November 21, 2019, 12:27:49 pm
Would it be possible to make a routine that would make each individual iso-box 1 at a time. like SUB ISOBOX(X,Y,SIZE,HEIGHT) and then you just have to call that over and over to create a grid. No that I think about that might as well name it CUBE.

would It be able to processes the cubes in stages? draw the outer shell, then fill then draw the inner lines? I added an Image of what I mean, as I am terrible at explaining!

thought if it was handled this way using paint might still be an easier and viable solution. might beable to add an option as to if the "back side" lines are drawn or not. (so the cube looks solid not semi transparent)

Title: Re: Isometric Mapping Demo
Post by: SMcNeill on November 21, 2019, 12:32:14 pm
Quote from: Cobalt on November 21, 2019, 12:27:49 pm
Would it be possible to make a routine that would make each individual iso-box 1 at a time. like SUB ISOBOX(X,Y,SIZE,HEIGHT) and then you just have to call that over and over to create a grid. No that I think about that might as well name it CUBE.

would It be able to processes the cubes in stages? draw the outer shell, then fill then draw the inner lines? I added an Image of what I mean, as I am terrible at explaining!

thought if it was handled this way using paint might still be an easier and viable solution. might beable to add an option as to if the "back side" lines are drawn or not. (so the cube looks solid not semi transparent)

You can, as long as the colors are all the same on each side, but what do you do if they’re different?  (Brown dirt sides for a cliff, green grass on top, as an example.)
Title: Re: Isometric Mapping Demo
Post by: bplus on November 21, 2019, 12:39:57 pm
Quote from: Cobalt on November 21, 2019, 12:27:49 pm
Would it be possible to make a routine that would make each individual iso-box 1 at a time. like SUB ISOBOX(X,Y,SIZE,HEIGHT) and then you just have to call that over and over to create a grid. No that I think about that might as well name it CUBE.

would It be able to processes the cubes in stages? draw the outer shell, then fill then draw the inner lines? I added an Image of what I mean, as I am terrible at explaining!

thought if it was handled this way using paint might still be an easier and viable solution. might beable to add an option as to if the "back side" lines are drawn or not. (so the cube looks solid not semi transparent)

I did just that with this: https://www.qb64.org/forum/index.php?topic=1905.0 and I even named it cube2 as cube was from other code I used for model.

There all sorts of cubes you can make. The one demo'd above fit in convenient square for front face 1 quarter of square for easy overlapping of psuedo 3D model, you can put the square face in any of 4 corners, or you can do regular hexagon shapes and grid them out like Hexagonal Life or Hexagonal Minesweeper.

You can use MAPTRIANGLE (2D) to add texture fills instead of ftri or fquad, which use MAPTRIANGLE too, and has to be much faster and more effective than PAINT eg transparent color fills!
Title: Re: Isometric Mapping Demo
Post by: Cobalt on November 21, 2019, 07:07:12 pm
Quote from: SMcNeill on November 21, 2019, 12:32:14 pm
You can, as long as the colors are all the same on each side, but what do you do if they’re different?  (Brown dirt sides for a cliff, green grass on top, as an example.)

what about using iso-boxes? have a horizontal one for top and bottom and then vertical ones for the sides? then each side could be a different color, or even alpha shaded? granted you would have 6 calls for each cube. I don't know, just fartin ideas that could keep it simple line\paint based routines.

Quote from: bplus on November 21, 2019, 12:39:57 pm
You can use MAPTRIANGLE (2D) to add texture fills instead of ftri or fquad, which use MAPTRIANGLE too, and has to be much faster and more effective than PAINT eg transparent color fills!

I mean Maptri would be great for applying textures to the faces, but at sizes <32(or maybe even 24-pushing though) a texture is going to be very limited. I've used DirectQB's maptri function to texture walls in a '3D'ish type dungeon crawl, but I was using full screen 13, textured tris up to 256px hor, and 192px vert. my source texture was 256x256 even for that.(had to be ^2 for DQB though so some of that was lost[if i remember correctly, was over 20y/a now.])
I should try to port that to QB64 actually. Use higher res textures for 640x400 or 800x600.
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 11:12:53 am
Quote from: SMcNeill on November 20, 2019, 03:14:25 pm
Code: [Select]
SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
    STATIC a&
    D = _DEST
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
     _DEST a&
    PSET (0, 0), K
    _DEST D
    _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
END SUB
A few quick changes to the routine which should speed it up just a wee bit.  Speed is one of the primary concerns with any sort of fill routine.  ;)

(Also returned the _DEST to whatever it was previously, and not just the display screen by default.)

Hi Steve,

I found problem with this modified routine of ftri plus a place where neither version of cSleep or your Pause worked.
Code: QB64: [Select]
  2. _TITLE "fTri Tests, click 4 points to draw transparent quad" 'b+ 2019-12-15 discovered a problem with fTri or using it with fQuad
  3.  
  4. CONST xmax = 800, ymax = 600
  5. SCREEN _NEWIMAGE(xmax, ymax, 32)
  6. _SCREENMOVE 300, 40
  7. DIM pi, oldMouse
  8. DIM mx(1 TO 4), my(1 TO 4)
  10.     CLS
  11.     WHILE pi < 4 'get 4 mouse clicks
  12.         _PRINTSTRING (5, 5), SPACE$(20)
  13.         _PRINTSTRING (5, 5), "Need 4 clicks, have" + STR$(pi)
  14.         WHILE _MOUSEINPUT: WEND
  15.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN 'new mouse down
  16.             pi = pi + 1
  17.             mx(pi) = _MOUSEX: my(pi) = _MOUSEY
  18.             CIRCLE (mx(pi), my(pi)), 2
  19.         END IF
  20.         oldMouse = _MOUSEBUTTON(1)
  21.         _DISPLAY
  22.         _LIMIT 60
  23.     WEND
  24.     _PRINTSTRING (5, 5), "Sleeping, click or press key... or esc"
  25.     fquad1 mx(1), my(1), mx(2), my(2), mx(3), my(3), mx(4), my(4), &H880000FF
  26.     _DISPLAY
  27.     ' cSleep 45   '<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< dang!! this is working either !!!!!!!!!!!!!!!!!!!!
  28.     ' Pause 30 ' <<<<<<<<<<<<<<<<<<<< well this isn't working either!!!!!!!!!!!!!!
  29.     SLEEP
  30.     pi = 0 'point index
  32.  
  33.  
  34. ' my original fTri that never had a problem with
  35. ' found at [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]:    http://www.[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]/forum/index.php?topic=14425.0
  36. SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  37.     DIM D AS LONG, a&
  38.     D = _DEST
  39.     a& = _NEWIMAGE(1, 1, 32)
  40.     _DEST a&
  41.     PSET (0, 0), K
  42.     _DEST D
  43.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  44.     _FREEIMAGE a& '<<< this is important!
  46.  
  47. '2019-11-20 Steve saves some time with STATIC and saves and restores last dest
  48. SUB ftri1 (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  49.     DIM D AS LONG
  50.     STATIC a&
  51.     D = _DEST
  52.     IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
  53.     _DEST a&
  54.     PSET (0, 0), K
  55.     _DEST D
  56.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  58.  
  59. ' original fill quad that may be at fault using Steve's fTri version
  60. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
  61. SUB fquad (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  62.     ftri1 x1, y1, x2, y2, x4, y4, K
  63.     ftri1 x3, y3, x2, y2, x4, y4, K
  65.  
  66. 'try a new quad   OK works fine with original fTri but not fTr1 Steves mod
  67. SUB fquad1 (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  68.     ftri1 x1, y1, x2, y2, x3, y3, K
  69.     ftri1 x3, y3, x4, y4, x1, y1, K
  71.  
  72. 'now this original code is not working!
  73. SUB cSleep (secsWait AS DOUBLE) 'wait for keypress or mouseclick, solves midnight problem nicely I think
  74.     DIM wayt AS INTEGER, oldMouse AS INTEGER, k AS LONG, startTime AS DOUBLE
  75.  
  76.     startTime = TIMER
  77.     wayt = 1
  78.     _KEYCLEAR
  79.     WHILE wayt
  80.         WHILE _MOUSEINPUT: WEND
  81.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN wayt = 0
  82.         oldMouse = _MOUSEBUTTON(1) ' <<< this is Steve's cool way to get clear of mouse click
  83.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: wayt = 0
  84.         IF TIMER - startTime < 0 THEN 'past midnight
  85.             IF TIMER + 24 * 60 * 60 - startTime > secsWait THEN wayt = 0
  86.         ELSE
  87.             IF TIMER - startTime >= secsWait THEN wayt = 0
  88.         END IF
  89.         _LIMIT 30
  90.     WEND
  92.  
  93. 'try Steve's Pause, nope doesn't work either!!!!
  94. SUB Pause (time AS _FLOAT)
  95.     DIM ExitTime AS _FLOAT, oldMouse AS INTEGER, k AS LONG
  96.     _KEYCLEAR 'clear the keyboard buffer so we don't automatically exit the routine
  97.     IF time <= 0 THEN ExitTime = 1.18E+1000 ELSE ExitTime = time + TIMER
  98.     DO
  99.         WHILE _MOUSEINPUT: WEND: IF _MOUSEBUTTON(1) AND NOT oldMouse THEN EXIT SUB
  100.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: EXIT SUB 'clear any stray key events so they don't mess with code outside the Pause.
  101.         oldMouse = _MOUSEBUTTON(1)
  102.         _LIMIT 10
  103.     LOOP UNTIL ExitTime < TIMER
  105.  
  106.  
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 11:50:45 am
Hi Steve,

This line added to both cSleep and Pause seems to fix the problem in the code above:
Code: QB64: [Select]
  2.  
where we use _KEYCLEAR, we have to clear old mouse clicks also?

I have not tested updated code elsewhere yet.
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on December 16, 2019, 12:54:35 pm
Quote from: bplus on December 16, 2019, 11:50:45 am
Hi Steve,

This line added to both cSleep and Pause seems to fix the problem in the code above:
Code: QB64: [Select]
  2.  
where we use _KEYCLEAR, we have to clear old mouse clicks also?

I have not tested updated code elsewhere yet.

One thing I see is missing: oldmouse should be set to -1 before the loop starts.

WHILE _MOUSEINPUT: WEND
IF _MOUSEBUTTON(1) = -1 AND oldmouse = 0 THEN...

If we don’t set oldmouse to -1, we’d instantly kick out of the loop if the user had the button down to begin with.

By setting oldmouse to -1 at the start, we treat the routine as if the button was previously held down, and only accept a click once we get confirmation it’s been up, before being pressed down.

^There might be your error.
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 01:25:39 pm
Hi Steve,

That Pause routine came from here:
https://www.qb64.org/forum/index.php?topic=1511.msg111606#msg111606
and was what I based cSleep on.


Setting oldMouse to -1 at start does seem better than my fix. I will test, thanks :)

Any thoughts about fTri? It seems to retain the last transparent color when we use STATIC a& and not _FREEIMAGE.
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on December 16, 2019, 01:32:35 pm
Quote from: bplus on December 16, 2019, 01:25:39 pm
Hi Steve,

That Pause routine came from here:
https://www.qb64.org/forum/index.php?topic=1511.msg111606#msg111606
and was what I based cSleep on.


Setting oldMouse to -1 at start does seem better than my fix. I will test, thanks :)

Any thoughts about fTri? It seems to retain the last transparent color when we use STATIC a& and not _FREEIMAGE.

Several options; as I didn’t think about alpha blending with the static handle.

CLS, 0 could clear the old pixel first.
Or _DONTBLEND a& before using the PSET command (I’d probably just go this route, as DONTBLEND is a speed up over using blend.)

Edit: Went in and preset oldmouse to -1 in the Pause command so it shouldn’t have the previously down glitch anymore.  ;)

Code: [Select]
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32): _DONTBLEND a&
(The above should set a& to no blend mode and then leave it to that, fixing the alpha issue with it.)
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 02:16:04 pm
Quote from: SMcNeill on December 16, 2019, 01:32:35 pm
Several options; as I didn’t think about alpha blending with the static handle.

CLS, 0 could clear the old pixel first.
Or _DONTBLEND a& before using the PSET command (I’d probably just go this route, as DONTBLEND is a speed up over using blend.)

Edit: Went in and preset oldmouse to -1 in the Pause command so it shouldn’t have the previously down glitch anymore.  ;)

Code: [Select]
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32): _DONTBLEND a&
(The above should set a& to no blend mode and then leave it to that, fixing the alpha issue with it.)

Hi Steve,

Reading about _DONTBLEND in help, it says that such will make the background opaque and block the background. When I use transparent colors with fTri, I usually want just a layer of see through color over what's behind. It's looking like I want to stick with original fTri that frees image to keep pure transparent layers going.

Update: confirmed the transparency is lost with _DONTBLEND

Thanks for your thoughts :)
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on December 16, 2019, 02:32:53 pm
Quote from: bplus on December 16, 2019, 02:16:04 pm
Hi Steve,

Reading about _DONTBLEND in help, it says that such will make the background opaque and block the background. When I use transparent colors with fTri, I usually want just a layer of see through color over what's behind. It's looking like I want to stick with original fTri that frees image to keep pure transparent layers going.

Update: confirmed the transparency is lost with _DONTBLEND

Thanks for your thoughts :)

I'm lost as to what the heck is wrong with _DONTBLEND; it appears to work as it should for me:

Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(640, 480, 32)
  3. PSET (0, 0), &HAAFFFFFF

How is the transparency lost?  When _dontblend is used, all we do is set the color to exactly what we specify it to be. 

As for the wiki, I have no idea what the heck this is supposed to mean:

Quote
Use CLS or _DONTBLEND to make a new surface background _ALPHA 255 or opaque.

_DONTBLEND doesn't change the alpha levels.  Unless my experience using it is just overly weird, all it does for us is directly put our specified colors to the image, without trying to blend the alpha levels and such like normal. 

Is there some secret trick to this command that I've been missing all these years??
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 03:08:20 pm
Hi Steve,

Here is my test code for the _DONTBLEND. First run it to see the shade of transparent used with fTri that uses _FREEIMAGE. Then run main code with fQuad1 that runs fTri with the _DONTBLEND, you can see it is full opaque blue and so much lighter because solid.
Code: QB64: [Select]
  2. _TITLE "fTri Tests, click 4 points to draw transparent quad" 'b+ 2019-12-15 discovered a problem with fTri or using it with fQuad
  3.  
  4. CONST xmax = 800, ymax = 600
  5. SCREEN _NEWIMAGE(xmax, ymax, 32)
  6. _SCREENMOVE 300, 40
  7. DIM pi, oldMouse
  8. DIM mx(1 TO 4), my(1 TO 4)
  10.     CLS
  11.     oldMouse = -1
  12.     WHILE pi < 4 'get 4 mouse clicks
  13.         _PRINTSTRING (5, 5), SPACE$(20)
  14.         _PRINTSTRING (5, 5), "Need 4 clicks, have" + STR$(pi)
  15.         WHILE _MOUSEINPUT: WEND
  16.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN 'new mouse down
  17.             pi = pi + 1
  18.             mx(pi) = _MOUSEX: my(pi) = _MOUSEY
  19.             CIRCLE (mx(pi), my(pi)), 2
  20.         END IF
  21.         oldMouse = _MOUSEBUTTON(1)
  22.         _DISPLAY
  23.         _LIMIT 60
  24.     WEND
  25.     _PRINTSTRING (5, 5), "Sleeping, click or press key... or esc"
  26.     'fquad1 mx(1), my(1), mx(2), my(2), mx(3), my(3), mx(4), my(4), &H880000FF '>>>>>>>>>>>>>>>>>>> switch between fquad and fquad1
  27.     fquad mx(1), my(1), mx(2), my(2), mx(3), my(3), mx(4), my(4), &H880000FF '>>>>>>>>>>>>>>>>>>> switch between fquad and fquad1
  28.     _DISPLAY
  29.     cSleep 45 '<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< dang!! this is working either fixed 2019-12-16 2nd time oldMouse = -1 at start
  30.     'Pause 30 ' <<<<<<<<<<<<<<<<<<<< well this isn't working either!!!!!!!!!!!!!! now fixed (2x's, Steves fix was better)
  31.     'SLEEP
  32.     pi = 0 'point index
  34.  
  35.  
  36. ' my original fTri that never had a problem with
  37. ' found at [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]:    http://www.[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]/forum/index.php?topic=14425.0
  38. SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  39.     DIM D AS LONG, a&
  40.     D = _DEST
  41.     a& = _NEWIMAGE(1, 1, 32)
  42.     _DEST a&
  43.     PSET (0, 0), K
  44.     _DEST D
  45.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  46.     _FREEIMAGE a& '<<< this is important!
  48.  
  49. '2019-11-20 Steve saves some time with STATIC and saves and restores last dest
  50. SUB ftri1 (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  51.     DIM D AS LONG
  52.     STATIC a&
  53.     D = _DEST
  54.     IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32): _DONTBLEND a& '<< fix ??
  55.     _DEST a&
  56.     PSET (0, 0), K
  57.     _DEST D
  58.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  60.  
  61. ' original fill quad that may be at fault using Steve's fTri version
  62. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
  63. SUB fquad1 (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  64.     ftri1 x1, y1, x2, y2, x4, y4, K
  65.     ftri1 x3, y3, x2, y2, x4, y4, K
  67.  
  68. 'update 2019-12-16 needs orig fTri
  69. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
  70. SUB fquad (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  71.     ftri x1, y1, x2, y2, x3, y3, K
  72.     ftri x3, y3, x4, y4, x1, y1, K
  74.  
  75. 'update 2019-12-16 in ...test\graphics\fTri tests.bas
  76. SUB cSleep (secsWait AS DOUBLE) 'wait for keypress or mouseclick, solves midnight problem nicely I think
  77.     DIM wayt AS INTEGER, oldMouse AS INTEGER, k AS LONG, startTime AS DOUBLE
  78.  
  79.     oldMouse = -1 '2019-12-16 2nd fix today assume an old mouse click is still active
  80.     startTime = TIMER
  81.     wayt = 1
  82.     _KEYCLEAR
  83.     WHILE wayt
  84.         WHILE _MOUSEINPUT: WEND
  85.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN wayt = 0
  86.         oldMouse = _MOUSEBUTTON(1) ' <<< this is Steve's cool way to get clear of mouse click
  87.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: wayt = 0
  88.         IF TIMER - startTime < 0 THEN 'past midnight
  89.             IF TIMER + 24 * 60 * 60 - startTime > secsWait THEN wayt = 0
  90.         ELSE
  91.             IF TIMER - startTime >= secsWait THEN wayt = 0
  92.         END IF
  93.         _LIMIT 30
  94.     WEND
  96.  
  97. 'try Steve's Pause, nope doesn't work either!!!!
  98. SUB Pause (time AS _FLOAT)
  99.     DIM ExitTime AS _FLOAT, oldMouse AS INTEGER, k AS LONG
  100.  
  101.     _KEYCLEAR 'clear the keyboard buffer so we don't automatically exit the routine
  102.     'WHILE _MOUSEINPUT OR _MOUSEBUTTON(1): WEND 'clear mouse too
  103.     oldMouse = -1 'in case a mouse down still active
  104.     IF time <= 0 THEN ExitTime = 1.18E+1000 ELSE ExitTime = time + TIMER
  105.     DO
  106.         WHILE _MOUSEINPUT: WEND: IF _MOUSEBUTTON(1) AND NOT oldMouse THEN EXIT SUB
  107.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: EXIT SUB 'clear any stray key events so they don't mess with code outside the Pause.
  108.         oldMouse = _MOUSEBUTTON(1)
  109.         _LIMIT 10
  110.     LOOP UNTIL ExitTime < TIMER
  112.  
  113.  
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on December 16, 2019, 03:09:04 pm
Doing some testing at the computer, I sorted out what was wrong with what I told you:

Code: [Select]
SUB ftri1 (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
    DIM D AS LONG
    STATIC a&
    D = _DEST
    IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
    _DEST a&
    _DONTBLEND a& 'set the image to not blend, so your new color will set itself without blending
    PSET (0, 0), K
    _BLEND a& 'but then turn blending on for the image, so when you use _MAPTRIANGLE, it'll blend into the other screen as desired.
    _DEST D
    _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
END SUB
See if the above doesn't work as intended.  ;)

We can't leave blending off with an image, if we want to blend it with another image.  (Which is kind of oddish.  I would think that all we'd care about is the _DEST blending state, not the _SOURCE's as well...)

Have blending off when setting your pixel, then turn it back on before making use of the _MAPTRIANGLE command.  It should fix the issue.  (I think.)

EDIT:

Testing, I think the code works as intended now:
Code: QB64: [Select]
  2. _TITLE "fTri Tests, click 4 points to draw transparent quad" 'b+ 2019-12-15 discovered a problem with fTri or using it with fQuad
  3.  
  4. CONST xmax = 800, ymax = 600
  5. SCREEN _NEWIMAGE(xmax, ymax, 32)
  6. _SCREENMOVE 300, 40
  7. DIM pi, oldMouse
  8. DIM mx(1 TO 4), my(1 TO 4)
  10.     CLS
  11.     oldMouse = -1
  12.     WHILE pi < 4 'get 4 mouse clicks
  13.         _PRINTSTRING (5, 5), SPACE$(20)
  14.         _PRINTSTRING (5, 5), "Need 4 clicks, have" + STR$(pi)
  15.         WHILE _MOUSEINPUT: WEND
  16.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN 'new mouse down
  17.             pi = pi + 1
  18.             mx(pi) = _MOUSEX: my(pi) = _MOUSEY
  19.             CIRCLE (mx(pi), my(pi)), 2
  20.         END IF
  21.         oldMouse = _MOUSEBUTTON(1)
  22.         _DISPLAY
  23.         _LIMIT 60
  24.     WEND
  25.     _PRINTSTRING (5, 5), "Sleeping, click or press key... or esc"
  26.     'fquad1 mx(1), my(1), mx(2), my(2), mx(3), my(3), mx(4), my(4), &H880000FF '>>>>>>>>>>>>>>>>>>> switch between fquad and fquad1
  27.     fquad mx(1), my(1), mx(2), my(2), mx(3), my(3), mx(4), my(4), &H880000FF '>>>>>>>>>>>>>>>>>>> switch between fquad and fquad1
  28.     _DISPLAY
  29.     cSleep 45 '<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< dang!! this is working either fixed 2019-12-16 2nd time oldMouse = -1 at start
  30.     'Pause 30 ' <<<<<<<<<<<<<<<<<<<< well this isn't working either!!!!!!!!!!!!!!
  31.     'SLEEP
  32.     pi = 0 'point index
  34.  
  35.  
  36. ' my original fTri that never had a problem with
  37. ' found at [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]:    http://www.[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]/forum/index.php?topic=14425.0
  38. SUB ftri (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  39.     DIM D AS LONG, a&
  40.     D = _DEST
  41.     a& = _NEWIMAGE(1, 1, 32)
  42.     _DEST a&
  43.     PSET (0, 0), K
  44.     _DEST D
  45.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  46.     _FREEIMAGE a& '<<< this is important!
  48.  
  49. '2019-11-20 Steve saves some time with STATIC and saves and restores last dest
  50. SUB ftri1 (x1, y1, x2, y2, x3, y3, K AS _UNSIGNED LONG)
  51.     DIM D AS LONG
  52.     STATIC a&
  53.     D = _DEST
  54.     IF a& = 0 THEN a& = _NEWIMAGE(1, 1, 32)
  55.     _DEST a&
  56.     _DONTBLEND a&
  57.     PSET (0, 0), K
  58.     _BLEND a&
  59.     _DEST D
  60.     _MAPTRIANGLE _SEAMLESS(0, 0)-(0, 0)-(0, 0), a& TO(x1, y1)-(x2, y2)-(x3, y3)
  62.  
  63. ' original fill quad that may be at fault using Steve's fTri version
  64. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
  65. SUB fquad1 (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  66.     ftri1 x1, y1, x2, y2, x4, y4, K
  67.     ftri1 x3, y3, x2, y2, x4, y4, K
  69.  
  70. 'update 2019-12-16 needs orig fTri
  71. 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
  72. SUB fquad (x1, y1, x2, y2, x3, y3, x4, y4, K AS _UNSIGNED LONG)
  73.     ftri x1, y1, x2, y2, x3, y3, K
  74.     ftri x3, y3, x4, y4, x1, y1, K
  76.  
  77. 'update 2019-12-16 in ...test\graphics\fTri tests.bas
  78. SUB cSleep (secsWait AS DOUBLE) 'wait for keypress or mouseclick, solves midnight problem nicely I think
  79.     DIM wayt AS INTEGER, oldMouse AS INTEGER, k AS LONG, startTime AS DOUBLE
  80.  
  81.     oldMouse = -1 '2019-12-16 2nd fix today assume an old mouse click is still active
  82.     startTime = TIMER
  83.     wayt = 1
  84.     _KEYCLEAR
  85.     WHILE wayt
  86.         WHILE _MOUSEINPUT: WEND
  87.         IF _MOUSEBUTTON(1) AND oldMouse = 0 THEN wayt = 0
  88.         oldMouse = _MOUSEBUTTON(1) ' <<< this is Steve's cool way to get clear of mouse click
  89.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: wayt = 0
  90.         IF TIMER - startTime < 0 THEN 'past midnight
  91.             IF TIMER + 24 * 60 * 60 - startTime > secsWait THEN wayt = 0
  92.         ELSE
  93.             IF TIMER - startTime >= secsWait THEN wayt = 0
  94.         END IF
  95.         _LIMIT 30
  96.     WEND
  98.  
  99. 'try Steve's Pause, nope doesn't work either!!!!
  100. SUB Pause (time AS _FLOAT)
  101.     DIM ExitTime AS _FLOAT, oldMouse AS INTEGER, k AS LONG
  102.  
  103.     _KEYCLEAR 'clear the keyboard buffer so we don't automatically exit the routine
  104.     'WHILE _MOUSEINPUT OR _MOUSEBUTTON(1): WEND 'clear mouse too
  105.     oldMouse = -1 'in case a mouse down still active
  106.     IF time <= 0 THEN ExitTime = 1.18E+1000 ELSE ExitTime = time + TIMER
  107.     DO
  108.         WHILE _MOUSEINPUT: WEND: IF _MOUSEBUTTON(1) AND NOT oldMouse THEN EXIT SUB
  109.         k = _KEYHIT: IF k > 0 THEN _KEYCLEAR: EXIT SUB 'clear any stray key events so they don't mess with code outside the Pause.
  110.         oldMouse = _MOUSEBUTTON(1)
  111.         _LIMIT 10
  112.     LOOP UNTIL ExitTime < TIMER
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 03:26:12 pm
Steve, I think you still have fQuad1 line still commented out and are using fQuad line with the other fTri used.
 I am still seeing a bright solid blue when I uncomment fquad1 and comment fquad.

fquad1 tests with the STATIC a& with _DONTBLEND and fquad tests the working fTri that uses _FREEIMAGE.


Update: OK so I tried testing some other ranges of Alpha and discovered Steve's fix for fTri is working fine and the original fTri isn't registering anything see-able in low ranges of Alpha.

So I am confused, maybe fTri was broken all along? This is sort of the same problem with the version of Titled Ellipse Fill I came up with yesterday, low alpha's are not see-able.
Title: Re: Isometric Mapping Demo
Post by: SMcNeill on December 16, 2019, 10:40:00 pm
Quote from: bplus on December 16, 2019, 03:26:12 pm
Steve, I think you still have fQuad1 line still commented out and are using fQuad line with the other fTri used.
 I am still seeing a bright solid blue when I uncomment fquad1 and comment fquad.

fquad1 tests with the STATIC a& with _DONTBLEND and fquad tests the working fTri that uses _FREEIMAGE.


Update: OK so I tried testing some other ranges of Alpha and discovered Steve's fix for fTri is working fine and the original fTri isn't registering anything see-able in low ranges of Alpha.

So I am confused, maybe fTri was broken all along? This is sort of the same problem with the version of Titled Ellipse Fill I came up with yesterday, low alpha's are not see-able.

Is it just a case of low alpha getting blended out into the background?  Take an image with 255 alpha, blend it with 10 alpha, and it fades it into the background.  Take a background with 0 alpha, blend it with 10 alpha, and it’s going to end up so faded as to be transparent in almost all cases.  (Particularly with my poor eyes an high gamma/contrast settings...)
Title: Re: Isometric Mapping Demo
Post by: bplus on December 16, 2019, 11:06:01 pm
Steve it was the _DONTBLEND / _BLEND thing, not only did it make the Fill Triangle code work better it fixed the problem I had doing tiltled ellipse fills from a Flat Filled Ellipse and RotoZooming the tilt onto the drawing. I guess I misunderstood how drawing transparencies were taking place on a 0 alpha background.
Text Only | Text with Attachments