6
As mentioned, another option is to use Forced Perspective. This is where an object's distance appears to be different to its actual distance due to how it appears and/or moves.
By placing an object in the middle-distance and parenting it to the Camera's location, it can move as if it were actually placed "at infinity" - so that it moves in relation ...
3
It's hard to say for sure without seeing the file.
But I believe you're probably seeing places where the reflections shoot off into infinity.
Let's think about glass, which is one place where you mentioned problems. A ray either goes through the glass or reflects from the glass. You can get vastly differing depths depending on which it does. The depth ...
2
I am by no means used to work much with the compositor, that said, I hope what I am going to show here is not too far from what others would do.
Object Index method:
Activate the Object Index in the View Layer Properties:
Make sure the object in question has its own Object Properties -> Relations->Pass Index:
Render the image with F12 if only that ...
2
I found out that if you press Ctrl + Tab, you can back out of multiple nodes until you reach the first one (first parent).
2
you have added some nodes just for the viewer, but not for the composite node (which is responsible for render output)
1
I found a solution here and it works
scene = bpy.context.scene
for node in scene.node_tree.nodes:
if node.type == 'OUTPUT_FILE':
node.file_slots[0].path = ''
Only top voted, non community-wiki answers of a minimum length are eligible
Related Tags
compositor × 1228nodes × 295
rendering × 273
cycles-render-engine × 227
render-layers × 103
transparency × 90
compositing × 79
image × 61
animation × 56
materials × 56
video-sequence-editor × 56
masking × 54
python × 53
render-passes × 51
blender-internal-render-engine × 46
video × 42
tracking × 40
color × 34
shaders × 33
light × 30
texturing × 29
effects × 29
blur × 29
color-management × 28
scripting × 26