textures :D

>>2
oooh

also ceiling cat is watching you render

>>2
Hardware or software rendering?

>>4
hardware, i imagine; it's opengl, and i'm pretty sure this machine has some kind of rudimentary hardware opengl implementation (but not completely certain -- it's not like i'm doing anything complex enough for it to matter at this point...).

Why would you draw a bounding box in a way that caused its winding to matter? I mean... last time I did that, I used GL_LINE_LOOP and was done with it.

>>6
because I'm learning, if that wasn't immediately obvious from the screen shots. the first way to do it that occurred to me was to set the polygon mode to lines and draw four quads, so that's what i did.

>>7
Ah, right. Been so long since I've touched polygon modes...

>>12
now make it red :D

>>13

Antialiasing!

I doodled with writing a raytracer once. Shitty it was, but I did it in Haskell and with minimal knowledge of how it's properly supposed to be done.

Pic related.

Mine's in Haskell too!

You're in luck then. CSG is surprisingly simple to do in Haskell. As you can see from the green sphere in my shot -- it's been carved up with two more spheres. Fancy detail: the change in shape can be seen in one of its shadows...

Just out of interest -- how long does yours take to produce a 640x480 image? Mine took around five seconds for the test scene in >>17, singlethreaded (don't know how to parallelize Haskell programs) on a socket 939 AMD64 X2 4400.

Amusingly enough it takes like twenty seconds to compile the Main module with the "-O" flag on. Haskell is serious bizness.

>>20
5 seconds without antialiasing, 23 seconds with, on a 2.33GHz core2duo.
How many lines of code is yours? Mine is around 280 right now..

987, but I use two newlines between toplevel definitions and the thing is split up into five or six modules.

... actually jpg would've been much less stupid. oh well.

boing!

and have some wallpaperage.

Now also in C64 form!

http://www.youtube.com/watch?v=g9TT55hrz90