Some random ideas for KeyShot Network Queue improvements.
- New user privilege: "Jobs by others visible" >> Makes sure that a user can/cannot see jobs submitted by other users.
- New sort filter: "Submit date" >> See on what date a job was added to the queue.
- New continuous refinement rendering >> Allows jobs to be rendered in the same way as realtime methods in KeyShot. Frames can be downloaded when an adequate quality level is reached. (aka Realtime Network Rendering... ;) )
- KeyShot Network profiles >> Allow users to save multiple Master configurations (hostname & port) for connecting to a queue. The user could then easily switch from one queue to another without having to manually dial in the connection settings every time. A plus would be that saved login credentials are saved as well.
- KeyShot Slave profiles >> Allow users to save multiple Master configurations (hostname & port) for connecting slave cores to a master. The user could then further specify core count and priority for each master profile.
Please feel free to add more.
Dries
Thanks Dries. I'm not sure I understand the benefits of network and slave profiles. NR supports scheduling for the slaves so can setup which slaves are being used when.
By profiles I mean setting connection settings for different masters.
Like now, I've started juggling network jobs between NR in office and NR at home. Call me crazy (some already did...), but I actually like this workflow a lot. :)
E.g. In the queue, it would be neat if I could select preconfigured master profiles so I could switch between queues with a simple click (no redialing of connection settings).
Dries
Like this...
Dries