Hey Matt,
Some code, essentially all I'm pulling is data that's already residing in
the PPG. What's failing is setting: bake.input_object.value = ob.FullName +
".SItoA.1000", but it logs back out just fine. However something is screwy
as this information is not getting pulled to the shader at rendertime -
works just fine in interactive...
PPG = get_object("RenderUtilities")
bake_active = PPG.bake_active.Value
if bake_active:
GridData = PPG.bake_data.Value
bake = get_object(PPG.bake_shader.value)
pss = app.GetCurrentPass()
index = None
for i in range(0, GridData.RowCount):
if GridData.GetCell("Pass",i) == pss.FullName:
index = i
break
if index != 0:
ob = get_object(GridData.GetCell("Object",index))
# set bake item to camera
bake.input_object_name = ob.FullName
bake.input_object.value = ob.FullName + ".SItoA.1000"
log(bake.input_object.value)
else:
bake_active = False
Cheers,
Jules
On Wed, Jun 11, 2014 at 7:43 PM, Matt Lind <[email protected]> wrote:
> Don’t do anything that interacts with a GUI. That’ll crash XSIBatch as
> XSIBatch is essentially XSI.exe without any GUI, or support for a GUI.
>
>
>
> How are you getting information from your custom properties? That might
> be a factor.
>
>
>
>
>
> Matt
>
>
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Jules Stevenson
> *Sent:* Wednesday, June 11, 2014 11:40 AM
> *To:* [email protected]
> *Subject:* Python: Limitations / Differences in xsibatch versus
> interactive
>
>
>
> Hey Gang,
>
>
>
> We have a few custom properties and events which refuse to behave
> themselves in batch, are there any common gotchas / workflows / things to
> avoid when using XSIbatch.
>
>
>
> Infuriatingly, all the logging I've been doing seems to suggest things are
> running just fine, but then the script still fails (specifically I'm
> pulling a value from a custom property and using this to change some
> parameters on a custom lens shader).
>
>
>
> Any thoughts / help much appreciated.
>
>
>
> Jules
>
