> ## Content Index > Fetch the complete content index at: https://contextualguides.com/llms.txt > Use this file to discover other available public pages before exploring further. # Three Tenets - URL: https://contextualguides.com/three-tenets/ - Published: 2026-08-09T16:56:58.000Z - Updated: 2026-08-09T16:56:58.000Z - Description: Three things to keep in the back of your head as you progress along your Octane learning journey. - Author: Scott Benson - Tags: foundations, tutorial, general, lighting, materials, #octane-guides, #beginner, #series-Octane Overview, #site-content ## About This Guide This is part of a conceptual, DCC-agnostic series on how OctaneRender works. This guide introduces some foundational theory about how to best get along with OctaneRender during your 3D journey. ### PDF This guide is also available in [📄 PDF format here](https://contextualguides.com/content/files/2026/08/three-tenets-1.pdf) ## Intro and Overview When you're first getting started with Octane (or any new tool or tech), it can feel pretty overwhelming. It's helpful to have a set of principles that you can always look back on to guide more granular decisions. Over the years of studying Octane, I've discovered three tenets that help me in my day-to-day use. You may end up finding different ones, but this is a good starter set (and three things are easy enough to remember). These three things have one thing in common: **Critical thinking**. It's probably the most valuable thing we can develop when learning the technicals of any 3D app. If we can learn to spend some time considering how something may work, and figure out how to ask the right questions, everything else falls into place eventually. ## Tenet #1: Real-world Values|Real-world Values **Important:** "Real-world" is honestly just a memory aid here. What we're really after here are *reasonable* or *plausible* values. No need to sit there with micron-scale calipers or a digital light meter to get perfectly accurate measurements, just make sure the basketball isn't 6 feet tall, the area lights aren't portable suns, and the glass doesn't refract like some impossible sci-fi metamaterial when first starting a scene. In the last guide, we learned that OctaneRender is a spectral, (mostly) unbiased, physically-based path tracer. We still haven't pulled that apart, and won't until the Rendering Overview guide in this series, but it ties in very closely with this tenet. All that means - at the core - is that OctaneRender is designed to work with **physically plausible** values for the lights, materials, cameras, and settings to hit its target of producing **physically plausible** results. This isn't to say we can't use it for weird or abstract imagery, it just means that when we're making our decisions for what we're feeding into it, we need to start with the size, intensity, color, and other properties of something similar in the real world, and then push the values creatively from there. If we do that, we'll make fast friends with OctaneRender and this experience is going to be fun. If we don't, we'll be spending an inordinate amount of time troubleshooting, and it won't be as fun. ### Some examples ![OG061 001 Tenet 1](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG061-001-Tenet-1.jpg) - A real 120 mm lens at f/1.4 has a particular amount of depth of field effect (fairly shallow). With a real world scale head, the render mimics what we'd see in a real photograph. If the subject is 10x too small, the effect is far too pronounced, and we can get texture errors that's we'd have to troubleshoot with ray epsilon and other settings. If it's 10x too large, the DoF effect is pretty much gone, and all the material scales and light scales need to be re-adjusted to start to look realistic again. - A 60-100 watt incandescent bulb (or equivalent) is what's usually found in our actual living room. The default area light in Octane for C4D is about 100 times brighter, which is why all the objects in our 3D living room start melting and catching fire when one's dropped in. It's great if we're lighting a football stadium, but needs to be dialed WAY down for smaller scenes. - Base colors for realistic materials are rarely ever 100% anything. Overly saturated or bright colors will cause the rest of a material to look cartoonish and off. ## Tenet #2: Avoid Conflation|Avoid Conflation This is good to do in any tool, but it's especially useful with a render engine. The short of it is this: **Filter out as much as possible to isolate the effects of the value you're trying to adjust.** It's harder than it sounds, because this is a very complex system. Turning up a main light source or rotating the environment affects EVERYTHING in the scene. Changing a material color mucks with the colors of surrounding objects via reflections and refractions. As an added bonus, working on an isolated part of the scene, lighting, model, material, etc. *greatly* speeds up the render time. This allows you to see results a lot quicker and iterate faster, and isolate pain points that are going to tank the whole scene without having to get into tedious diagnostics later. ### Some examples ![OG061 002 Tenet 2](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG061-002-Tenet-2.jpg) - When setting up the lighting, disable the environment and all the materials and work on one light at a time on basic forms. - When working on a layered material, adjust one layer at a time and then merge them to see how they work together. Within each layer, adjust one setting at a time to see what it does. - When building a scene, leave depth of field, motion blur, and other camera effects off to get the composition right, then start layering those effects on and adjusting them one at a time. ## Tenet #3: Perfection is the Enemy|Perfection is the Enemy This seems counter-intuitive at first - after all, tenet one was spouting off about real-world values. There's realistic, there's reasonable, and then there's *perfect*. Mathematically perfect material things don't exist in the real world. If you look close enough at anything around you, you'll start to see imperfections and variation, even when you didn't think there were any. ### Some examples ![OG061 003 Bevel](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG061-003-Bevel.jpg) - Bevel every edge and corner to catch the light in a convincing way. Nothing is perfectly sharp, not even a Hattori Hanzō blade. - Randomize the color, pattern, or texture across several similar objects - they came off the same assembly line, but didn't all run through the machines exactly the same way. - Roughen, smudge, and smear fingerprints on a glass phone screen. It's one of our most-used items, so it can't stay pristine forever. - Vary up the color temperature and/or intensity in a string of lights. ## Wrap Up 1. Real world values (make the engine happy) 2. Avoid conflation (keep your cortisol levels down) 3. Perfection is the enemy (make your renders look better) And above all, **sharpen those critical thinking skills.** With a bit of up-front context in tow, we can start our journey in earnest by looking at some of the common interface components we'll be using to interact with OctaneRender.