Image Sequence F10/LWSN Crashes with Material Update

[3dreamstudios]

I use image sequences alot on screens for tv's and video screens etc. I check the Update Materials in the Editor but have Update Scene only not Full Scene Reload as main option. However it seems the scene closes at the end....reloads all objects and then begins to render again.

I use LWSN to render on single machine, because I can control many scenes in the que this way.

Version 2.x did not do this...I'm wondering if there is an issue with 3.x in this area or am I somehow missing something with the new setup, somewhere, Thanks!

[juanjgon]

Rendering with F9/F10/LWSN or in the IPR? I have seen this problem working with the IPR due to an issue in Layout, that fire a full scene reload event if you set the image sequence in any of the surface editor "T" texture layers, but it is weird that in update mode, rendering with F10 or LWSN, the plugin force a full reload the scene.

-Juanjo

[3dreamstudios]

Rendering with F9/F10/LWSN or in the IPR? I have seen this problem working with the IPR due to an issue in Layout, that fire a full scene reload event if you set the image sequence in any of the surface editor "T" texture layers, but it is weird that in update mode, rendering with F10 or LWSN, the plugin force a full reload the scene.

-Juanjo

Using LWSN to render. And it certainly seems a full scene reload is being called because it finishes rendering and then shuts down....reloads scene and continues. I may need to fall back to v2x for now As this is causing renders to be 2x longer with the loads...

Thanks for looking into it...

[3dreamstudios]

ah it may not be reloading, but CRASHING. See attached list of files it rendered. Hmm...switched back to 2.24 see how it goes...

[juanjgon]

If you have a scene that crashes the LWSN nodes, please let me know. Check if the scene can be rendered fine from the Layout, and try to get the LWSN log to see if we have a CUDA error.

-Juanjo

[3dreamstudios]

If you have a scene that crashes the LWSN nodes, please let me know. Check if the scene can be rendered fine from the Layout, and try to get the LWSN log to see if we have a CUDA error.

-Juanjo

Can you remind me how to do this for you? I would certainly be glad to provide any help that could direct your attention...

[juanjgon]

I suppose that you could redirect the LWSN command to a file ... something like 'lwsn > E:\log.txt'

-Juanjo

[3dreamstudios]

I know it doesn't help you right now...but I think it's something in the 3.00.6 version as compared to the 3.00.4 version. As I just loaded up the .4 version and all seems to be going just fine...without crashes.

If it keeps up I'll need to let it finish! Been fighting it all weekend...but if I can get you logs on the .6 reason I certainly will.

[3dreamstudios]

well it seems it doesn't crash...but the frames look quite a bit different. IES lights and quality are quite a bit different. will have to manage the crashes in .6 version for now...client has approved those images....

[3dreamstudios]

Here is the DUMP file from LWSN.exe when using 3.00.6 version.