Deadline problems with render node license

[gagui]

Hi, yesterday I've purchasaed a new render node license but My deadline is giving me errors saying that there is no license to render.
What colud be the problem here?

[gagui]

Here I show you some captures of the error deadline is giving me.

By the way, why is deadline making a task of 10 frames when I set it up to make 1 frame per task?

[gagui]

Today I've tried to render a deadline job in the same computer it was sent through deadline worker and I'm getting the same error. What could be the problem here? I'm a bit lost

[aneliya_karadzhova]

Hi gagui,

Can you please open a ticket at support.chaos.com? Our team will be able to look at this further for you.

[gagui]

Ok, anyway it would be of great help if someone can share a workflow between houdini, vray and deadline. I'm still a bit lost.

[Dubbie99]

Just use the Deadline node that comes with V-Ray.

Plug your renderer into it, press submit - done.

[bdancer]

> I'm getting the same error. What could be the problem here? I'm a bit lost

From what I see the error has nothing to do with V-Ray...

Try using our Deadline node as Dubbie99 suggested.

[gagui]

Well, after many tests I found the problem was caused by an outdated node from the Modeler plugin (the "mirror" node)
After updating to Modeler last version the problem was gone.

Anyway, now I'm using the v-ray deadline node as you people suggest and it's working kind of ok.
It does everything ok but for some reason the job output in the deadline monitor always points to the ROP export path and not the output path even if de job was submitted as a render only job.
Oddly the frames are saved in the correct output path but in deadline monitor if you look into job properties/submission Params the output directory corresponds to the ROP export path, not the output path.

Could anybody confirm this?

[Dubbie99]

Yeah this has been a longstanding issue.

[bdancer]

> Yeah this has been a longstanding issue.

Well I guess Deadline still doesn't support this filepath syntax. I'm not sure we could do anything on our side, but we may check again if we could workaround this somehow...

[Dubbie99]

Our internal Solaris deadline submitter sets the correct paths for task output browsing.
I don't think it is too tricky. As far as I know you just need to switch <frame04> to <$F4>

here is an example from our farm that works: