Default settings?

[superrune]

Hi,

I find myself always changing a few of the defaults in Brazil, such as Camera Space Shading, Float Output and the Clamp value. Is there a way to have them permanently changed, without doing it through a maxstart file?

[zemmuonne]

Rune, just out of curiosity: usually what AA/Clamp values combo you use?

[RichardAnnema]

There's no specific default settings file for Brazil; maxstart.max -would- typically be the place you set these things.

You could do something with scripting, a la:

callbacks.removescripts id:#brazil_defaults
callbacks.addScript #postRendererChange "
    if ((renderers.current.classID as string) == \"#(95494396, 474502030)\") do (
        if (getAppData trackviewnodes.brazil_r_s 399 != \"defaults set\") do (
            -- set defaults here
            -- example start
            if (queryBox \"Do you wish to apply custom default Brazil settings?\") do (
                local brz
                for i = 1 to 4 do (
                    brz = trackviewnodes.brazil_r_s[i]
                    local brz_is = brz.Sampling_Parameter_Block_Holder
                    brz_is.aa_min = 1
                    brz_is.aa_max = 2
                    brz_is.clamp = 1e6
                    brz_is.filter_name = \"BrAreaFilter\"
                    brz_is.filter_radius = 0.001
                )
                -- example end
            ) -- querybox
            setAppData trackviewnodes.brazil_r_s 399 \"defaults set\"
        ) -- check appdata
    ) -- check renderer classID
" id:#brazil_defaults

..sticking that into a maxscript file in your <max>\scripts\startup\ folder.
Unfortunately the #preRendererChange callback already shows the trackviewnode as existing, so preventing the defaults-setting on existing files (which won't have the appdata marker) would need some further pondering.

[superrune]

I was thinking that through the comprehensive Brazil preset system there would be some way of making defaults as well. A great feature would be a folder of XML-based presets that people could share between them, that would be a very nice alternative to the presets that V-Ray and MR already have in their renderers. I have some reservations against propping my 3ds Max full of callbacks, but thanks Richard, perhaps I should just go for that

zemmuonne:
I have a bunch of sampling and GI settings that I find myself returning to. My render samples usually stays at 1,2 but I sometimes boost that to 2,4 if I have some severe sampling issues (but then I tend to increase the contrast color). And I like to check the adaptive tests for Normal and Object Edge.

As for clamping, I like to have that somewhere around 10. I frequently render superbright values, so the default 1.0 value is a no-no for me. And of course, because of that I always have 32-bit float image output checked.

I also like to keep the KDA accelerator as the default, and there are plenty of GI values I keep returning to (a rate around 15, 3 bounces, and cache samples to -2,0). It's probably more than that, that's why I'd like a custom default preset so that I don't forget them

[RichardAnnema]

Originally Posted by superrune

I was thinking that through the comprehensive Brazil preset system there would be some way of making defaults as well.

'fraid not

Originally Posted by superrune

A great feature would be a folder of XML-based presets that people could share between them

There's a Bonus Tool that'll let you load/save preset files; preset files technically save all data (minus maxwrapper stuff), the preset loading lets you specify which sections to actually load (and of course manually removing bits from the preset file will prevent those from being loaded altogether). Nothing tightly integrated into the main Brazil UI, though - which tends to be the biggest stumbling block for most users.

Similarly - 3ds Max itself supports saving presets to an extent, but it doesn't play nice with brazil and, imho, is a bit limited anyway.

Originally Posted by superrune

I have some reservations against propping my 3ds Max full of callbacks, but thanks Richard, perhaps I should just go for that

It's just one - and a pretty low-impact one at that.. how often do you change renderers?
Although you'd want to put them on the 'new file' callbacks as well, I think, if you keep the renderer around in a session.

[superrune]

Thanks again Richard