Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Feature Requests => Topic started by: atelieryork on 2015-11-06, 11:07:49
-
Not sure if this is possible, but I hope so...
Could we please get CoronaCameraMod controls for specifying max render passes/max time and perhaps other features like displacement override, MB override etc.?
Edit: forgot to mention - the other super important one would be the GI v AA balance value, per cameramod. Could be very useful!
This would be enormously useful when you have multiple cameras per max file and need different passes for some, some shots might not need displacement while some do etc. This would do away with needing to split out into loads of max files as separate shots. Scene States are horrible and unreliable to use.
-
Another thing that would be really nice to have per camera is render output size (and thereby ratio). This way it would be possible to render i.e. both 360 pano cams and "normal" cams without constantly manually change output settings :)
-
I don´t think it´s a good idea to put everything in CameraMod though at the moment it seems the only reasonable location.
Since max exists I would like to have the render settings (even those in the Common tab) to be just keyable. But I don´t know if it´s even possibe to implement. It would be another approach to handle different settings in that (very common) scenario you described. In your case you would join the cams into a single one and simply animate settings along timeline.
Scene States are horrible and unreliable to use.
Exactly.
Good Luck
-
I would like to have the render settings (even those in the Common tab) to be just keyable.
I already had it implemented, but it caused some trouble so I had to disable it. I will revisit it at some point
-
Even though being extremly curious I will not ask which trouble but instead hope...
I will revisit it at some point
... this will come true. It would provide a completely different (and simpler) approach for many situations indeed.
Good Luck!
-
Key-able render settings would give some possibilities, but would not always be use-able (i.e. when working with animated objects). Another way to do it, could be to make an optional render preset selection in the Camera mod.
-
some great suggestions Alex!
-
+1!
but it will looks messy if I see complete render setup in coronacammod. but i remember that i have a scene that has indoor view, outdoor view , different ratio&resolution per view, motionblur, different GIvsAA. then, if it is implemented i will never experience tired of making render presets, and furstated if i make a mistake by load the wrong renderpresets on a cam view.
i believe everyone really need it.
-
I did a very quick and crappy mock-up of what this could maybe look like:
(http://i.imgur.com/MjmMyR0.jpg)
"Overrides" should probably be renamed "Render Settings Overrides" or similar.
The wording and ordering is not good, but the idea is there. The mod is basically already there purely for overrides to your main render setup settings, so I don't see any reason why it can't contain more overrides than it already has (for cleanliness reasons I mean).
It could be separated into sections:
Section 1 - Lens-based Overrides (e.g. the top stuff like iso, SS, aperture etc.)
Section 2 - Exposure & Toning Overrides
Section 3 - Render overrides (e.g. dof/mb/passes/msi etc.).
Section 4 - Projection Type
-
nice suggestion atelieryork, but maybe to keep the simplicity of modifiers dev.team can add an option "associated and load renderpreset/rendersetting" on coronacammod, and on the render setup there is an option "save preset/setting to coronacammod". hope this will help.
-
Yes, nice suggestion.
But.... seeing this I couldn't stop thinking about a "cleaner" way to do it, without having the whole render setting panel duplicated several times in different locations.
Why not simply use the panel that's already there (in the renderer) and then just select what camera/s to affect with which settings/set up. A sort of internal Corona presets. Since all adjustment goes on in the renderer, this would possibly also make realtime adjustment possible.
I know it's a totally different approach, and I don't know if it's possible to do. But in my head it would be much more logical and "clean".
-
Yes, nice suggestion.
But.... seeing this I couldn't stop thinking about a "cleaner" way to do it, without having the whole render setting panel duplicated several times in different locations.
Why not simply use the panel that's already there (in the renderer) and then just select what camera/s to affect with which settings/set up. A sort of internal Corona presets. Since all adjustment goes on in the renderer, this would possibly also make realtime adjustment possible.
I know it's a totally different approach, and I don't know if it's possible to do. But in my head it would be much more logical and "clean".
This is interesting but it means that you couldn't merge cameras between scenes without losing the override settings. The elegance of having all of this per-camera is that you can do just that. This would open things up nicely, and would also minimise the risk of incorrect render settings for particular shots.
I also disagree that these settings are duplicates across the UI. These settings are only really accessible currently in the render settings dialog. I think they should be enabled as overrides in the cameramod and then kept in the render settings but only take affect if no cameramod is being used, as is currently the case. Currently, if you have no cameramod then it takes the exposure settings etc. from your RS dialog. If you do have a cameramod then that takes over. It's quite a nice, clean solution already in place that could just be expanded upon, IMO.
I like Noel's idea of having presets as well, why not.
-
Hi atelieyork. I can see that I didn't explaine it vell enough, and unfortunately I haven't got the time to do it right now. But one thing: You should always be able to transfer render override settings via saved presets.
BTW - No matter how its done, it'll still be nice to have this functionallity.
-
I like PROH idea about render settings presets with include/exclude cameras list. To cram everything in camMod - no, please NO!
-
I like PROH idea about render settings presets with include/exclude cameras list. To cram everything in camMod - no, please NO!
Big agree, i'm with romullus and PROH ;)
-
I also agree with romullus, it´s a CameraMod, not a RenderSettingMod but as I posted earlier, it seems a good location to handle scene settings at the first glance.
So another idea would be to have a CameraMod (as it is now, including "Shape" option as the last one missing so that a proper DOF on/off and not "override" can be implemented but that´s another story) AND a "CoronaSceneMod" with all the stuff about Render settings as shown in the mockup (and maybe more). This looks more flexible and easier to handle for me and blends away a lot of UI confusion for users who only want to override basic camera settings.
As for the idea to link (Max) Render Presets:
- I hate them and find them cumbersome :]
- Render Presets are another file(!) in the first place somewhere on some harddisk. I expect issues when it comes to networked rendering, scene exchange and so on, but maybe there is a simple solution for that
Good Luck!
-
Yes, max's renderpresets are external files. That's why I wrote: "A sort of internal Corona presets." - Hoping that Corona could handle it internal in a smarter way than Max does :)