AWS Thinkbox Discussion Forums

lighting_startup.ms is being used by another process error.

Deadline
#1

Hi there,

I’m getting a ton of errors like this:

[code]=======================================================
Error Message

The process cannot access the file ‘C:\Users\loocas\AppData\Local\Temp\lightning_startup.ms’ because it is being used by another process.[/code]

on my farm from all my machines.

Sometimes the number of errors reaches the point it fails the job, but most of the times it just tries so many times until it works.

Any idea where the error might be coming from? The .ms file is certainly not being used by anything else than Deadline.

Trying to render with 3ds Max 2012 PU 5, Deadline v5.2.0.49424

#2

Hmm, I’ve seen this error with Max 2013, but never with 2012. Are you rendering with Concurrent Tasks greater than 1?

#3

My apologies, I am on Max 2013, it was a typo on my side.

I am rendering with Concurrent Tasks set to 1 and Limit Tasks to Slave’s Task limit set to True.

#4

Ah, cool.

The problem, from our understanding, is that 3dsmax 2013 locks our .ms script when it reads it in. This was never the case in 2012 and earlier. It appears that this lock can stick around a bit, and thus causes this error. It’s even worse with concurrent tasks > 1, because every task but the first will almost always hit this error.

We’ve addressed this issue in Deadline 6 by completely refactoring how 3dsmax gets the information that would normally go inside the .ms file. Now we have it working without requiring the .ms file at all, and that seems to fix the issue.

Cheers,

  • Ryan
#5

Ryan,
Has this made it into the beta build available yet? - (Didn’t see any notes on this topic)
Thanks,
Mike

#6

Yup, it’s been in there since beta 8.

Cheers,

  • Ryan
#7

Ah, ok, so my options are either not render in 2013, or update everything to the beta of Deadline 6. :slight_smile: Not really great in the middle of production.

Unfortunately I have to render a ton of very simple scenes that take about a minute or so to render, but as I said, it’s going to be hundreds, or rather thousands of those scenes. :confused:

So there is nothing else I can do about it? If not, I’ll go for the beta then.

#8

Unfortunately, there isn’t a known workaround for Deadline 5.2. The 3dsmax plugin went through some heavy refactoring in 6.0 to workaround this issue, and we has to update the plugin so that it would work with version 6. :frowning:

#9

Ok then. Well, at least it works in 6. :slight_smile:

Thank you, I’ll test 6 some more in my VMs and then deploy on my farm.

Privacy | Site terms | Cookie preferences