Re:Filament: Physically-based rendering engine
by RomainGuy on Friday August 03, 2018 @08:03PM
(#17684544)
Glad you like it. We found it hard to piece together all the information we needed and after reading hundreds of papers and presentations we figured that writing such a document would be helpful to beginners like us (in this field that is).
[ Parent
| on HN ]
Re:Filament: Physically-based rendering engine
by buchanae on Friday August 03, 2018 @10:04PM
(#17684987)
I think my render in Chrome is pretty broken. Here's a screenshot of the top of the page: https://drive.google.com/open?id=1YVtcV-J0JrDyW2pJ6vwgEDsgjO...
Re:Filament: Physically-based rendering engine
by RomainGuy on Friday August 03, 2018 @10:20PM
(#17685041)
Looks like the page wasn't able to load all of its resources. Try to refresh the page until it works. I should make an offline version that doesn't require online processing.
Re:Filament: Physically-based rendering engine
by mkl on Friday August 03, 2018 @11:11PM
(#17685167)
It took multiple reloads for it to work for me on Android Chrome, and was almost unreadable for a couple of minutes (MathJax processing? Tried KaTeX?) due to an enormous right margin. The margin and font(?) changed multiple times.
Is there a PDF version?
Re:Filament: Physically-based rendering engine
by tripzilch on Saturday August 04, 2018 @01:14PM
(#17687628)
Sort of!
The document uses a JS tool called MarkDeep to convert extended MarkDown into styled HTML. Just look at the source, it's 99% plaintext Markdown.
If you read the MarkDeep docs, you'll find that it has a feature to convert the source into PDF instead. I admit I haven't tried this, though.
If it were up to me, I'd do the transform offline and just serve the static HTML instead. And sure, a link to the PDF just to be nice :)
Re:Filament: Physically-based rendering engine
by RomainGuy on Saturday August 04, 2018 @02:36PM
(#17687963)
We just serve straight from the source tree so it's not out of date :)