@spikeyxxx Yes, that’s the nature of syncing and it’s particularly good for rendering. The reason being that Blender looks in that folder for frames that are already rendered so it can skip them and start working on un-rendered frames.
You could work around this. You could tell lsync (or officialgoogle drive app on mac/windows) to not sync the frame files themselves via the selective sync preferences. NOTE you’d have to uncheck each rendered file (so 395 checks based on the count as of the time I’m typing) but leave the folder still syncing.
This means the files stay in the cloud but aren’t duplicated to your local hard drive. IF you go that route, you would need to open the .blend file and change the start frame to align with the frames already rendered to the cloud (which you can check via the google drive website). Then your renders would still go to the cloud but you would have skipped waiting for 395 existing frames to be duplicated to your local drive.
I recommend the first way, just letting everything sync and then start rendering. But the second option is doable.
