Author Topic: [Lua] Tiny3D (Read 23331 times)

Loulou 54 · « **Reply #15 on:** September 25, 2011, 10:20:33 am »

Quote from: Chockosta on September 25, 2011, 08:01:53 am

Quote from: Loulou 54 on September 24, 2011, 01:59:28 pm
Quote
but I have to train with 3D
lol %)
Er... What's fun ?

Indeed you've never made 3D.. x)
http://ourl.ca/12034

Chockosta · « **Reply #16 on:** September 25, 2011, 11:29:33 am »

Actually, raycasting is not real 3D.
Moreover, I followed a tutorial to do my raycaster whereas I'm doing tiny3D without any help.

EDIT :
Now it's also possible to draw 3D function...

Adriweb · « **Reply #17 on:** September 26, 2011, 01:57:34 pm »

nice !

Scipi · « **Reply #18 on:** September 26, 2011, 02:23:46 pm »

How do you use this library? Like, how should you store the data to render a 3D object?

Spyro543 · « **Reply #19 on:** September 26, 2011, 02:27:33 pm »

Heh, tesseract. Love it

Levak · « **Reply #20 on:** September 26, 2011, 02:32:51 pm »

Quote from: HOMER-16 on September 26, 2011, 02:23:46 pm

How do you use this library? Like, how should you store the data to render a 3D object?

Two ways I guess :
1) library, like I made for Make3D
2) Using its source code

Chockosta · « **Reply #21 on:** September 26, 2011, 02:33:09 pm »

For now, to render 3D object with tiny3D library, you have to send them to the render() function in the Lua code.
I've made a 3D-viewer in which you can modify vertices and faces with TI-Nspire-Basic. (You can also modify them with the spreadsheet application)
I'll release it soon...

Scipi · « **Reply #22 on:** September 26, 2011, 04:02:13 pm »

Well, what I meant was, I assume you send two tables to the render() function, one for vertices and one for edges. How are those tables formatted?

Suppose I had 8 points in space to make a cube:

[0,0,0][1,0,0][,1,1,0][0,1,0]
[0,0,1][1,0,1][,1,1,1][0,1,1]

How should that data look inside the tables that go to the render function?

Chockosta · « **Reply #23 on:** September 27, 2011, 01:08:36 pm »

New ! Color is supported (and some optimizations) ! I think that it's finished...
New code :

Spoiler For Spoiler:

Code: [Select]

--Lua Tiny3D - By Loic Pujet

function multiplyMatrix(matrix,vector)
 local x=matrix[1][1]*vector[1]+matrix[1][2]*vector[2]+matrix[1][3]*vector[3]
 local y=matrix[2][1]*vector[1]+matrix[2][2]*vector[2]+matrix[2][3]*vector[3]
 local z=matrix[3][1]*vector[1]+matrix[3][2]*vector[2]+matrix[3][3]*vector[3]
 return x,y,z
end

function rotate(vertices,angle,x,y,z)
 local sum=x+y+z
 x,y,z=x/sum,y/sum,z/sum
 local c,s=math.cos(angle),math.sin(angle)
 local matrix={{x*x+(1-x*x)*c,x*y*(1-c)-z*s,x*z*(1-c)+y*s},{x*y*(1-c)+z*s,y*y+(1-y*y)*c,y*z*(1-c)-x*s},{x*z*(1-c)-y*s,y*z*(1-c)+x*s,z*z+(1-z*z)*c}}
 for i,e in pairs(vertices) do
  vertices[i]={multiplyMatrix(matrix,e)}
 end
end

function translate(vertices,x,y,z)
 for i,e in pairs(vertices) do
  vertices[i]={e[1]+x,e[2]+y,e[3]+z}
 end
end

function scale(vertices,x,y,z)
 for i,e in pairs(vertices) do
  vertices[i]={e[1]*x,e[2]*y,e[3]*z}
 end
end

function width() return platform.window:width() end
function height() return platform.window:height() end

