Chaos Corona for 3ds Max > [Max] Daily Builds

Corona 1.4 render setup UI overhaul

<< < (2/9) > >>

romullus:
Sorry Rawa, but i completely disagree with you, it WOULD make process faster and easier to use (click vs click-move-click) and it almost won't add any visual clutter as no controls have to be moved or crunched - there is plenty of space to add those checkboxes. Every (i mean EVERY) single time i use render selected feature, i wish that there would be that damn checkbox. As much as i like elegant and simple UI idea, i can't stand when usability has to be sacrificed for it.

Sorry for a rant, i just need to vent my frustration. If it's firmly decided that those checkboxes has no place in Corona's vision of UI, i won't bother you again about it.


--- Quote from: lacilaci on 2016-03-03, 08:00:44 ---Well if changing the setting can make a notable difference in performance, then yes... otherwise you can still experiment with it using string options right? "int adaptivity.adaptivityInterval = #"

--- End quote ---

Thanks for info!

Ludvik Koutny:
The thing is that there are more than one options. So while denoiser would be activated with a single click, firefly removal would then have to be click-click-move-click instead of click-move-click. And render selected has more modes as well, so as long as user does not want to use what's set there by default, it's actually one more click for him.

While i agree that every click or move should be shaved off if possible for tasks that are done often, enabling denoiser or render selected is probably not a task that is being done 10+ times a minute, so it's really not worth adding UI clutter.

Lastly, UI always needs to have clear and consistent guidelines. You can't use few different UI philosophies scattered across single piece of software, or you end up with something like 3ds Max itself. So if we followed a logic that any dropdown that has none option should have checkbox activator, then primary and secondary GI would have checkboxes to, so would image filter and VFB type. Now we would have 6 new UI elements that do not add any real speed or flexibility benefit.

Frood:

--- Quote from: romullus on 2016-03-03, 10:01:03 --- i can't stand when usability has to be sacrificed for it.

--- End quote ---

I think it´s only a different definition of "usability". I remember the UI switch from Alpha to v1.0: suddenly I needed twice the time to find the (few) settings, some of the Corona magic got somehow lost. And what about new users? One of the most appealing features of Corona was/is it´s simplicity. This is a bigger deal than one might think as someone who has been using Corona for a long time now.

Solution may be having a "Standard" and a "Advanced" GUI. Similar to checking "Development/Experimental Stuff" but with impact on all rollouts/settings. This way you (and me, because I also miss it) may get your checkbox in "Advanced" mode ;) or the adaptivityInterval (please do;) while new users have the simplified UI. Regarding that checkbox it does of course not make sense to change the basic handling but you get the idea.

I remember there has been a (way to) short note/discussion about standard/advanced UI somewhere in the forum.

Good Luck



Ludvik Koutny:
Well, actually if majority of people would be for to have checkboxes to activate dropdowns that have currently "none" or "disabled" option, it would be reasonable to do it, but it would have to be done everywhere, so UI is consistent across all corona windows and panels. This is not nVidia forum where you get banned for feedback, here, everything is always open for discussion. In the end, it's the userbase who use the renderer on daily basis :)

Juraj:
Standard/Advanced version of GUI is rabit hole. It creates the effect that even the most clueless beginners feel like they're missing out on "better controls".

Just look at the amount of people still asking for "best settings" on forum :- ). Advanced division would simply amplify this effect, Advanced would become de-facto the new default anyway.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version