Topic awaiting preservation: The JavaScript Raytracer version 2.0

Voila!
http://www.slimeland.com/raytrace/

This is the result of a few months of work (on and off, not steady).

If you don't have a clue what to do with it, look for the "Load Preset" dropdown menu, select one from the list, click "Load," and then click "Render" at the bottom of the page.

Large renders of the presets are also displayed in the help file, in which, for the first time, I hit the limit of <h6> and needed an <h7>.

I'm happy to say that it worked fine Opera 7 with almost no tweaking. It should also work in IE5+ (windows) and Mozilla. I wouldn't be surprised if it crashes miserably on IE 5/mac, which seems to have a couple of severe DOM bugs.

Go on now. Have fun with it.

I knew you've been hiding something but... but... shit me. Your a phyco!

Amazing stuff, as always.

Dude, you're not even human...

Sick. Really sick.

Hi,
i think you sold your seoul to the devil , or ?
Great piece of work !!



[This message has been edited by Toadward (edited 02-09-2003).]

That is so really amazing.

Slime: I'm just glad you are on our side

[edit: OK I started an FAQ to keep track of things:

:FAQ:

InI: The link in your raytracing thread to wapod is broken - fancy editing it to the right one?]

___________________
Emps

FAQs: Emperor

Heh, thanks guys =)

Unfortunately, it has two major problems: it's not easy for beginners to use, and it's too slow for more experienced raytracers to use seriously. So it's really nothing more than a toy.

Nonetheless, if it intrigues you, and you make a simple scene of some sort, click the "Save Workspace" button, upload it as a text file, and share it with the rest of us.

Let me know if you get a 404 or something; I don't trust my hosting providers.

Slime: it may be nothing more than a toy, but what a toy you did !
The flower scene in 320x240 took ~1.5 hour on my home computer among which ~12 minutes were spent inactive. Is that time gap due to a setTimeout called after each pixel/ray is rendered ?
Now the ultimate feature would be a tree-view of the scene elements ( I guess the right name is a "scene graph" ) were you could edit/remove them and their properties Coding that thing should only affect the GUI so it shouldn't impact your engine.

Great job!

Mathieu "POÏ" HENRI

[This message has been edited by poi (edited 02-10-2003).]

I've been trying to make something worth while but eh... I suck at this 3D stuff. How the hell did someone make a frigin flower with that?

Fuck .. thats amazing !!!

No wait .. the first one was amazing, I dont know what the hell that is ??

Poi: yup, there's a setTimeout called every second or so. (It does as many pixels as it can, and when either a certain amount of time has passed (I forget how long), or a line is finished, it does a setTimeout.) The setTimeout interval is really short (like 10ms), but the browser often uses that time to catch up on other things, so it ends up being longer. This keeps the browser from freezing (and avoids a "this script is running slowly" message).

Dracusis: Try something simple. The flower was difficult for my friend to make, and shows some of the limitations of the interface. I believe he actually started it in POV-Ray to get the basic petal shape (which is, surprisingly, just a sphere cut out of another sphere) and layout.

By the way, IE 5 users: the "Load Preset" dropdown menu was invisible before; this has been fixed. A silly IE 5 bug makes it invisible for some reason. (You wouldn't *believe* the number of bugs IE has had with this thing. Form elements and the DOM simply don't mix in IE. I now know how to make radio buttons that are comletely uncheckable, dropdown menus that cause crashes, and checkboxes that ignore their "checked" property.)

Hmz, I'd like to say I love it, but since it scares the hell outta me, I guess I don't