Scene crashing on the farm - renders in the UI

[Morten Bartholdy]

Hi all,

I have a scene which has rendered fine until now, but after some modeling and shader changes in a referenced model (performed on the master and referenced in) it crashes on the farm (RoyalRender) but renders fine in the UI RenderRegion.

I made some shader and scale changes to assets in a referenced model after which this occurs, but I am not sure how that could be the problem. I am not sure what to make of the bug info - any ideas?

I actually see a number of messages pertaining to a large number of deltas not being applied to objects in a referenced model, like this:

R144| ' WARNING : 3000 - Cannot apply Delta Road, because the target model Landscape_01.Delta2 is invalid.

After these messages I see this:

R318| * CRASHED in C3DStaticCompArray::Set at 00:00:00
R319| * signal caught: error C0000005 -- access violation

- later again:

R417| >"C:\Program Files (x86)\rrService\lc64\rrCheckexitcode.exe" -1073741819 0 0 12
R418| +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
R419| +++++++++++++++++++++++++++03.01. 17:51.01 Render Executable done +++++++++++++++++++++++++++++++++++
R420| ++++++++++++++++++++ Royal Render checks the return code of the executable ++++++++++++++++++++
R421| ++++ Executable returned -1073741819 (0x c0000005) as exit code for frame 12.
R422| Error: Renderer or plugin contains a bug. Crash was caused by a NULL pointer memory access.
R423| ++++ Executable crashed

- and:

C 0| ************************* CLIENT REPORTS DURING THIS RENDER *************************
C 1|
C 2| Error in this log file (213): ' error : 2356 - this plug-in is not installed: redshift options
C 3| Error in this log file (394): * signal caught: error c0000005 -- access violation
C 4| Error in this log file (497): error: renderer or plugin contains a bug. crash was caused by a null pointer memory access.
C 5|
C 6| Job crashed
C 7|
C 8|


It doesn't ring any bells with me except for the delta/ref model messages, and the only way I know to fix that is delete the offending refmodel and reload it in the scene, which I would prefer to avoid.

Given that the crashing is caused by the delta trouble, does someone here have any ideas regarding how to clean/fix the refmodel delta's or is the only way to delete and load it again and redo all partitioning?


Thanks
Morten
------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Orlando Esponda]

Try to get rid of the Redshift options. It's been a while since I used Royal Render but I remember it stops the render if it finds any kind of error in the scene. Deleting renderer options is not that easy to do manually, I recommend doing it via script.

try this:

from win32com.client import constants as c

si = Application

log = si.LogMessage

RENDERER_NAME = "Redshift Options"

renderOptionsList = []

for cstmProp in si.FindObjects("", "{76332571-D242-11d0-B69C-00AA003B3EA6}"):

    if RENDERER_NAME in cstmProp.Name:

        log(cstmProp.FullName)

        renderOptionsList. append(cstmProp)

for renderer in renderOptionsList:

    si.DeleteObj(renderer)

To unsubscribe, send a mail to softimage-request@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Morten Bartholdy]

I have Redshift on my workstation but not on the farm, and it has never caused problems when rendering on the farm. I guess I can't remove Redshift options when I have it installed without screwing something up.

I am pretty sure this is scene content related - referenced models with loads of standins being loaded at rendertime.

MB

> > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >

> ------
> Softimage Mailing List.
> To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Morten Bartholdy]

I am troubleshooting a scene which repeatedely crashes when rendering on the farm (RR) or using xsibatch, but renders fine in the UI Renderregion.

I get these error messages:

---------------------------------------------------------------------------------------------------------
R160| >"C:\Program Files (x86)\rrService\lc64\rrCheckexitcode.exe" -1073741819 0 0 6
R161| +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
R162| +++++++++++++++++++++++++++03.03. 15:41.43 Render Executable done +++++++++++++++++++++++++++++++++++
R163| ++++++++++++++++++++ Royal Render checks the return code of the executable ++++++++++++++++++++
R164| ++++ Executable returned -1073741819 (0x c0000005) as exit code for frame 6.
R165| Error: Renderer or plugin contains a bug. Crash was caused by a NULL pointer memory access.
R166| ++++ Executable crashed

