No I’m not kidding; yes it’s the 3rd edition. See the announcement (an interesting read – I loved the first cover proposal), or the front page, or jump right to the table of contents. HTML only for now, though there is an ancient first draft available, but free is pretty great.
You are currently browsing the archive for the Resources category.
The code’s here, but can only be run if you have a Titan V or new RTX card, and if you haven’t installed the Windows 1809 October update.
[I was told “evar” looked like a misspell, so I’m fixing it this time.]
It clearly takes a village to write the book Real-Time Rendering. Ola Olsson pointed out this entertaining bit on Google Scholar:
The fourth edition appears to be Volume 19 Issue 2. The article mentioned does exist, but is the very last reference in the book (#1978). The number of authors on the paper is impressive, quite an increase from the original three for this article. Ansel Adams, among others, gets listed three times as an author – excellent CV padding. My favorite, though, is the description of the article, a quote by Billy Zelsnack used at the beginning of our chapter “The Future.”
I poked around a bit more and found some alternate reality listings, such as this:
In both 4th editions our new three authors don’t show up. More disturbing is that in one universe’s edition Tomas Akenine-Möller also no longer exists (sad, since he’s listed six times as an author in the first image). And a strange universe it is, where the book has 40 citations, despite being out for less than 6 weeks. The prescience of some authors citing it is impressive, with one article published in the year 2000 referencing this fourth edition. Research must be wonderfully accelerated there, with developers being able to read about future breakthroughs that they can then write up.
I enjoyed the previous ray tracing monday two weeks ago, so let’s do it again.
Since it’s been two weeks, two resources:
- “Real-Time Ray Tracing” – this is a free chapter (number 26) of Real-Time Rendering that we just finished and is free for download. 46 pages with a focus on DXR, but also including a detour through everyone’s favorite topic, spatial data structures for efficient ray tracing. Tomas, Angelo, and Seb did the heavy lifting on this one over the past 3 months, I helped edit and added bits where I could.
- Ray Tracing Resources Page – along the way we ran across lots of resources. With the chapter finished as of today, I was inspired to make a page of links, mostly things I don’t want to lose track of myself or found of historical interest. Please do feel free to send me awesome resources to add, etc.
Steve Hollasch mentioned that there’s a “new” (well, new to me – it’s 9 years old) Creative Commons instrument, CC0. Their website has an explanation of the problem with trying to put something you made into the public domain, and how CC0 solves this. Open Knowledge International (no, I never heard of them, either) recommends it, which I’ll take as a good sign. I didn’t know of this CC0 beast, and suspect readers here don’t, either, so now you do. It’s mostly not a license, it’s a “dedication,” a way to ensure that something you created is considered unowned and free to reuse in every country.
If you want to make sure your code is properly credited to you, use something such as the MIT license instead, or some other (often more restrictive) choice. Creative Commons recommends not using their other licenses for code, but rather some common source code license. I’m assuming (it’s not super-clear) that CC0 is also fine for code you’re putting into the public domain. Update: aha, Steve Hollasch sent this follow-up link – CC0 can be applied to code, and that link shows you how to do it.
Update: I received a number of interesting responses from my tweet of this post. David Williams points out that CC0 is approved by the Free Software Foundation for putting code in the public domain, as it has a fallback license for countries where public domain is not recognized. Arvid Gerstmann notes that dual-licensing with CC0 and the MIT license may be an even better option, for those companies where the lawyers haven’t approved the lesser-known CC0 but have approved use of code with the MIT license.
I know this all sounds like “it doesn’t matter, I’m never going to enforce this,” but it does, sadly. With Graphics Gems we made up a license long ago (basically, “don’t be a jerk”) because someone was trying to sell his company to a larger firm, which had some software testing firm test the smaller company’s code for copyright infringements, and various bits of Graphics Gems code popped up. If CC0 had existed, or maybe even the questionable (and rude) WTFPL, we would have gone with that. Happily, there is now the CC0. (tweet)
Now that I’m back from SIGGRAPH, I can catch up on all the things. So here’s one: win a free copy of Real-Time Rendering, 4th Edition. Our publisher is giving away three copies, deadline to enter is August 31.
As far as actually receiving a copy of the book, well, if it’s any consolation, none of us authors have a physical copy at this point, either. Our publisher wrote on August 8th:
This reprint should be in the warehouse within the next 3 weeks. I assume the fulfillment dept will give customer orders priority over author copies.
So it’s a case of the shoemaker’s children go barefoot. Amazon says the book’s back in stock on August 27th.
I do like that the first three chapters are free on Amazon, for Kindle, and Google Play, so I hope that will tide people over until these ship. That this much content was made free was unexpected, a happy decision on the publisher’s part. If you’re done with those chapters and still waiting, don’t forget to read Pete’s now-free books on ray tracing.
I got to see a physical copy of our book at SIGGRAPH, so know such things exist. I also bought the book on Kindle (which at first had some download problem on my iPhone and PC, but downloaded fine the next day) and Google Play (surprised to find it there; same price as Kindle, by some amazing coincidence), as I wanted to see if a layout problem in my local copy was present in the book (happily, it wasn’t – ahhh, the mysteries of LaTeX).
One of the best parts of SIGGRAPH was actually meeting my coauthors. The wild party on the yacht that night in Vancouver Harbor was really something, too, but then I realized I made that up.
OK, everything happened today, so I am believing the concept of time is no longer meaningful.
First, NVIDIA announced its consumer versions of their RTX ray tracing GPUs, which should come as a shock to no one after last week’s Ray Tracing Monday at SIGGRAPH. My favorite “show off the ray tracing” demo was for Battlefield V.
In celebration of the launch of @nvidia Turing ray tracing hardware, I am making my three ray tracing books are available as free pdfs. I have donated half the money people have sent to @hackthehood, a really neat organization. Trace those rays! https://t.co/1vypwui2QH …
— Peter Shirley (@Peter_shirley) August 14, 2018
I love free. To get up to speed on ray tracing, go get the books here (just in case you can’t click on Pete’s link above), or here (our site, which shows related links, reviews, etc.). Then go to the SIGGRAPH DXR ray tracing course site – there’s even an implementation of the example that’s the cover of Pete’s first book.
Up to speed already? Start writing an article for Ray Tracing Gems. At SIGGRAPH we found that a few people thought they had missed the proposals deadline. There is no proposals deadline. The first real deadline is October 15th, for completed articles. We will judge submissions, and may reject some, but our goal is to try to work with any interested authors before then, to make sure they’re writing something we’ll accept. So, you can informally write and bounce ideas off of us. We avoided the “proposals” step in order to give people more time to write and submit their ideas, large and small.
BTW, as far as free goes, we’re aiming to make the e-book version of Ray Tracing Gems free, and also having the authors maintain reprint rights for their works.
All for now. Day’s not over yet.
I finally finished the Sisyphus-like task of putting useful links for RTR4’s references. For this brief moment I think all the links on that page work – enjoy it for the few minutes it lasts (and feel free to send me fixes, though I may blithely ignore these for a bit, as I’m sick to death of this task – no mas!). At the top of the page I note some pleasant tools, such as the Google Scholar search button extension, which saved me a lot of copying and pasting titles.
I’m writing a post mostly because I found this oddity: The classic paper
Torrance, K., and E. Sparrow, “Theory for Off-Specular Reflection from Roughened Surfaces,” Journal of the Optical Society of America, vol. 57, no. 9, pp. 1105-1114, Sept. 1967
is not one Google Scholar knows about in English. It turns up one in Japanese, which was a surprise. Searching on Google as a whole, it turns out Steve Westin still has one squirreled away. Paper archiving is a house of cards, I tells ya.
Next task: work on our main page of resources.
Here’s an update to my previous blog post, on the volatility of web links.
The Twitter post has a bunch of responses, with some useful tidbits in there. Some resources mentioned: HTML5 UP! for free CC templates; gamedev.net has been around for almost 20 years and can act as an archive, gamedevs.org keeps some old presentations around. Go three paragraphs down for some web hosting suggestions. The idea of using the archive.org link as the “real” link is clever (and a bit sad), but assumes archive.org will always be around. Note that publishers such as the ACM allow you to put your published articles up on your homepage, your institution’s website, and on non-commercial repositories. I’m not sure how entities such as ResearchGate (where I’ve seen a number of papers stored) fit into this picture – they appear to be for-profit, e.g., they sell advertising, so I don’t think they fall into any of the ACM’s categories. I appreciate their efforts, but am concerned that papers there may go away because ResearchGate hasn’t been challenged by the ACM or others. Again, long-term durability is a question.
Also see the comments after the original post. My comment on “The sooner these are displaced by open publications like the JCGT, the better” is that, in graphics, there are no other free (to both readers and authors) journals, at least none that I know about. arXiv maybe qualifies. Looking there today, this article seemed like a handy summary, pointing to some resources I hadn’t known of before. But, trying to go to a site they mention in their article, Chrome warns, “Attackers might be trying to steal your information from dgtal.org” – OK, never mind. There might be great stuff at arXiv, but it seems like a firehose (10 articles published in graphics in the last week), without serious peer review. Editorial filtering and peer review is worth a lot. I guess you might be able to use a strategy of putting your preprint at arXiv, sort of like ResearchGate but less questionable (arXiv is run by Cornell). This approach is underutilized within graphics, AFAIK: only 2 papers on our refs page are available this way, vs. 25 for ResearchGate. If someone wants to explain what I’m missing here, great!
Thanks to you all for the followups, and I find my thoughts about the same: corporations come and go, more quickly than we expect. While I have a lot of faith in various institutions, ultimately I think the entity that best looks out for my interests is me. Having my own domain and website is good insurance against the vagaries from change of job status, change of corporate services (or existence), and change of webmaster. Me, I’m a cheapskate: http://erichaines.com is just a subdomain of realtimerendering.com, of which I’m the prime webmaster; we also host a number of other groups as subdomains, such as the Advances in Real-Time Rendering course notes repository and Ke-Sen’s invaluable work tracking conference articles – doing so costs me no time or money, as others maintain them. So another option is to share a domain and host among a bunch of people.
Yes, your own website costs a little money (the price of two cups of Starbucks per month), but admit it: you pay more in a month for your smartphone and internet service provider than the yearly cost for a website. It’s a bit of effort initially to register a domain and set up a website, but once the template and blog are in place, you’re done. Write a new article or slide set, one that took you hours or weeks to create? It’s five minutes to add it to your web page and upload it. Morgan McGuire, Andrew Glassner, and I like bluehost. Sven Bergström likes digitalocean for $5/month hosting, and gives some setup and admin tips. His previous favorite was site5. Sebastien Sylvan likes nearlyfreespeech, which I hadn’t heard of and looks quite cheap for a personal site (like, possibly something like $3.65 a year (plus $12 per Gig stored, or maybe less – the pricing is not clear), with a free Gig download a day), assuming you’re not serving up huge files or don’t get popular; ijprest notes in the comments that Amazon’s S3 hosting is bare bones, just basic hosting, but about as cheap at nearlyfreespeech and is pretty much guaranteed to outlast you.
Oh, and the presentation from 2012 I mentioned in my last post that is no longer available – dead link – is now available again, as Duncan Fewkes sent me a copy and Michal Valient gave me permission to host it. It’s now here – a few minutes work on my part.
Question for the day: if Gmail and Google Docs suddenly went away, would this cause a collapse that would take us back to the 1990’s, 1950’s, or would the loss kick the world all the way back to some time in the 1800’s? Just a thought, you might want to use Google Takeout or other backup method now and then. If nothing else, visiting your Google Takeout site is interesting in that you see the mind-boggling number of databases Google has in your name.