In this day and age, manual should be last resort, not the first one. The possibilities of UI these days are so vast and refined the reason to leave software to seek some external documentation should be a rare exception.
If you are learning UE4, then send me a PM. I can help you with any questions you have
is it planned to also improve pixel filtering in cycles x? Having used other renderes in and outside of blender, cycles seems to be the only one that does not filter every sample. It looks as if it only affects object edges and areas with some contrast.
Also it only has any effect with at least two samples whereas other renderers already filter with only 1 sample.
Not that that would be of much use but that already gives a much smoother/filtered look than the current pixelnoise.
I’m also hesitating. The denoising topic is starting to dominate this general Cycles Requests thread, so it’d be appreciated if you could wrap it up, or I can turn it into a dedicated thread if you want to continue the denoising discussion.
I was wondering whether the Cycles architecture would for limiting the secondary effects of emissive surfaces to specific (or no) other elements in the scene. This isn’t entirely an out-of-nowhere request; there are renderers out there that permit emissive surfaces with exclusion lists, allowing for selective illumination. It allows for a number of effects that otherwise force the use of the compositor, with more awkward workflows in terms of keeping the scenes in-sync.
Light linking, groups and Octane like displacement:
Octane and render man have light linking feature, which allows one to exclude certain meshes to not interact with a specific light source. It’s an absolute bomb of a feature especially for product rendering where sometimes you need a light source to only affect a certain object or want to exclude only one object or maybe a collection of objects. Apart from that, most other render engines also have light group feature which allows you to look at multiple lighting scenarios in the compositing phase. Octane happens to have this really amazing way of adding displacement without adding crazy amounts of geometry, since Cycles X is being written from the ground up, I thought these few things would be a nice addition to the engine. These tools are basic and I believe should be included in Cycles X when it finally comes out in October.
This looks snappy as hell indeed. Wonder what’s their recipe. How can displacement work if not with mesh tesselation though ? (diagsplit et al) Do you think it’s some parallax trick, like this one? (Parallax Occlusion Mapping)
I don’t think it could be parallax mapping as it doesn’t work with lower angles, yet here it works perfectly at all angles.I think they might just be using a very “smart” subd mode, where octane adds geometry ONLY where needed to displace. That’s the only thing I can think of. Whatever it is, it’s real good.
Octane’s Texture Displacement seems to be some form of Voxel Rendering. From my limited understanding it’s drawing a strand for every pixel in a texture with the appropriate displacement length. But it’s mixed with something else. It’s extremely awesome, VERY fast and stable in animations. Would be a killer feature if Cycles-X had it.
Here’s a sample (almost everything is Displacement):