Takua Render

There is a way to model this type of situation for watertight dielectrics with interface tracking: you assign each material a priority value, and a transition between materials occurs when entering that material only if it has a higher priority than your current material. Yining Karl Li has a great article about it: https://blog.yiningkarlli.com/2019/05/nested-dielectrics.html that inspired me to add the feature to my renderer (rayrender.net). The downside to priority tracking (and possibly why PBRT does not include it) is it introduces a lots of overhead to ray traversal due to each ray needing to track a priority list. Modern raytracers use packets of rays for GPU/SIMD operations, and thus minimizing the ray size is extremely important to maximize throughput and minimize cache misses.

https://blog.yiningkarlli.com Writing about computer graphics. Long detailed posts every few months. It's been on a slight pause over the past year, but new stuff coming soon.

> The M1 Max uses 120W when stressing GPU and CPU. The GPU by itself uses around 60W. The article clearly states that it is 120W on the wall. The SoC goes up to 92W. Nowhere it says that the GPU itself uses 60W. You have also glossed over the fact that the article asserts that the MacBook runs at half of the wattage of an Intel system with a RTX 3080, 120W v. 256W. > The M1 Max GPU does use 60W and so do many 3060 Mobiles with worse overall performance A 3060 runs on 60W at the very low end. Usual configurations are 80W and 115W, and the differences in performance between those two are quite noticeable [1]. And again, you seem to focus on gaming, which is fine, but not the target market of a MacBook Pro. Notice that all the games tested are not native, but running on top of Rosetta 2. The M1 Max does great when it comes to video [2], and I would say the same for other workloads [3] [4] that have been, at least historically, where Apple has mostly focused on. > at almost three times the price Citation needed. Three times the price of what? The Intel system used in the Anandtech article is $3,149.00 [5], is the MacBook Pro $9,000? By the way, Nvidia also has pro versions of their GPUs, they don't perform as well in gaming as they do in other tasks, and they really are way more expensive than their consumer counterparts. Are we now going to dismiss a Quadro RTX because it does not do too well running Tomb Raider? [1]…

Some context: During a panel on production renderers at SIGGRAPH [0] it was mentioned that most rendering research was not really usable for production rendering, as those algorithms are unable to handle the complexity of production scenes. Matt Pharr (one of the authors of pbrt [1]) asked the panelists to release production datasets for research purposes. Walt Disney Animation Studios is now following up on his request by releasing these two datasets. Yining Karl Li of Disney [2] and the readme for the Moana dataset [3] have some more info. It's absolutely amazing that Disney is doing this, especially as the license is quite permissive and also allows the usage for non-research purposes. [0] https://dl.acm.org/citation.cfm?id=2927384 [1] http://pbrt.org/ [2] https://blog.yiningkarlli.com/2018/07/disney-animation-datasets.html [3] https://s3-us-west-1.amazonaws.com/assets.disneyanimation.com/island-R…

Ok. Did you see this: https://blog.yiningkarlli.com/2019/05/nested-dielectrics.html And I'm curious how you solve it.

TSO has a performance cost, on M1 this is 10-15% [1] loss from enabling TSO on native arm64 code (not emulated). [1]: https://blog.yiningkarlli.com/2021/07/porting-takua-to-arm-pt2.html

When I viewed Figure 5 [link] at full resolution, the pine tree bark felt to me like a poorly-done bump-mapping tech demo. I think it lacks sharp contrast between the raised and recessed regions (instead having a gradient), and I think the outline/silhouette of the branches are perfectly smooth and unaffected by the bark, and too uniform and slender to look like real trees. [link]: https://blog.yiningkarlli.com/content/images/2021/Oct/takua-on-m1-max/…

Also coming into play during Moana is the hyperion rendering engine, which was first showcased in Big Hero 6: https://www.disneyanimation.com/technology/innovations/hyperion Also, here's an article containing some stills from the movie: http://blog.yiningkarlli.com/2016/11/moana.html

The last point (reflection by front glass versus mechanism access so no front glass) is the only issue I see with it. Other than that I can easily visualize an image that satisfies the prompt. I think that the general idea is a good one because it's satisfable while having multiple competing requirements that impose geometric constraints on the scene without providing an immediate solution to said constraints as well as requiring multiple independent features (caustics, reflections, fluid dynamics, refraction, directional lighting) that are quite complicated to get right. To illustrate that there aren't any contradictions (other than the final bit about the reflection in the glass). Consider a macro shot showing partial hands, partial tweezers, and pocket watch internals. That's much is certainly doable. Now imagine the partial left hand holding a half submerged pocket watch, fingertips of right hand holding front half of tweezers that are clasping a tiny gear, positioned above the work piece with the drop of water falling directly below. Capture the watchmaker's perspective. I could sketch that so an image model capable of 3D reasoning should have no trouble. It's precisely the sort of scene you'd use to test a raytracer. One thing I can immediately think to add is nested dielectrics. Perhaps small transparent glass beads sitting at the bottom of the dish of water with the edge of the pocket watch resting on them, make the dish transparent glass, and place the camera…