C 0| ************************* CLIENT REPORTS DURING THIS RENDER *************************

C 3| Error in this log file (240): error: renderer or plugin contains a bug. crash was caused by a null pointer memory access.
C 4|
C 5| Job crashed
---------------------------------------------------------------------------------------------------------


I suspected a hickup with a large referenced model and deltas, so I deleted this and reimported and partitioned elements in it again, but the scene still crashes.

Does anyone here know what these errors mean and what might cause them so I know what to look for for a fix?

Thanks

Morten

> Den 2. marts 2017 klokken 10:22 skrev Orlando Esponda <orlando...@gmail.com>:
>
>

> > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >

> ------
> Softimage Mailing List.
> To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Sven Constable]

I cannot comment on the specific error code, other than it looks similar to
most errors I got when a job crashed ( even when a crash was not directly
related to the render engine).
Does it also crash, when rendered locally via xsibatch on the workstation?
That would at least out rule the farm and RR...

Which renderer ar you using btw? Are there any debug modes like mental ray
has? Maybe this will give a hint too.

Sven

[Morten Bartholdy]

Yes, xsibatch crashes too, so likely not a RR problem. I am using Sitoa Arnold, and Stefano says the errors are not Arnold related.

Cheers
Morten

[Sven Constable]

Are they any warning messages in the script editor, when loading the scene?
I would also check the debug log from Arnold when rendering from inside the
GUI.
Maybe test render with mental ray, overriding the arnold shaders in a new
pass and see if it works. Just to out rule the renderer for sure.

Does it render when you convert the ref models to local? Just for testing
purposes, of course.

> R162| +++++++++++++++++++++++++++done

> +++++++++++++++++++++++++++++++++++
> R163| ++++++++++++++++++++ Royal Render checks the return code of the
> executable ++++++++++++++++++++
> R164| ++++ Executable returned -1073741819 (0x c0000005) as exit code

> R164| ++++ for

> frame 6.
> R165| Error: Renderer or plugin contains a bug. Crash was caused by a

> R165| NULL

> > > R144| target

> model
> > > Landscape_01.Delta2 is invalid.
> > >
> > > After these messages I see this:
> > >
> > > R318| * CRASHED in C3DStaticCompArray::Set at 00:00:00
> > > R319| * signal caught: error C0000005 -- access violation
> > >
> > > - later again:
> > >
> > > R417| >"C:\Program Files (x86)\rrService\lc64\rrCheckexitcode.exe"
> > > -1073741819 0 0 12
> > > R418| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > +++++++++++++++++++++++++++++++++++
> > > R419| +++++++++++++++++++++++++++03.01. 17:51.01 Render Executable

> > > R419| +++++++++++++++++++++++++++done

> > > +++++++++++++++++++++++++++++++++++
> > > R420| ++++++++++++++++++++ Royal Render checks the return code of

> > > R420| ++++++++++++++++++++ the

> > > executable ++++++++++++++++++++
> > > R421| ++++ Executable returned -1073741819 (0x c0000005) as exit

> > > R421| ++++ code

> for
> > > frame 12.
> > > R422| Error: Renderer or plugin contains a bug. Crash was caused

> > > R422| by a

[Morten Bartholdy]

No warnings I wouldn't expect, no. I am using some tile textures which throw warnings, but thats it.
Arnold is not complaining in the UI. The MR approach I can do, but there are many Arnold standins, so perhaps not a valid test.

I have not yet tried making refs local, but will give it a go.

MB

[Morten Bartholdy]

I am bumping this one in the hope someone can share some insight on what to look for.

