That I can guarantee did not happen.
I highly recommend you adopt an “Iterate” workflow. Your current workflow is non-optimal.
1 Like
I’ll make a note of that. Thanks.
i just uodate the batch to v002 idk why iterations exist they seem to constantly reset their count when i open the batch on different machine
1 Like
Iterations are stored locally but also act as a way to version up your setup.
When you load a setup on a different machine there is no known local version so iterate will ask/try and start again at 1
It does seem as if there are three (or more) ways to save your setup 
My resetting write nodes are named the same but are sending to different locations. Maybe that is why mine are getting confused 
1 Like
the disk based ascii batch files are more of an emergency backup, they aren’t really great at being the “working file”. Batch Groups and Iterations are meant for that.
yea but thats kinda the idea behind the openclips workflow, we pass those around we dont have anything inside the flame project itself.
Would make it all very unconfortable for us, as we use this with a hybrid/remote workforce that isnt connected to project servers or anything
also enables us to mix and match flame versions.
In an openclip workflow, iterations are a localized versioning system and only important to local work. What’s rendered is what’s published and is actually the only thing that actually matters for workgroups as the setups which are saved by the render are the only setups attached to the resultant render.
The openclips have no way of retracing their steps back to which seat of Flame created them and which iteration, only what setup is associated with which particular version of an openclip.
Edit: long way of saying they’re different mechanisms for different puposes.
2 Likes
Indeed, the Alt-Save file is exactly that; an emergency backup. And as serendipity would have it, not long after I wrote that, I crashed when I hit the render button, but the backup saved my last few changes. As far as iterations go, in my work there’s little aesthetic except for the skill and finesse I bring to the task. It’s basically either right or wrong. If it’s wrong, I have no need to save it. It is VERY rare that I need to step back to an earlier version. If I feel in my gut that I might want to do that, then I do as Finn does: I make a copy and change the suffix. I do that maybe one batch in ten jobs. When you take into consideration all the downsides the others have mentioned, I have no use for iterations. I write over my previous setup as I work.
1 Like
There is a Preference to save disk based Batch file automatically when you Iterate. We haven’t manually saved in a decade.
I have 3 decades of muscle memory. I don’t need to iterate to save myself micro seconds of work.
Guess that is working out well for you then?
Wonderfully
Have you changed the default destination to get saved on the server because by default this just saves to my local machine?
Sweet, so topic solved?
Yes, we changed it to a central project based location.
1 Like
This wasn’t the topic. You hijacked my thread
Iterations/Batch Groups is the solution.
Heeding my late mother’s advice about saying things nice or shutting up is the solution at this point.
I’m choosing the latter
1 Like