Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Dalton Watts

Pages: [1] 2 3 ... 13
Are tonemapping camera controls planned for the Improved lister 2.0? I ask this because they aren't implemented on the newest daily build (2023.01.31).
Yes! A button to open tone mapping editor, maybe also reset, copy, on/off

Great Ondra!

Some suggestions if I may:

1. Set per camera resolution inside the lister with custom presets. (see
2. To be able to add and delete the camera parameters necessary to adjust to ones workflow.


Are tonemapping camera controls planned for the Improved lister 2.0? I ask this because they aren't implemented on the newest daily build (2023.01.31).


We have logged this as a feature request in our system if there will be any update on this, we will let you know.

(Internal ID=1037725204)

Thanks Avi! I was hoping it would be something we could change already in the "Development / Experimental stuff" tab, for example. I guess not.

Not sure if this helps you, but these settings help me get the effect you're describing, without denoising. It's how Corona behaved years ago.

I already have that setup lupaz :-) Not quite the same.

Exactly romullus! Everyone works differently.

can we, as of right now, start the AI denoiser on the first sample in order to simulate default Cycles viewport rendering behavior?

But why? I do not see any argument in your message.
Why is seeing a low-quality, unrefined image worse than seeing the same thing just with additional blurring?

The argument is there. If the AI denoiser starts at the first sample, the interactivity improves even though the first sample has notorious AI artifacts that soon fade away, at least in my view. This combined with GPU support would greatly improve Corona's usability.

[Max] Feature Requests / Persistent data
« on: 2022-12-07, 13:46:57 »
Still, on the Cycles page, would it be possible to implement "Persistent Data" in Corona?

"Persistent Data keeps render data in memory after rendering for faster re-renders and animation renders at the cost of extra memory usage while performing other tasks in Blender".

[Max] Feature Requests / Re: Denoiser Exclude List
« on: 2022-12-04, 13:54:58 »
Will this be implemented in v10? Something like "Denoise by material" or a particular render element that would allow us to manually select what would be denoised similar to what we have with CMasking_Mask.

I was fiddling around with Blender and Cycles and really liked their fluid implementation of Cycles rendering on the viewport.

In Cycles since the viewport is denoising in real-time for every sample, we can set a start sample so that the denoiser doesn't kick in before a set number of samples has already been calculated. That's the default behavior for Cycles. If we change that so the denoiser only kicks in at a later sample it behaves similarly to Corona or V-Ray.

The viewport rendering (similar to viewport IPR on V-ray and the "Interactive rendering in 3ds max viewport" as suggested on "The most wanted feature?" topic on the forum) alongside the GPU rendering with all the scalability that GPU rendering allows would greatly improve Corona experience, in my opinion.

I know GPU rendering and viewport interactive rendering may be in the distant future (or never happening at all) but can we, as of right now, start the AI denoiser on the first sample in order to simulate default Cycles viewport rendering behavior?

Note: In the video, I'm using a GTX 1070 Ti which is very far from the latest and greatest but it is still a smooth experience.

[Max] Feature Requests / Re: Region improvements
« on: 2022-12-04, 12:30:14 »
Is this already implemented in v9, Marcin?

[Max] Feature Requests / Re: Clipping warning in VFB
« on: 2022-04-07, 17:43:52 »
Any idea when/if is this going to be implemented on VFB, guys? This would be REALLY useful!

The opinion I was trying to convey in my first post is that Corona UI is somewhat unrefined in some places. Can't understand those blue arrows and bad placing at the right on the image I sent above. Seems that Tone Mapping Settings Editor accessed via "Edit" on camera controls is a copy-paste of what we have in Corona VFB without removing the arrow left of Tone Mapping, which doesn't serve any purpose. I know it's a little thing but to me, it kills the usability and pleasure of working with the software.

Obviously, Corona has a lot to offer and it surely gained a lot of steam by joining Chaos, yet from my subjective point of view - of someone that abandoned Vray years ago - it looks like Vray is slowly copying coronas features yet Corona is not doing the same vice versa.

I have to agree with Mike here. I too abandoned Vray years ago. Chaos bought Render Legion out of fear. Enscape too. I really don't like this way of doing business because it hampers progress. Those were my fears when the news came out and, from my point of view, they're slowly becoming more evident judging from the pace of new features. Cannot say I'm surprised. Chaos trying to monopolize the 3d rendering industry is just sad, IMHO.

Corona is still the best renderer for what I use it for, though.


Then you would not be able to hide Tone Mapping, the arrows help you reduce the space taken on your screen by the menus. I think it's quite ok.

There is no need for the left arrow when you open Tone Mapping Settings Editor via "Edit" on camera controls. I see the need for it when you are on Corona VFB and when you have Bloom, Glare, Sharpening, and Denoising menus below it but not here.

Pages: [1] 2 3 ... 13