A breakdown on how this shader works:
The first loop is the raymarcher loop with 100 iterations ("i" is the iterator). Raymarching works by starting at the camera origin (in this case, 0,0,0) and stepping forward along the ray direction.
Thanks for the kind words!
There are also some older talks that are less known, but have a lot to offer!
Tomislav from Croteam on Talos Principle 2 environment art - so a lot of concepts from shaders, graphics programming, UE5 https://t.co/ri5sgE2SQJ
or Ali Motisi on making a full game from scratch, with a lot of info about his custom engine https://t.co/C57gHAwd1u
I talked to @wookash_podcast about some low level programing, C++, graphics, 3D, shadertoy, VR and many other (sometimes rabdom) things: https://t.co/ZbVgNf1zs4
The magician himself, @iquilezles joined me to discuss his unique ability of painting pretty pictures with math!
We talk about loads of subjects: demoscene, math, shaders, VR and Quill, graphics and Shadertoy, and more!
Inigo, it was an honor! This is one of the most action-, information-, and insight-packed conversation on this channel! Everyone, give it a listen!
and in Fusion, if using an OCIODisplay node in Fusion before a Saver node for example, it can be set to:
OCIO Config File: Left empty / blank, this should use your config from the path in the Windows Environment Variable: OCIO
I was previously setting explicitly while testing :-)
and in Fusion, for the Grid Icon / LUT Edit setting under OCIO Config: This can be blank to use the Windows Environment Variable OCIO path, or can be set explicitly to the path to your config file.
cg-config-v2.2.0_aces_v1.3_ocio-v2.3.ocio Fusion should pick up the config automatically. Middle mouse drag the node you want to view into the right hand viewport in Fusion. Make sure the grid icon (LUT) is enabled, top right of the viewport's controls. With the down arrow
@BradeskoUrban The older OpenColorIO-Config-ACES 2.1.0 - 2.2.0 for ACES 1.3 / config is here: https://t.co/NcoPINvbOd
This most closely matches the version used by Houdini 20.5 which is: houdini-config-v2.1.0_aces-v1.3_ocio-v2.3.ocio
@BradeskoUrban Not sure how I ended up with this exact cg-config-v2.2.0 / OCIO 2.3 config file:
cg-config-v2.2.0_aces-v1.3_ocio-v2.3.ocio
As the website now shows 2.1.0 for OCIO 2.3:
cg-config-v2.1.0_aces-v1.3_ocio-v2.3.ocio
@BradeskoUrban so am switching to one that matches Houdini's factory OCIO config file.
I got this from links via: OCIO website https://t.co/LjdLElNpS0 Downloads link to here: https://t.co/G5BTbb1bwM
If scene_linear is ACEScg, then there's no transformation. Note that if you change the file rule for .exr files, Karma will also assume that input textures are also in ACEScg color space. So you need to ensure that your textures are indeed in ACEScg color space too."
.exr files in ACEScg, then you should set the color space for .exr files to ACEScg. It all depends on what your client expects (or whomever uses the .exr files). If you do this, Karma will convert from whatever scene_linear is into ACEScg when writing out the .exr file.