I have almost rebuilt the scene, ie. removing all referenced items and reimported them and redone all partitioning in various passes, but it still crashes on the farm and with xsibatch on a workstation, while rendering in the UI render region.

Some additional info:

Softimage crashes if I try merging the scene in to an empty scene.

I can render the various assets being referenced in from their master scenes.

I get two different error messages when crashing for different passes, ie. the product and the env:

Product pass (env primary rays off):
--------

R163| ++++++++++++++++++++ Royal Render checks the return code of the executable ++++++++++++++++++++

R164| ++++ Executable returned -1073741819 (0x c0000005) as exit code for frame 8.

R165| Error: Renderer or plugin contains a bug. Crash was caused by a NULL pointer memory access.
R166| ++++ Executable crashed

env pass (product primary rays off):
----
R161| +++++++++++++++++++++++++++03.04. 13:52.10 Render Executable done +++++++++++++++++++++++++++++++++++
R162| ++++++++++++++++++++ Royal Render checks the return code of the executable ++++++++++++++++++++
R163| ++++ Executable returned -1073740940 (0x c0000374) as exit code for frame 0.
R164| ++++ 'A heap has been corrupted.'
R165| ++++ Executable crashed

Does someone know what these might mean:

1. Crash was caused by a NULL pointer memory access.

2. 'A heap has been corrupted.'

I have never seen them before, and if I had an inkling of an idea what might cause them it might be easier to pinpoint the cause of the crash.

I would have liked to avoid rebuilding the scene from scratch redoing passes and overrrides, but since the assets individually seem fine, but the scene doesn't render the problem might lie somewhere in ref model deltas or overrrides in passes.

Thanks.

[Schoenberger]

|> 1. Crash was caused by a NULL pointer memory access.
|> 2. 'A heap has been corrupted.'

I am sorry, but it won't probably help you to know.
They have a bug in the software accessing the memory.
1. They have assigned a random memory segment for a variable, but the application did never tell Windows to assign a part of the
memory.
2. Different kind of memory.

>but the scene doesn't render the problem might lie somewhere in ref model deltas or overrrides in passes.

Delete as many other passes as you can, try to delete deltas, delete overrrides, delete ref models.
This way you can find out which combination of ref model/delta/pass overrides is responsible.


Holger Schönberger
technical director
The day has 24 hours, if that does not suffice, I will take the night

[Morten Bartholdy]

Thanks Holger,

So what you are saying that some combination of content, overrrides and delta data is throwing Arnold off, or XSI off?

I made referenced models local but it still crashes.

I think I have narrowed the problem down to a particular version of my environment by using a backup of an older version which renders fine.

Weird thing is my new environment renders fine in its own scene, but not in the production scene with passes and overrides.

Tough one, but thanks for the insight.

Cheers
Morten

[Schoenberger]

|> overrrides and delta data is throwing Arnold off, or XSI off?

"Cannot apply Delta Road"
"CRASHED in C3DStaticCompArray"

Both do not look like Arnold error messages.
Arnold does not know anything about deltas. It just asks Soft for the final geo.

Holger Schönberger
technical director
The day has 24 hours, if that does not suffice, I will take the night

|> -----Original Message-----
|> From: softimag...@listproc.autodesk.com
|> [mailto:softimag...@listproc.autodesk.com] On Behalf
|> Of Morten Bartholdy
|> Sent: Monday, March 06, 2017 11:54 AM
|> To: Official Softimage Users Mailing
|> List.https://groups.google.com/forum/#!forum/xsi_list
|> Subject: RE: Need help - Scene crashing on the farm -
|> renders in the UI
|>

[Morten Bartholdy]

I have done meticulous step by step troubleshooting going through each ref model, eliminating ref model and delta issues and it comes down to a particular ref model making the scene crash on the farm. This model renders fine from its master scene, so I am guessing some combination of the content - large displacements and large numbers of ICE scattered standins with high polycount, combined with passes, partitions and overrides make it crash, ie. a problem in the scene.

