Post by inventordave on Mar 31, 2020 17:36:36 GMT
Hi,
I stopped working on the raytracer for a while, and came back to it today. I have implemented the ability to import an .obj file mesh, and generate a group of triangles from it, to render. My raytracer is written in vanilla Javascript rendering to a Canvas in the browser window.
The problem is, my code is unoptimised, and even in my "preview" option of 150x84, it is taking over 1000ms to render each pixel, so about 2.5 mins per row, of 84 rows. As I have MCI, and my noggin's taken a floggin', I don't even know if I've positioned the camera right to get the teddy bear in view [EDIT: I was tired, I've had a nap, ignore this awkward nugget about the camera]... I know how to program, all my tests have passed, and I've been happily playing with my raytracer, but I obvs need to do some serious optimisations, any suggestions? I don't want to wait ~200 mins to see if I get a suitable image....
Thanks!
Lee David O'Dea.
I stopped working on the raytracer for a while, and came back to it today. I have implemented the ability to import an .obj file mesh, and generate a group of triangles from it, to render. My raytracer is written in vanilla Javascript rendering to a Canvas in the browser window.
The problem is, my code is unoptimised, and even in my "preview" option of 150x84, it is taking over 1000ms to render each pixel, so about 2.5 mins per row, of 84 rows. As I have MCI, and my noggin's taken a floggin', I don't even know if I've positioned the camera right to get the teddy bear in view [EDIT: I was tired, I've had a nap, ignore this awkward nugget about the camera]... I know how to program, all my tests have passed, and I've been happily playing with my raytracer, but I obvs need to do some serious optimisations, any suggestions? I don't want to wait ~200 mins to see if I get a suitable image....
Thanks!
Lee David O'Dea.