function reverseTable(tbl)
 local tbl2={}
 for i,e in ipairs(tbl) do
  tbl2[#tbl-i+1]=e
 end
 return tbl2
end

function replaceFaces(tbl1,tbl2,faces)
 local faces2={}
 for i,e in pairs(tbl1) do
  for j,e2 in pairs(tbl2) do
   if e2 then
    if e==e2 then
     table.insert(faces2,faces[j])
     tbl2[j]=nil
    end
   end
  end
 end
 return reverseTable(faces2)
end

function sortFaces(vertices,faces)
 local faces2,distTbl,facesTbl={},{},{}
 local middle={}
 local dist,xsum,ysum,zsum=0,0,0,0
 for i,e in pairs(faces) do
  xsum,ysum,zsum=0,0,0,0
  for j,e2 in pairs(e) do
   xsum,ysum,zsum=xsum+vertices[e2][1],ysum+vertices[e2][2],zsum+vertices[e2][3]
  end
  middle={xsum/#e,ysum/#e+5,zsum/#e}
   dist=math.sqrt(middle[1]*middle[1]+middle[2]*middle[2]+middle[3]*middle[3])
  table.insert(distTbl,dist)
  table.insert(facesTbl,dist)
 end
 table.sort(distTbl)
 return replaceFaces(distTbl,facesTbl,faces)
end

function renderFaces(gc,vertices,faces,pos,mode,color)
 local polygon={}
 local faces2=sortFaces(vertices,faces)
 for i,e in pairs(faces2) do
  polygon={}
  drawPoly=true
  for j,f in pairs(faces2[i]) do
   if not pos[f] then
    drawPoly=false
   else
    table.insert(polygon,pos[f][1])
    table.insert(polygon,pos[f][2])
   end
  end
  if drawPoly then
   table.insert(polygon,pos[faces2[i][1]][1])
   table.insert(polygon,pos[faces2[i][1]][2])
   if mode==4 or mode==5 then
    gc:setColorRGB(color[1],color[2],color[3])
    gc:fillPolygon(polygon)
   end
   if mode==2 or mode==3 or mode==4 then
    gc:setColorRGB(0,0,0)
    gc:drawPolyLine(polygon)
   end
  end
 end
end

function renderVertices(gc,pos)
 gc:setColorRGB(0,0,0)
 for i,e in pairs(pos) do
  if e then
   gc:fillRect(e[1]-1,e[2]-1,3,3)
  end
 end
end

function render(gc,vertices,faces,mode,color)
 local yDist,pos=0,{}
 for i,e in pairs(vertices) do
  if e[2]>-5 then
   yDist=5/(e[2]+5)
   table.insert(pos,{e[1]*yDist*25+width()/2,height()/2-e[3]*yDist*25})
  else
   table.insert(pos,false)
  end
 end
 if mode==1 or mode==2 then
  renderVertices(gc,pos)
 end
 if mode==2 or mode==3 or mode==4 or mode==5 then
  renderFaces(gc,vertices,faces,pos,mode,color)
 end
end

HOMER-16 :
Here is how the (latest) function render works :
render(gc,vertices,faces,mode,color)
-gc is the graphic context (given in on.paint(gc))
-color is a table which contains RGB values
ex : {200,200,200}
-mode :
1 to render vertices only
2 to render vertices and edges
3 to render edges only
4 to render edges and faces
5 to render faces only
-vertices is a table which contains vertices pos
ex : {{0,0,0},{1,1,1},{1,2,1},{0,1,2}}
-faces is a table which contains table of vertices.
ex : {{1,2,3,4},{1,2,3}}

To render your cube, you should use

Code: [Select]

cubeVertices={{0,0,0},{1,0,0},{1,1,0},{0,1,0},{0,0,1},{1,0,1},{1,1,1},{0,1,1}}
cubeFaces={{1,2,3,4},{1,2,6,5},{2,3,7,6},{3,4,8,7},{4,1,5,8},{5,6,7,8}}
color={200,200,200}

function on.paint(gc)
 render(gc,cubeVertices,cubeFaces,4,color)
end

Scipi · « **Reply #24 on:** September 27, 2011, 01:24:40 pm »

Thank you! That helps alot

DJ Omnimaga · « **Reply #25 on:** September 27, 2011, 01:55:26 pm »

Looks nice Chokosta. I wonder if eventually it could be used for simple models in games like Space Dementia?

Chockosta · « **Reply #26 on:** September 27, 2011, 02:21:09 pm »

That's the point of this engine : games.
I'll try, and I will see if it's fast enough...

DJ Omnimaga · « **Reply #27 on:** September 27, 2011, 02:30:26 pm »

That's good to hear. I hope you don't have too much troubles with speed.

I think Space Dementia ran at about 5 FPS and was very playable.

aeTIos · « **Reply #28 on:** September 28, 2011, 09:53:24 am »

:O
just :O

calc84maniac · « **Reply #29 on:** September 28, 2011, 12:20:39 pm »

Quote from: Levak on September 24, 2011, 10:10:08 am

Quote from: Chockosta on September 24, 2011, 10:09:44 am
On my Clickpad.
Which one is the slowest ?
The CX =)

Computer Software > ClickPad/TouchPad > CX

I thought CX was faster because it didn't have to do grayscale conversion. Or is that just for gc:drawImage()?

Author Topic: [Lua] Tiny3D (Read 23331 times)

Loulou 54

Re: [Lua] Tiny3D

Chockosta

Re: [Lua] Tiny3D

Adriweb

Re: [Lua] Tiny3D

Scipi

Re: [Lua] Tiny3D

Spyro543

Re: [Lua] Tiny3D

Levak

Re: [Lua] Tiny3D

Chockosta

Re: [Lua] Tiny3D

Scipi

Re: [Lua] Tiny3D

Chockosta

Re: [Lua] Tiny3D

Scipi

Re: [Lua] Tiny3D

DJ Omnimaga

Re: [Lua] Tiny3D

Chockosta

Re: [Lua] Tiny3D

DJ Omnimaga

Re: [Lua] Tiny3D

aeTIos

Re: [Lua] Tiny3D

calc84maniac

Re: [Lua] Tiny3D