Live data from Hacker News

Photorealistic Path Tracer

thume.ca

71–80 of 98 posts

Re: Photorealistic Path Tracer

#71
post #27

Earlier quoted context omitted.

Hah you’re obviously capable. Some big firm will scoop you up no problem.

Truly capable people rarely want to be “scooped up by some big firm”, much less “no problem”.

Half of Google's employees would probably disagree with you.

Re: Photorealistic Path Tracer

#73
post #35

I just wonder why author named ray tracing as path tracing..

> I just wonder why author named ray tracing as path tracing.. Ray casting (1968) was simply casting rays from camera, one per each image pixel, until the ray hits the closest object. Then the pixel gets the color from the object. Ray tracing (1979) made ray casting recursive for three cases: 1. Reflection: The object surface is a perfect mirror, so we calculate the reflection angle from the incoming ray angle, and c…

You almost touched photon mapping there but as long as rays start only from the screen, there is nothing wrong calling anything varying as ray tracing. Limiting reflection count or having multiple rays (monte-carlo) are often aligned with priciples you described.

Re: Photorealistic Path Tracer

#74
post #35

Earlier quoted context omitted.

> I just wonder why author named ray tracing as path tracing.. Ray casting (1968) was simply casting rays from camera, one per each image pixel, until the ray hits the closest object. Then the pixel gets the color from the object. Ray tracing (1979) made ray casting recursive for three cases: 1. Reflection: The object surface is a perfect mirror, so we calculate the reflection angle from the incoming ray angle, and c…

You almost touched photon mapping there but as long as rays start only from the screen, there is nothing wrong calling anything varying as ray tracing. Limiting reflection count or having multiple rays (monte-carlo) are often aligned with priciples you described.

Photon mapping? As in can render diffraction?

Re: Photorealistic Path Tracer

#75
post #69
post #67

Earlier quoted context omitted.

I'm just wondering how people retain the content? I've read a lot of books over the last few years to learn AI/programming ranging from Sutton/Barto's Reinforcement Learning to Scott Meyer's Effective C++ series, and so much of it ends up flying away from my brain.

I'm like this. I find topics fascinating, but I don't have good memory retention. I find that I allow the subjects to influence me rather than creating a catalog of stuff to reference in my brain.

Agreed. I let the author’s brain temporarily take over mine by thinking the words of the book for so long. And, instead of copying the material to my brain, it becomes more of an index. I know these ideas exist, can be referenced, and roughly where to find them if necessary.

Re: Photorealistic Path Tracer

#76

Earlier quoted context omitted.

Yah PBRT was my most important resource for completing this project, way more important than anything I learned in course lectures. I read it cover to cover before doing much, but then made sure I wrote things how I wanted without referencing the book except for a few bits of formula-heavy code I mention in the credits. Definitely the best technical book I've ever read.

How did you read it without falling asleep?

Have you tried reading it? Because PBRT is by far one of the best programming-oriented books I've read.

The literate programming style used works very well, making it easy to follow the code as the authors works it out and how it connects with the math or more abstract ideas.

Of course, it's not light reading so reading it in bed might indeed be sleep inducing. But that's hardly something you can hold against it.

Re: Photorealistic Path Tracer

#77

Earlier quoted context omitted.

The definition of 10x

Apparently, 10x developers even design and build their own keyboards so they can type faster (he really did that): http://thume.ca/2014/09/08/creating-a-keyboard-1-hardware/

It must have been very impressive in 2014, but nowadays DIY keyboards are a big thing. Of course most people just build a kit but designing and building isn't that hard with 3d printers, the QMK firmware and all.

Disclaimer: I'm in the middle of my first keyboard build, modified from an existing 3d-printable design. The left half works already. I'll probably blog about it when it's finished.

Re: Photorealistic Path Tracer

#78
post #27

Earlier quoted context omitted.

Truly capable people rarely want to be “scooped up by some big firm”, much less “no problem”.

Half of Google's employees would probably disagree with you.

Half of google’s engineers are 3D graphics aficionados and can make compelling 3D scenes? There’s a scale of programmer out there: and whatever that scale is for you I put those who canary physics and computer graphics at the top.

Re: Photorealistic Path Tracer

#79
post #67

Earlier quoted context omitted.

He liked the content? I used to read programming books cover to cover 25 years ago when I was in High School/College. I don't do it so much these days, the books aren't as useful and I know too much so most of it ends up being redundant now. If you're learning something new you can consume voraciously.

I'm just wondering how people retain the content? I've read a lot of books over the last few years to learn AI/programming ranging from Sutton/Barto's Reinforcement Learning to Scott Meyer's Effective C++ series, and so much of it ends up flying away from my brain.

You just have to actually use what you read/learn to retain it. But that's common in all fields, not just software. It can be fun to read things without plans to retain/use the information, because that is a skill in its own right: devouring and soaking up knowledge.

Re: Photorealistic Path Tracer

#80

Earlier quoted context omitted.

Half of Google's employees would probably disagree with you.

Half of google’s engineers are 3D graphics aficionados and can make compelling 3D scenes? There’s a scale of programmer out there: and whatever that scale is for you I put those who canary physics and computer graphics at the top.

Given your nickname that reads like you would put yourself at the top. Programming is programming. I've done 3D graphics, real time machine control, OS development, device drivers, game engines and whatever else I've come across in my professional career to date and none of it struck me as being on a different scale as other software development: it all boils down to meticulously specifying your thinking to a machine so that it can repeat what you dreamed up at a much higher speed than a human ever could.

The person that comes up with a sorting algorithm is not on some different scale than the person that makes a game or controls a machine. BTW, I'm not quite sure how to interpret the bird in your sentence.

Post reply on HN