Adding and enforcing custom fields

Post your messages that do not fit in the other rooms here.
Post Reply
ch3m1kal
Posts: 31
Joined: 23 Feb 2015, 13:09

Adding and enforcing custom fields

Post by ch3m1kal » 28 Aug 2017, 15:45

Hi,

I was just wonder if it's possible to add custom fields when submitting jobs and ideally making some of them mandatory.
For example, adding a field for due date of a specific render, or even making the "Project" field mandatory. Also why do some things only exist while editing net jobs, but not in the submitter?

Thanks!

User avatar
Shoran Support
RenderPal Team
Posts: 1227
Joined: 11 Apr 2008, 00:35
Location: Germany
Contact:

Re: Adding and enforcing custom fields

Post by Shoran Support » 28 Aug 2017, 16:01

That's not possible, no. Some fields have simply not been added to the submitter yet.

ch3m1kal
Posts: 31
Joined: 23 Feb 2015, 13:09

Re: Adding and enforcing custom fields

Post by ch3m1kal » 28 Aug 2017, 16:18

That's sad to hear.
I don't suppose it's planned for a near-ish release?

Meanwhile there's no way to maybe feed custom metadata at least, maybe via a python pre-execution event?

User avatar
Shoran Support
RenderPal Team
Posts: 1227
Joined: 11 Apr 2008, 00:35
Location: Germany
Contact:

Re: Adding and enforcing custom fields

Post by Shoran Support » 28 Aug 2017, 16:37

You can always pass arbitrary additional command-line switches to the underlying console RC when using the submitter. Take a look at the nj_project and nj_setfield switches (RenderPal V2 manual chapter 27.2).

ch3m1kal
Posts: 31
Joined: 23 Feb 2015, 13:09

Re: Adding and enforcing custom fields

Post by ch3m1kal » 29 Aug 2017, 09:17

Hmm looks like it may be possible with a combination of nj_setfield, nj_tags and nj_project, but that would require us to basically write our own submitter.

Thanks for the tip!

User avatar
Shoran Support
RenderPal Team
Posts: 1227
Joined: 11 Apr 2008, 00:35
Location: Germany
Contact:

Re: Adding and enforcing custom fields

Post by Shoran Support » 29 Aug 2017, 12:31

Another way to go might be to not use custom fields but to add new parameters to the renderer(s) you use; these can be made mandatory.

Post Reply