I eventually rebuilt the scene so content and passes are as clean as possible, and this scene crashes too.

Incidently if I have done a renderregion and save after that, it will save the scene, but Softimage will hang, requiring me to kill it. I am on 2015 R2 for various reasons - I recall 2015 R2SP2 has a considerable number of bugfixes. Could it perhaps be that R2 has a sort of memoryleak?

MB

[Oscar Juarez]

Maybe for the sake of decoupling softimage completely but depending what you are rendering (static or moving), you could try to convert this whole model to an ass file and render that instead of the model itself.

> ------
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-request@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-request@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Matt Lind]

If the scene is only crashing during render from XSIBatch, then you need to
start checking for tools/properties that invoke any kind of a graphics call.
XSIBatch does not support anything that invokes drawing of graphics or
anything that calls such an API to do work. That'll induce a crash.

2015 does fix bugs, but it also has a good number of regressions. Which
version is best is specified to your needs, but I think 2014 SP2 is a better
bet in the stability department.

Matt




Date: Tue, 7 Mar 2017 15:58:32 +0100 (CET)
From: Morten Bartholdy <x...@colorshopvfx.dk>

Subject: RE: Need help - Scene crashing on the farm - renders in the
UI

To: "Official Softimage Users Mailing List.

I have done meticulous step by step troubleshooting going through each ref
model, eliminating ref model and delta issues and it comes down to a
particular ref model making the scene crash on the farm. This model renders
fine from its master scene, so I am guessing some combination of the
content - large displacements and large numbers of ICE scattered standins
with high polycount, combined with passes, partitions and overrides make it
crash, ie. a problem in the scene.

I eventually rebuilt the scene so content and passes are as clean as
possible, and this scene crashes too.

Incidently if I have done a renderregion and save after that, it will save
the scene, but Softimage will hang, requiring me to kill it. I am on 2015 R2
for various reasons - I recall 2015 R2SP2 has a considerable number of
bugfixes. Could it perhaps be that R2 has a sort of memoryleak?

MB

------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Morten Bartholdy]

That is actually a good idea. Do you know if I can have .ass files nested in an .ass file, ie. ICE scattered standins inside the model .ass?

MB

> > > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> > ------
> > Softimage Mailing List.

> > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> ------
> Softimage Mailing List.

> To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Oscar Juarez]

Nested procedurals, last time I tried it was supported.

> > > To unsubscribe, send a mail to softimage-request@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> > ------
> > Softimage Mailing List.

> > To unsubscribe, send a mail to softimage-request@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> ------
> Softimage Mailing List.

> To unsubscribe, send a mail to softimage-request@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-request@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Morten Bartholdy]

Cool, thanks.

MB

> > > > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > > > with "unsubscribe" in the subject, and reply to confirm.
> > > >
> > > ------
> > > Softimage Mailing List.

> > > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> > ------
> > Softimage Mailing List.

> > To unsubscribe, send a mail to softimag...@listproc.autodesk.com

> > with "unsubscribe" in the subject, and reply to confirm.
> >
> ------
> Softimage Mailing List.

> To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

------
Softimage Mailing List.
To unsubscribe, send a mail to softimag...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.

[Morten Bartholdy]

The delta stuff was from earlier. I made all referenced models local and it still crashed - now I have rebuilt every assets and the scene inluding all passes, overrrides etc. and it still crashes, now wothout delta errors.

I am now trying to find out if it is xsbatch, Arnold (Sitoa) or windows that is acting up, and more importantly what in my scene is causing it.

MB

> Den 7. marts 2017 klokken 11:11 skrev Schoenberger <X...@digidragon.de>:
>
>
>

[Schoenberger]

If it does not crash within the UI, then exporting .ass from the UI seems to be a solution.
Either only that one ref model or the whole scene.
(If nested .ass files work, but as rendering is creating some kind of .ass file in memory, and you can use standins, it should work)


