I agree, the default location temp save should be in the same folder as the blend file, like Krita’s defautl autosaving. In windows, the /tmp file goes… sometimes literally nowhere till you program it.
In windows there isn’t such a problem, since tmp isn’t a memory folder. But for linux maybe something like ~/.tmp or ~/.blender_tmp, so it stays in user folder. Of course it will be the responsibility of the user to cleanup folder from time to time. The reasoning behind it being in the /tmp was to avoid user getting out of space due to a lot of autosaves as this is what happens in windows, getting 50+Gb tmp folders with a few weeks of temp files is very normal in professional workspace. As a TD I can’t recall how many times I wrote scripts and fixed this kind of problems on artist machines.
So in the end, if you are a making a living as professional user, one of the first things you do, is setup blender, and this includes setting keymaps, addons, navigation preferences and system paths.
Have a default autosave location that’s not in a location you have to hunt for Am not sure if the Data - Temporary Files location in Preferences - File Paths is the same; if not, an extra field could be added here to query such a location along with a limit on the number of automatic backup files as not to fill up your storage.
Having 1 file per day, a second that is saved each hour and a third being continuously saved might also be a good idea so you have some older files to get back to whole preventing total overflow in regards of storage.
Getting paid to work with blender means I’m a professional user.
And Autosaves in Blender are reliable if set up correctly. My main problem being I work a lot with in browser office tools, that save continuously and that leads to bad habits in offline tools like blender especially if I’m really focused on something.
sorry but u made terrible workflow mistake… and is not blender fault… blender have 2 independent backup system… 1 is in tmp… the other is versioning that u can setup how many u want to keep. basically it works in such way that if u set it to 3 for example it will save original file… + 3 backup copies that are saved… usually the first is last time u hit ctrl+s the next one is i think last 10 min and the next one is 30 min and the next is like 1-3h… i never really digged how it works… but that is in my case usuall timestamp on those files
Since I usually use the daily compiled version of blender,
Will often crash, so I developed a habit of saving at any time.
However, if you suddenly lose power while saving, the file will be broken and cannot be recovered.
I have encountered this situation before.
I only set up to save two versions, both versions are broken, and I was very depressed at the time.
Fortunately, there is a file that is not very far away from the auto-save file.
The saved function does not know if it can be optimized to avoid damage to the original file when the power is off.
I don’t really like auto-save. When the scene is very large, saving it on a mechanical hard drive will make the computer slow.
I think Blender especially needs a function like zbrush and maya that can be automatically saved in the event of a crash, which can largely avoid the user’s loss and reduce the risk of serious bugs.
I just want to point out the point of an autosave.
That is, to protect users in the case of a crash.
Many crashes impact the entire system (eg, power loss, catastrophic overheat, angry chainsaw attack). That is a problem. However, autosave ensures that you don’t lose much work. Even if you don’t save often (easy to do if you don’t have the right habits), you won’t lose a ton of work.
By saving to /tmp/, blender is making its autosave worse than useless at protecting data loss from total system crashes. I work with a graphics card that sometimes dies without warning. I know that blender has an autosave, and so I set my interval to be low and expected it to work without me needing to save frequently. When my card recently went down, I restarted my computer, expecting Blender to have autosaved. Except that, because of this issue, the autosave had been deleted. It only served to lure me into a false sense of security.
This problem has a ridiculously simple solution. Save to /var/tmp instead of /tmp. /var/tmp files are persistent through shutdowns, but are still allowed to be cleaned. This change would only help: there is no situation in which it hurts the user. It would literally take less time for someone to change the destination directory to /var/tmp than it would for someone else to write about why it is the responsibility of the user to change this folder every time they boot up.
I cannot stress this enough, but this is not a place to put blame.
I know it’s possible to change the deafult.
I know it’s possible to save.
I know it’s better to not rely on autosaves.
… I know blender is not a terrible software because of that choice.
But my point remains:
It’s a very odd choice, because it makes Autosaves voulnerable to system crashes and it is not compliant with software standards and changing that deafult will probably improve the usefulness of this feature.
So what if someone makes a mistake one time because of having a hard day? This happened to me today and I lost 8hrs of work. The purpose of autosave is to automatically save not save to tmpfs which may as well be /dev/null. My battery backup also failed.
In Linux /tmp folder is volatile. A kernel panic, power outage, or a system reboot will mean loss of files.
On Linux Trash system should be used by default in Blender. Also for Trash system you will surely have a very accessible icon/widget somewhere by default on any Linux distro. Added to this is that you can set the expiration date for files in Trash system, so that they are automatically deleted according to their age.