(L) [2012/07/13] [tby voxel] [My second ray tracer actually...] Wayback!I have been slowly working through the PBRT book and have been rewriting some of the millions of wrong design decisions I made the first time I implemented my toy JavaScript ray tracer. I want to make a real general purpose JavaScript ray tracing engine because - who really needs performance? [SMILEY :lol:]
Currently, it runs either within the browser or from the command-line (using node.js) but there is no scene description language yet. It reads Wavefront objects and material libraries. The eventual goal is to create an actual (non-trivial) path tracer implemented in pure JS.
Maybe it will be a good research or teaching tool once the interfaces are stable enough to release publicly. It could be an easy way to try out new things out without having a full development environment + libraries at hand.
Some sample images:
[LINK http://imgur.com/a/k3aQR]
An interactive demo of the ray tracer (alpha quality, Google Chrome web browser very much preferred):
[LINK http://fluxjs.s3-website-us-east-1.amazonaws.com/]
NOTE: You must first select a model from the nav-bar up top. I know it isn't the most intuitive thing but the interface is just a rough working demo at the moment.
Jon