Last option: I have never tried it, but perhaps it is possible to batch render with the XSI UI over the farm.
Two prequesites:
1) To test if the scene does not crash, you could reduce the resolution and samples to a minimum
And execute this vbs line in XSI:
renderpass passName , , frstart,frend,frstep
2) Check if you can start and control the XSI UI via a script.

Holger Schönberger
technical director
The day has 24 hours, if that does not suffice, I will take the night



|> -----Original Message-----
|> From: softimag...@listproc.autodesk.com
|> [mailto:softimag...@listproc.autodesk.com] On Behalf
|> Of Morten Bartholdy
|> Sent: Tuesday, March 07, 2017 4:59 PM
|> To: Official Softimage Users Mailing
|> List.https://groups.google.com/forum/#!forum/xsi_list
|> Subject: Re: Need help - Scene crashing on the farm -
|> renders in the UI
|>

[Morten Bartholdy]

Hi Holger,

I am actually about to try rendering with Kick on RoyalRender as standalone kick renders the scene fine, which possibly points to an xsibatch problem.

Can you tell me where RR stores the .ass files if I use the RR Ass_create_n_Render?
They are kind of big (about 2GB per frame) so I would like to keep tabs on them so I can clean up.

MB

[Morten Bartholdy]

Thanks for the insight Matt. There is a problem of sorts in the scene which xsi does not like. I can't think of anything making graphics calls, but then again I don't know what they might be. I am rendering with Sitoa so lots of Arnold specific stuff, loads of standins and a lot of big displacement combined with a sort of large scene extent, around 40.000 units across.

I can render a region in the UI but if I save the scene after that, XSI saves the scene but hangs. In one attempt to fix the scene I tried merging the scene into an empty scene - XSI crashes. Rendering with RoyalRender xsibatch after rebuilding the scene I find that it renders a few frames randomly but still crashes with the same error messages.
I have tried hiding suspected offenders one at a time and it still crashes. I need to check some more items here as there are many.

Arnold standalone kick renders it fine, and so far creating .ass files and rendering i RoyalRender seems to work too. All this points to xsi/xsibatch having a problem with this particular scene and combination of objects, passes and overrides, but the maddening thing is I still don't have a clue what causes it. Unfortunately AD has made sure I can't get support help.

It would be great if upgrading to 2015 SP2 would fix it but I have no way of knowing without trying it, which is not straightforward due to a Maya/RR issue.

Soldiering on
MB

[Matt Lind]

Edit: I meant anything that makes a call to the UI.

You want to inspect the scene for anything that can cause the UI to be
updated such as a PPG being displayed, a layout menu being hidden/unhidden,
something that invokes the UI to refresh, etc... For example, do you have
a script which runs automatically whenever you change render passes or
selection? How about OpenGL display such as frame stamps? An embedded
viewport in a custom layout which updates when selection changes?

Since you mentioned you're using SItoA, make sure you're on a version of
Softimage that doesn't have SItoA issues. if using 2014, make sure you're
using 2014 SP2 as the main release and SP1 had a fatal issue specifically
with Arnold.

Even if you don't render your images with mental ray, consider using it as a
debugging tool by activating the basic and detailed debug settings in your
render options. The idea being that it's a quick way to cut the size of the
problem in half as XSI is really 2 programs in 1. The interface and data is
XSI, but the rendering is all mental ray. Translation has to occur to go
from one to the other. If you can get mental ray to spit out errors, then
it indicates it's a data problem. If mental ray gives clean bill of health,
but you still crash, then it's squarely an XSI application or user interface
error. Warning: the output will be enormous, but if there's a problem
mental ray will provide better details about it than straight XSI will.

I would advise making sure you're in the default XSI layout with no
customizations, then send that off to xsibatch.

