Reddit reviews Physically Based Rendering: From Theory to Implementation
We found 9 Reddit comments about Physically Based Rendering: From Theory to Implementation. Here are the top ones, ranked by their Reddit score.
Morgan Kaufmann Publishers
That is the best answer.
There's also No Bullshit Guide to Linear Algebra, Vulkan Programming Guide, Physically Based Rendering, Game Engine Architecture
No problem.
A solid understanding of python & logic also helps, but 90% of the dicking around you'll be doing will be in VEX, which is pretty much just vector math.
The handy thing about Houdini is that geometry operators and shaders are both written in the same language, so you can prototype operations in SOPs and then copy/paste the code/VOPs to the shader context and as long as you remember to handle the space transforms (shaders default to camera space, SOPs default to object space) everything just works.
This masterclass on fluid solvers is fantastic, it's what made DOPs really click for me, this is a good example of the math;
https://vimeo.com/42988999
Other books worth reading;
https://www.amazon.com/Fluid-Simulation-Computer-Graphics-Second/dp/1482232839/ref=sr_1_1?s=books&ie=UTF8&qid=1480804002&sr=1-1&keywords=fluid+simulation+for+computer+graphics+second+edition - full explanation of how fluid solvers work internally, probably overkill for most artists, but helpful if you want to break things, namely FLIP & Pyro.
https://www.amazon.com/Advanced-RenderMan-Creating-Pictures-Kaufmann/dp/1558606181 (this is quite old and deals solely with the old REYES algorithm, but contains a lot of information on how renderers work internally and a lot of it applies to VEX, which was designed to be very similar to RSL).
https://www.amazon.com/Physically-Based-Rendering-Third-Implementation/dp/0128006455/ref=sr_1_1?s=books&ie=UTF8&qid=1480803895&sr=1-1&keywords=physically+based+rendering This is an explanation of the workings of physically based renderers, but it's quite heavy going.
I would also recommend "Physically-based rendering": https://www.amazon.com/Physically-Based-Rendering-Third-Implementation/dp/0128006455/ref=sr_1_1?ie=UTF8&qid=1520055423&sr=8-1&keywords=physically+based+rendering
Shirley's Fundamentals of Computer Graphics is a good textbook.
Pharr's Physically Based Rendering goes more deeply into the fundamentals.
> pbrt3
https://www.amazon.com/Physically-Based-Rendering-Third-Implementation/dp/0128006455
This one?
Thank you so much!
> You'll need a renderer, acceleration structure, scene manager, main class, and object loader at the very least.
Strictly speaking imo you just need render loop and scene graph.
struct Ray { Vector3f start, direction; }
class SceneObject { RenderHit trace(Ray&); }
and
SceneObject& world = ...;
for (y = 0; y < 480; y++) {
for (x = 0; x < 640; x++) {
auto ray = pixel_to_ray(x, y);
auto hit = world.trace(ray);
PutPixel(x, y, hit.emissive_color);
}
}
Then doing acceleration is as simple as adding a BoundingBox object. You can add a scene loader, but you don't really need to; you can just build your scene manually. (This strongly depends on if you want to load existing
.objsand the like or build your scene manually, PoVRay style.)Re BRDFs, just use diffuse to start, it looks reasonable and is trivial. Just get something pretty rendering, then iterate.
If you want a dirt simple scene description format that's trivial to parse, I've had good experiences with something Forth based. You just need identifiers and numbers, there's basically zero high-level grammar to parse. S-expressions are also easy, they're basically just nested arrays or identifiers. Or you can just grab a library and use JSON or XML.
Forth example:
skyground.sky = Y 0- Y 10 plane V1 shine V0 color
skyground.ground = Y V0 plane 0.6 0.4 0.4 vec3f 0.4 0.4 0.6 vec3f checker
skyground = ( -- obj ) sky ground group
Lisp (S-expression) example:
(let
((scene
(group
(plane +Y -Y)
(sphere (vec3f 0 0 5) 1)
(color black (shine white (plane -Y ( 100 Y))))))
(scene' (fuzz (pathtrace 10 scene))))
(render scene')))
Also if you have a lot of money to splurge, Physically Based Rendering: From Theory To Implementation has everything.
Oh by the way: path tracing is trivial to implement and makes your image look a lot better. (Also render a lot slower, but them's the breaks.) Just add random rays in addition to your shadow rays.
Sandbox
Reference
Books
OK, so right now I have three books in question (priority in that order):
What do you think?
> Anybody can sing but not everybody can sing well, that is a skill that takes practice.
Anybody can sing and anybody can sing well but not everyone is born with a good voice plus it takes luck to land yourself to music industry. Good voice is not equal to success. Some of the best voices I have heard on x Factor went completely unsuccessful. Luck, luck and luck + Skills! However, YouTuber need LUCK not skills. Completely irrelevant to what I was saying originally. You are just pushing me to the edge and trying to win. I will advice you to stick to your OP aka "Is Youtuber hard work?". If not, I will not bother replying.
> do not believe you can do what PewDiePie does
I can scream louder than PewDiePie.
> MOST people who work on YouTube make below minimum wage
Really? Source please? Anyway, irrelevant to HARD WORK. IRRELEVANT TO WHAT I SAID! SERIOUSLY! DO YOU EVEN KNOW HOW TO DISCUSS!? angry.gif
> editing, acting, writing/scripting, directing, producing
You wrote such a loooooong post for what? To defend them with no.. umm.. no logic? I'm speechless. I really am.
Btw, I am not anti-YouTuber. I sound like one becaues you are Pro YouTuber who think they work hard.
I am a programmer but I don't whine how my job is hard. However, now I'm going to whine to you. I work on game engine graphic programming side and it is really really really tough. I need to study a lot and get a lot of new skills or I am fired.
What is my everyday life is like?
You see? An average YouTuber have nothing to do and spends most of his time whining how media is insulting them and how they work hard for nothing and haters gonna hate bullshit blah blah blah.. huh.
PS: I only earn around $4000 a month! Companies prefer using their money to advertise their games using YouTubers. Who does nothing other than scream at top of their lungs and here are people like you who call it a hard work.. Try reading this book from amazon using "look inside". You will learn that there is so much to learn before you can even get into a game engine programming job! It is just one of 25 books.
PPS: This is what whining is like.
Edit:
> I downvote ignorance, sorry.
Funny how the ignorant one is you.