Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Submitted byAnonymouson06-15-201704:18 AM
Status:
Implemented
Render layer support for the render queue
It would make the render queue far more useful if it could save render layer activation. Currently you have to use sequencer because of this lack of render layer support.
This is now possible with the Cluster Queue since 2018.2. The render queue was designed to work with the simple UI that does not support render layer. Thus this capability is not part of the render queue.
You can submit job to the cluster queue and this will take into account every single attribute set in your scene.
That's a fair comment to assume but I spent a bit of time yesterday playing with it before I wrote that. I wrote it in haste as I was still a bit perplexed by the whole setup and outcomes I saw but from what I could make out it is not the next step up from the render queue. It could be but can't be at the same time.
I sent all my support questions to Nadja and so I will see if it makes more sense after and will then share my findings on the forum.
no worries. It was originally meant to allow different users to send render jobs to a central cluster that is scheduled and progressed in a prioritized order. So there is a difference between the two features. Flexibility often comes with a higher complexity of a feature, but this was the best way we saw to balance the needs of our big and small customers.
Please find a how to document on AKN under the following link. This hopefully clarifies some of your questions.
I know this is not explicitly solving the issue with the render queue but it solves the issue of not being able to queue render jobs with render layers. Therefore I pointed this out as a potential solution to this problem.
The premise is good as you could use vred without needing deadline and send your jobs to other nodes why you work however it is very limited/restrictive and again not a complete production friendly item. It seems like a quickly done add-on for a client who wanted it in this strange way.
All we want is the Render Queue to just support render layer states. Other people outside of our company have asked for this. It is not just us. If you can do that then we can push the render queue items to this new Cluster Queue and get the benefits of that new feature.Any nice functionaltoy/features on top of that is a bonus.
But as it stands this new Cluster Queue is not a production friendly feature.
I will not comment on the last thread as most of your assumption are obviously just wrong, uninformed and insulting the smart people working on VRED every day to make it best in class.
I will change the state to "Gathering Support" and we continue to work on it when it is getting interesting for more than the 3 people on this thread.
Sorry in my last comment I meant to end it "for us". I am sure it is production friendly for the customers who deem it useful for them. For us however it doesn't work quite how we would like for our workflow but I don't expect every new feature to do that.
Do you know why my assumptions in my last thread might have been uneducated and wrong...it is because you release updates and features without giving good education into how to use them. So forgive me for not knowing exactly how to use it but my comments were based on me testing it as best I could. I see you put the pdf up online after I had requested some documentation to support.
Of course you want Vred to be best in class. I think we may want it to be even better than you do as we are the ones using it for our work on a day to day basis. So we want it to be the best it possibly can be and we only ask for things that we think will make the software better and make users lives easier.
I will say it is good that you have now been responding and updating these Ideas threads. Thank you for that.