Also, edit the following user preferences:
- deactivate: General > Launch Netview on Startup
- activate: Scripting > Log size = unlimited
- activate: Scripting > Log commands
- activate: Scripting > Log Messages
- activate: Scripting > Log Verbose Messages
- activate: Scripting > Real-time Message logging
- activate: Scripting > Log to File (and specify a file)
- activate: Scripting > Log File (defaults to <username>.log in your XSI
user folder)

These won't log everything, but if it's XSI specific, you'll at least get a
rough idea of where the problem may be located. Render using xsibatch and
see where it leads.

If the above doesn't solve the problem, try these preferences:
- activate: Data Management > Disable all geometry operators on load
- activate: Data Management > Skip loading of floating objects
- activate: Data Management > Disable cycle checking when applying
animation operators
- activate: Data Management > Disable cycle checking when editing ICE
Trees
- activate: Data Management > Kills all notifs during load
- activate: Data Management > Records user and time information in
deltas

If activating all these settings causes the scene to successfully render in
xsibatch, then back up a few steps and deactivate them one at a time between
renders until the problem resurfaces. You're mostly likely to see changes
with the disable geometry operators on load, and skip loading of floating
objects settings. Especially the latter considering you've already reported
such messages (as a result of merging scenes - don't do that).


Matt




Date: Wed, 8 Mar 2017 14:26:19 +0100 (CET)

From: Morten Bartholdy <x...@colorshopvfx.dk>
Subject: RE: Need help - Scene crashing on the farm - renders in the UI
To: "Official Softimage Users Mailing List.

Thanks for the insight Matt. There is a problem of sorts in the scene which
xsi does not like. I can't think of anything making graphics calls, but then
again I don't know what they might be. I am rendering with Sitoa so lots of
Arnold specific stuff, loads of standins and a lot of big displacement
combined with a sort of large scene extent, around 40.000 units across.

I can render a region in the UI but if I save the scene after that, XSI
saves the scene but hangs. In one attempt to fix the scene I tried merging
the scene into an empty scene - XSI crashes. Rendering with RoyalRender
xsibatch after rebuilding the scene I find that it renders a few frames
randomly but still crashes with the same error messages.
I have tried hiding suspected offenders one at a time and it still crashes.
I need to check some more items here as there are many.

Arnold standalone kick renders it fine, and so far creating .ass files and
rendering i RoyalRender seems to work too. All this points to xsi/xsibatch
having a problem with this particular scene and combination of objects,
passes and overrides, but the maddening thing is I still don't have a clue
what causes it. Unfortunately AD has made sure I can't get support help.

It would be great if upgrading to 2015 SP2 would fix it but I have no way of
knowing without trying it, which is not straightforward due to a Maya/RR
issue.

Soldiering on
MB

[Sven Constable]

Hey Matt, I would to chime in with a side question. You mentioned a few
things regarding user prefs. Is xsibatch using the user preferences to some
extend? He was able to render the passes from inside XSI but xsibatch
crashed on the local workstation and the farm. This is what puzzles me.

Sven

[Matt Lind]

As stated earlier, if something in the scene causes a UI refresh or update,
that'll work just fine in xsi, but fail in xsibatch. User preferences can
have an effect on UI interaction and behavior. for example, displaying a
PPG on node creation. That is a preference setting which affects UI.

User preferences tell xsi how to behave when certain events occur. So yes,
user preferences most definitely apply in xsibatch.

Matt




Date: Wed, 8 Mar 2017 23:30:36 +0100
From: "Sven Constable" <sixsi...@imagefront.de>

Subject: RE: Need help - Scene crashing on the farm - renders in the UI
To: "'Official Softimage Users Mailing List.

Hey Matt, I would to chime in with a side question. You mentioned a few
things regarding user prefs. Is xsibatch using the user preferences to some
extend? He was able to render the passes from inside XSI but xsibatch
crashed on the local workstation and the farm. This is what puzzles me.

Sven