[BUG] - Render queue state (activate/deactivate) not saved in friction project file

[samytichadou]

I recently had a paid gig where i used friction (yayyyy :) ) and i had to output a bunch of transparent graphics stating name/functions of characters for a documentary video.

To gain in efficiency, i had the render queue setup for each of them, and i just had to activate one or the other to output/overwrite when something has changed (because of the director choices).

But my friction project contains over 30 scenes, so 30 render in queue, and the state (render active or inactive) is unfortunately not retained in the friction project file, so on every startup i had to go through my 30+ render queue and deactivate them one by one...

I think this state should be saved in the friction project file, and a simple way to select all renders and active/deactivate them should be available to simplify this

[pgilfernandez]

I think it is not a bug but the default behavior, after a successful render, the job is unchecked.

Anyway, I agree with you that I would prefer to save your desired state in the project file.

[samytichadou]

I think it is not a bug but the default behavior, after a successful render, the job is unchecked.

Anyway, I agree with you that I would prefer to save your desired state in the project file.

Yes you are right, it is not "per se" a bug, but the situation that resulted feels wrong (all the queue is automatically activated on opening).
The user cannot select every render do deactivate them quickly, so you have to do it manually, one by one, for 30+ items in this case 🥲.

And it really feels to me, knowing everything in the queue except that is saved, that it should also be saved in the project