cellular textures

[fog]

could this be done in an other, more "real", free, language?

Yes but not necessarily any easier.....although it shouldn't be that hard anyway.  You just want one routine to generate the "grid" and another to blur the image.

i meant coding the real thing, like in the website

I hadn't seen the website link until now   That looks pretty simple to me.  The basic code for producing the texture on that site will work in DBPro with only slight modification.  It wont be very fast but it will work.

[fog]

I've knocked up a quick version of that website code to see how fast it is.  Using the current technique it's very slow but that could be speeded up quite a bit with a memblock.

Anyway here's the code.  The texture wraps great and you can get some really nice effects by messing with the colour values.

Code:

sync on
sync rate 60
sync
randomize timer()
dim Function_Return(10)
null=make vector2(1)

global Texture_Width=100
global Texture_Height=100

global Pnt_Qty=10
type pnts
   X as integer
   Y as integer
endtype
dim Pnt(Pnt_Qty) as pnts

for p=1 to Pnt_Qty
   Pnt(p).X=rnd(Texture_Width)
   Pnt(p).Y=rnd(Texture_Height)
next p

type grids
   Dist as float
   Col as integer
endtype
dim Grid(Texture_Width,Texture_Height) as grids

`find distances
Mmin_dist#=999
Mmax_dist#=0
for y=0 to Texture_Height
   for x=0 to Texture_Width
      min_dist#=999
      for p=1 to Pnt_Qty
         for oy=-1 to 1
            for ox=-1 to 1
               dist#=Get_Distance_2D(x+(ox*Texture_Width),y+(oy*Texture_Height),Pnt(p).X,Pnt(p).Y)
               if dist#<min_dist# then min_dist#=dist#
            next ox
         next oy
      next p
      Grid(x,y).Dist=min_dist#
      if Grid(x,y).Dist<Mmin_dist# then Mmin_dist#=Grid(x,y).Dist
      if Grid(x,y).Dist>Mmax_dist# then Mmax_dist#=Grid(x,y).Dist
   next x
next y

`set colours
for y=1 to Texture_Height
   for x=1 to Texture_Width
      Grid(x,y).Col=255*((Grid(x,y).Dist-Mmin_dist#)/(Mmax_dist#-Mmin_dist#))
   next x
next y

`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

repeat
cls 0

for y=0 to Texture_Height
   for x=0 to Texture_Width
      ink rgb(Grid(x,y).Col,Grid(x,y).Col,Grid(x,y).Col),0
      dot x,y
   next x
next y

ink rgb(255,255,255),0
text 0,200,str$(screen fps())
sync
until escapekey()

`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

`Get the distance between 2 points
function Get_Distance_2D(x1#,y1#,x2#,y2#)
x#=x2#-x1#
y#=y2#-y1#
set vector2 1,x#,y#
dist#=length vector2(1)
endfunction dist#

[donny]

wtf, u're amazing:o
i found my mistakes, i just don't know enough of darkbasic yet
its very slow, 4fps:D

[las6]

well it is slow because every time you generate the texture it has to do four distance calculations per pixel.
So if you have a 256x256 texture, that counts as 65536 pixels... and multiplying that by four gives us 262144. That's how many distance calculations are done to generate a single 256x256 texture. And while fog here uses the vector commands (I assume they are slightly faster than pure math) the distance calculation is going to be slow because at some point it will have to do a SQRT() (Square Root) - which is slow compared to the rest of the math.

[fog]

its very slow, 4fps:D

Well it's slow but not that slow   The 4 FPS is because my code example is drawing the texture pixel by pixel every frame.  In reality you would just draw it once, turn it into an image, and then display the image.....which is very very fast.

And you could easily speed the initial image creation up by using memblocks.

[donny]

Well it's slow but not that slow Smiley  The 4 FPS is because my code example is drawing the texture pixel by pixel every frame.  In reality you would just draw it once, turn it into an image, and then display the image.....which is very very fast.

so, the creation of the image 100*100px takes 1/4sec?
i tryed it 800*600 and it was like 0fps (probably 1/3fps, but its an integer, so...)

And you could easily speed the initial image creation up by using memblocks. Smiley

i don't know what memblocks are, if you have some sparetime you could make 'em

actually y'all have to know that i'm not imediatly planning to use this code, i just wanted to show you

[fog]

so, the creation of the image 100*100px takes 1/4sec?
i tryed it 800*600 and it was like 0fps (probably 1/3fps, but its an integer, so...)

Currently yes but it could be made faster.

actually y'all have to know that i'm not imediatly planning to use this code, i just wanted to show you

That's ok.  All coders like to discuss problems and possible solutions.  I bet most of the code we write is never used for anything useful.

[donny]

Currently yes but it could be made faster.
I bet most of the code we write is never used for anything useful.

BUT, i could use it for my upcomming abstract bullet hell shooter.

[fog]

Currently yes but it could be made faster.
I bet most of the code we write is never used for anything useful.

BUT, i could use it for my upcomming abstract bullet hell shooter.

Cool.  Well have a mess around with that code and you can get some pretty neat effects.  Adding animation and a bit of colour is really easy.

[donny]

animation?
with 4fps?

[fog]

animation?
with 4fps?

lol.  Well you pre-generate the textures when the game loads so there will be no slowdown in game.

[donny]

hmm, could be done aesely, but the loading would take eaons

[fog]

hmm, could be done aesely, but the loading would take eaons

Well that depends on how big the texture is and how many frames of animation you need.

And you can be creating the textures in the background while you display a title or options screen.

And once you have created the necessary images why not just save them to disc so they can just be loaded the next time the game is run and are never generated again?

[donny]

And once you have created the necessary images why not just save them to disc so they can just be loaded the next time the game is run and are never generated again?

i planned to do that for other projects in photoshop, but using that in the game would not make it random any more
but, whatever

And you can be creating the textures in the background while you display a title or options screen.

wouldn't that make the optionsscreen slow?

[fog]

And you can be creating the textures in the background while you display a title or options screen.

wouldn't that make the optionsscreen slow?

Well you could run an options screen at 30fps and nobody would ever notice.  Regardless, provided you did it properly, nobody would know the textures were being generated because nothing would slow down.  You just generate the texture one small chunk every frame and not all in one go.

You might well think it's more trouble than it's worth and you could be right but it is possible.