- Posts: 58
- Joined: Mon Apr 14, 2014 12:06 pm
- Location: Johannesburg, South Africa
Fri Jul 02, 2021 1:14 pm
I'm experiencing the following issue since updating to 17.2.2:
If I add renders from different projects, and then "show all projects" and fire off the batch, resolve renders out the first project that is in the render queue for every instance in the render queue. Neatly puts the exports in the different locations, but it is the same file - the first render in the list. If I turn off "show all projects" and go back to the first project after rendering, there are now 5 queued instances of the same render, pointing at the different locations specified for the different projects. When going back to each of the other projects, there are now no items in their respective render queues. This is on MacOS Mojave, PostgreSQL database.
If I add renders from different projects, and then "show all projects" and fire off the batch, resolve renders out the first project that is in the render queue for every instance in the render queue. Neatly puts the exports in the different locations, but it is the same file - the first render in the list. If I turn off "show all projects" and go back to the first project after rendering, there are now 5 queued instances of the same render, pointing at the different locations specified for the different projects. When going back to each of the other projects, there are now no items in their respective render queues. This is on MacOS Mojave, PostgreSQL database.