Well presuming it’s encrypted and never gets decrypted (and then the string removed) and re-encrypted, that would work fairly well. Keep in mind, tho…

it’s 5.10am and I wasn’t going to peek back in ’til the weekend, buuuuuuuut… Can everybody get back on-topic? The thread is clearly spinning into a …

how are you using that script in a network render? the script seems to call render() itself and takes the requested channels as the argument for that…

you could script something up that would apply the effect to all materials; can’t be good for calculation times, though as far as the g-buffers go… …

you’d have to use layers with the g-buffer approach, though, as otherwise you’d only be fading the nearest surface to, say, black… rather than what’s …

yes, use ‘System.Windows.Forms.Combobox’; rollout roll_test “test” width:400 height:200 ( dotNetControl dno_ddl_test “System.Windows.Forms.Combobox…

go fig… I guess they decided to implement that stuff a bit non-standardly. The node itself, in Max, is just a Dummy Node. They store the parameters……

try ‘showInterfaces <node>’ or ‘showInterface <node>’ instead. Specifically, you might try… <node>.GetLodDistance() The documen…

You could make a .MZP file that would extract (and run) all the appropriate .ms and .mcr files before your user loads the toolbar file (can’t load/dis…

no idea… I’m guessing ‘no’; our renderer uses its own VFB, but that’s all handled from within the renderer plugin, and no arbitrarily for any renderer…

can’t replace the VFB entirely – closest thing to it is popping up your own window after rendering has completed (using e.g. a #postRenderFrame callba…

I’m guessing “no”; the VFB is basically a view of a framebuffer, and if you need a different resolution, a differently sized buffer has to be allocate…

if you keep the bitmap in the same variable, you can call display() on that variable to update the existing display without opening a new window. a …

to start, you should probably grab data on which faces are connected to which other faces, get the faces’ normal data, and use that normal data to see…

Diff.coords.blur = 0.0 (defaults to 1.0, I think) — Diff.coords.Blur_Offset = 0.0 (should default to 0.0 already) Similar for ‘Opa’