Notifications
Clear all
[Closed] batchRenderViewOps bugs
Feb 20, 2008 4:12 pm
I’m writing a script based off the Batch Render tool (batchRenderMgr interface in mxs) and can’t get two pretty essential things to work;
Both the .enabled and .sceneStateName properties of the batchRenderViewOps interface are supposed to be read/write, but setting these properties doesn’t seem to do anything.
-- get the first "view"
v = batchRenderMgr.GetView 1
-- [b]get[/b] the .enabled and .sceneStateName properties
print v.enabled
true
print v.sceneStateName
"TestState"
-- [b]set[/b] the .enabled and .sceneStateName properties
v.enabled = false
v.sceneStateName = "AnotherTestState"
-- .enabled and .sceneStateName properties haven't changed..
print v.enabled
true
print v.sceneStateName
"TestState"
Can anyone confirm this?
Thanks,
Martijn
3 Replies
Feb 20, 2008 4:12 pm
Martijn,
Yes, these are known issues. Hang on until the next release of Max, maybe they’ll be fixed?
Feb 20, 2008 4:12 pm
Thanks. I should have searched the forum before asking, just found a thread from someone asking the same question back in 2006…
[Edit] Just noticed that setting the .sceneStateName property actually changes the .presetFile property … [/Edit]
Cheers,
Martijn