Even though cameras have the option to control all the postprocessing, it’d be nice to have a bar with buttons where you can load different conf files directly from the VFB.
This would allow you to use different settings for GROUPS of cameras.
Sorry, but I didn’t fully understand this. What is the final outcome of your idea? The possibility to “push” post settings from the VFB to the selected camera? (or multiple cameras)
It would be like presets. Each preset opens a custom CONF file.
The final outcome is to be able to go from one preset to another directly in the VFB without having to click on load and search for it in the directory tree.
Hi, why are you suggesting to add these settings to the VFB? If I understand the original suggestion, you’d like to have some settings shared by multiple cameras. Wouldn’t it be better to introduce some kind of “take settings from another camera” option, similar to what we have implemented for the ColorCorrect texture? That way you would not have to switch the postprocessing settings in VFB at all whenever you switch the cameras.
Hi.
That would work.
In my current workflow I use only the VFB for tone mapping, exposure and post processing.
I think it’s because the camera settings are not as responsive during interactive rendering.
I could change my workflow if you’re adding the possibility to copy those settings while not changing other settings in the camera.
However, the VFB is much cleaner than the command panel, which makes it nicer to work with. The camera has so many settings that it’s just not comfortable.
The other difference between what you’re proposing and the presets in the VFB that I was suggesting is that the presets can let you compare settings very easily, while loading settings from a camera would require a dialog box or drop down list.
If this gets implemented at some point, which would be beneficial for sure, each preset could be stored with the max file instead of external saves maybe.
Would be awesome if the load button could load the conf settings of a *.max file. Rather than having to open the max file just to save out the conf file. But I don’t know if this is possible.
This is already possible. Ive done it with other data in C# outside of max but with C++ you could do it within the max environment.
You can do it with pretty much any information you might need and have it be readable without having to open the file too. Camera settings, VFB Settings, pretty much anything you can express in under 255 characters. I use it for adding metadata for other software to max files.
Happy to show the devs if theyre interested. I have something i can put on github.