LW 9.3 new Photoreal Motion BLur is incompatible with Deadline

Deadline
1

Hey guys,

been toying with the Deadline demo (incredible piece of software really, much more streamlined than say Muster), i have however run into what i think is a bug.



When you use LW 9.3 and use one of the new camera types (say, Real Lens or Perspective Camera) and activate Photoreal motionblur__ with more than 5 motion blur passes (say 50), Deadline will throw an error and refuse to render.

Funny thing is, it is somethign with Deadline, as the same scene will render with no problems using either a command line LWSN render batch or a Muster dispatch render.



This problem has been mentioned by more than one person on the Newtek forums aswell.

2

I second this, tried it with a few scenes. Also have tried it with Lightwaves screamer net and TequilaScream and it works fine.

Can post the error message on monday when back at work if needed.

3

Hi guys,



Try submitting two separate jobs. One with the “Use ScreamerNet

Rendering” box checked, and one with it unchecked. Does either job

render? If either job generates errors, can you send us an error report

for each job? These can be obtained by right-clicking on the job and

selecting Job Reports -> View Errors.



Thanks!

4

Hello Ryan,



Right now i’m having trouble getting Deadline to run, i think either my

license expired or i have deleted something i wasn’t supposed to delete.

Also, i’m downloading the latest Deadline right now 2.7.29178 and trying

that one.



As soon as i get it running again i’ll try the 2 renders.



with kind regards,

Sven



–



House of Secrets

Mediapark - Mediacentrum | Sumatralaan 45 | 1217GP Hilversum | The

Netherlands

+31 (0)35 6409709 | +31 (0)6 25128136 | http://www.houseofsecrets.nl







Frantic_Deadline Listmanager wrote:

From: “Ryan Russell” (rrussell@franticfilms.com

mailto:rrussell@franticfilms.com)



Hi guys,



Try submitting two separate jobs. One with the “Use ScreamerNet

Rendering” box checked, and one with it unchecked. Does either job

render? If either job generates errors, can you send us an error report

for each job? These can be obtained by right-clicking on the job and

selecting Job Reports → View Errors.



Thanks!

5

Hello Ryan,



I’ve downloaded the latest Deadline version and the problem still

persists, i’ve attached error logs of both rendering methods you described.

The problem is easily reproduced, but if you like i can send the test

scene aswell.



With kind regards,

Sven Neve

–



House of Secrets

Mediapark - Mediacentrum | Sumatralaan 45 | 1217GP Hilversum | The

Netherlands

+31 (0)35 6409709 | +31 (0)6 25128136 | http://www.houseofsecrets.nl

6

Hi Sven,

Thanks for posting the logs. I have a feeling the error is occuring in our stdout parsing which sets the progress of the render. When I get back into the office on Monday, I'll see if I can figure out what the problem is.

Cheers,
 - Ryan

7

Hi Sven,



Can I bother you to send us a test scene that reproduces the problem? We

currently only have the Discovery version of LW 9.3, so I can’t save my

own scene for testing.



Thanks!!

8

Hello Ryan,



not a problem, let me prep one and send me it later today.



cheers,

Sven



Frantic_Deadline Listmanager wrote:

From: “Ryan Russell” (rrussell@franticfilms.com

mailto:rrussell@franticfilms.com)



Hi Sven,



Can I bother you to send us a test scene that reproduces the problem? We

currently only have the Discovery version of LW 9.3, so I can’t save my

own scene for testing.



Thanks!!

9

Here’s a test scene with 50 motion blur passes (can be adjusted with a

text editor aswell now that you have this scene)



cheers,



Sven


10

Thanks Sven!



The problem was with our progress parsing, and the fix is quite simple.

Navigate to \your\repository\plugins\Lightwave and open the file

Lightwave.mpr and change this line…



OutputRegEx5=(Rendering frame [0-9]+).* pass ([0-9]+).([0-9]+).



…to this…



OutputRegEx5=(Rendering frame [0-9]+). pass ([0-9]+)[^0-9]+([0-9]+).





Save the file, and then open Lightwave.mmp and change this line…



OutputRegEx6=(Rendering frame [0-9]+).* pass ([0-9]+).([0-9]+).



… to this…



OutputRegEx6=(Rendering frame [0-9]+). pass ([0-9]+)[^0-9]+([0-9]+).





After saving this second file, you should be good to go. Try submitting

a test job again and see if you have any luck. If it works, we’ll be

sure to include the fix in the next release.



Cheers,

11

Ryan i would just like to say thankyou for fixing this so fast, I also had this problem and have applied the fixes and all works great now.

We just bought 14 nodes of deadline and you service here conferms it was a good investment.

 

Thanks again.

12

Thank you Ryan, it all works as expected now.



Excellent support and service, we are still testing other rendermanagers aswell, but so far, i’m the most impressed with Deadline, this is probably doing to be our next rendermanager.



cheers,

Sven