UI dilemma

[jujubee]

Global - simple is best to avoid additional confusion IMO.

[harperperkins]

The legacy option/system units checkboxes work fine where they are now, and the fact that you've got it working automatically is great, but I agree they'd be better served under the global rollout myself. I can't forsee a reason why I'd want it to be a per-light option except if I were testing between old and new sun/sky/cams like Lele says - and who's got time for that, anyways, except DaForce? hehe

[Robur]

Global for me too

[Dynedain]

I'm not going to pretend that I know exactly how this works, but I think it would make sense if there was a global checkbox in the VRay globals rollout that simply adjusted multipliers throughout.

This way values would still be displayed as they were on old scenes, but a global render-time setting would make the modifications at rendertime.

[dgsantana]

Global renderer option.

[apexmotion]

Global render option for me. Changing settings automatically when opening Vray legacy files with prompt.

[sv]

yeah, i think that if the only reason why this problem exists is so that files previously created using 1.48 > 1.5RC can be rendered in the same way using the newer builds, then just keep it simple, and have a 'legacy units' option in the Renderer. Perhaps this could also work in an automatic way, similar to the warning for the rQMC sampler stating the file was created with an older version, and have it automatically set itself to the 'legacy units' when appropriate.

Option 2 for me....

[dapeter]

What about doing it individually by light/object, then scripting some sort of Vray-aware light lister that would allow you to select all the lights and enable/disable the override? You could just add a warning when opening an old scene similar to the rQMC popup you get, that says, "Go to the VrayLightProperties viewer and adjust for light intensity compatibility" or something like that.

[studioDIM]

Just to clarify it: it DOES work automatically for scenes built with the older models for sun and sky and physcam.
Only it's on the sun, and on the physcam, rather than globally.
But it does get ticked automatically (and tickled a bit, too ).

Sure enough, unticking "legacy" on the sun, while leaving it ticked on the camera ISOs will produce an overblown render.
And the other way around holds true as well (sun as legacy, Physcam ISOs as new will underexpose).

As i said previously, it's really really minor once one creates new scenes, or simply loads old ones.

As a side note, the matrix exposimeter works just as good (or bad, make your pick) with new or old model, whatever the mix of "legacy" tickboxes.
VRay behaves very consistently and as expected regardless.

Lele

edit: and yeah, scripting something like this is dead easy (not a light lister, but a simpler change-them-all script.),