Cycles Requests

24 posts were split to a new topic: Proxy objects

Any chance we can get per path type multipliers for lights? Essentially float values for ray visibility instead of booleans. It really helps in production lighting.

Hi, I saw this being asked on blender artists and there’s been times I’ve missed it. I can’t believe no one asked for it here (apparently) but being able to exclude objects from certain lights is quite important in some cases.


It’s been asked for. This is usually called light linking, and it’s on the cycles roadmap.


I looked for it the way you named it and I found there’s a patch for it already but needs to be reviewed. I hope someone can push it forward and accept it or change wathever is needed since it’s almost there.

1 Like

So it does not seem that there’s hardly any talk on transferring bake data to vertex colour data. In 2.79, we had bake Ambient Occlusion to vertex colour for example, which used Blender Internal. But we have since lost BI Renderer in 2.8. Any talk on getting this incredibly useful feature back? Vertex colours are still necessary! Thanks :slight_smile:

1 Like

mantra can do that. acctualy :smiley:

The latest official NVIDIA Studio driver release supports Optix (no more need for a beta driver).

Now I hope Optix will soon support all Cycles features, including the Ambient Occlusion and Bevel nodes.

Aaaand the GTX line of cards, I’m curious to see the improvment :slight_smile:

1 Like

Dont know if this has been mentioned before, but when you have a scene with geometry far from the origin you start getting precision errors in shading.

Have you guys considered adding a “render in camera space” option, where world zero gets moved to where the camera is relative to the scene?


Basically this: image

There used to be this:

I think it’s helpful to see memory usage and time remaining because it helps with optimizing.

While I don’t think it needs to be as precise (ms) I think time in seconds is very useful. Both total time and time remaining. Then if you change something in the material, you know exactly what is the difference in render time.

something like:

Path Tracing Sample: 56/100
Mem: 537.51 MiB
Previous: 7.3 s
Time: 5.1 s (and raising as is being rendered until the end - then upon new render is moved to “Previous” right above)
Remains: 3.1 s (and lowering as is being rendered)

this way if we add 5.1 s + 3.1 s (and the estimation is good) the render will end up taking 8.2 s which is longer than previous 7.3 s so there was probably done something that makes rendering slower.

Would even be good to separate Memory usage for geometry and textures because those are the biggest influencers anyway,

and in Eevee there could be how long SSR takes and how long Ambient Occlusion takes and how long Shadows take, sometimes when preparing a rendered animation with Eevee it’s good to know these for optimization.


if i remember viewport never had such statistics… the bar u are referencing with memory stats etc was only avable as Final render.

Here is the full screenshot of default cube:)

and here it’s visible that’s 3D View:

through this it’s also visible that smaller the rendered window the lower it’s memory requirement is. Makes sense but can be missed without the Memory usage.

1 Like

Hi @OmarEmaraDev! I noticed that there’s now a random per island attribute. Thanks for that! It’s a much needed addition…
I would like to ask if there’s any plans for having this great suggestion by duarte.framos as well?

random output of the Object Info node would be a “From Dupli” option, so randomness would be kept consistent across multiple object inside one instance of a collection

Though IMHO, from parent gives much more room for control over which get random values.
Having both will be super awesome! :slight_smile:

1 Like

All render engines have Physical sun and sky horizon lighting feature,so can we have this for cycles.

1 Like

Seems like a bold claim. I can understand it is a useful feature, maybe making a proposal on right click select could get some interest. Really all you need is a developer interested and capable of developing the feature.

There is a pretty feature complete addon available at gumroad, here is the blenderartists forum link:


I’m talking about built in feature not 3rd party paid addon,next big thing Luxcore have this feature.why can’t our living legend have the same.

Hey there @brecht !

I’m a VFX professional and a very long-time Blender user. I have a generalist 3D skillset but I am specialized as a digital compositor. I love the Cycles engine and have found it to be very capable, you fine folks are getting closer and closer to feature parity with the commercial render engines, slowly but surely.

The fact that progress is being made is fantastic, you folks are great developers. However, I can’t help but feel that it’s taking too long to implement support for Deep Output with absolutely no indication that it’s in the works or being seriously considered.

There are other things like light selects and built-in World, Object, refWorld and refObject position passes(without having to do strange conversions and workarounds to make them sort of work in comp packages) that also need implementing but Deep Output is a big one. OpenEXR supports the reading and writing of Deep data and has reasonably clear documentation.

I’m aware that generating Deep data and being able to write it are two different things of course. Given that almost all the major engines and packages support Deep Output by now, what exactly is it going to take to get it implemented as a utility pass in Cycles? Looking around, some of the previous mentions of feature requests for it go back as far as 12+ months.

I really don’t mean any offence but non-answers and skirting around the subject have been incredibly frustrating. I genuinely enjoy using Blender and Cycles and believe that having Deep Output would take what is a great render engine and get it on the path to become an amazing render engine that studios would have to be crazy not to adopt, promote and contribute towards.

Kindest Regards & Respects,


It would be a great feature to have, but at the moment there are quite a few features higher on our priority list. Realistically we can’t give a time estimate for it. It’s really the same as other features, we’d need more time and developers to get it done faster.