The crashes are just regular random ones I think, doing things with cycles viewport ect.. But hard to tell if it happened just right when the auto-save was trying to save, probably not as it…
This is still happening by the way, 3 years later on 3.6.3. Really glad this was the first result on google because already had another crazy bug today with autosaves.
Ok the last time I manualy backuped my userpref.blend file was 2 month ago, restored it, solved autosave, but I hope I didn't change anything since then.
Daamn, just lost work now. will need to go back to 3.5 or 4.0 I guess to be safe, but only because I migrated my prefs to 4.0 before this bug appeared.
Blender does mange to write the copy buffer files, for copy paste between files, so it's not an issue of folder access or something. it does manage to create a folder when opening a file, but not…
it seems to be a recurring issue, and people seem to have had to sacrifice their pref file, restore an older one ect..
https://www.reddit.com/r/blenderhelp/comments/mzqhss/blender_stopped_autosa…
Hi, thanks, just tried on 3.6.3, same behavior where my files are not autosaved, nothing is written. Obviously restoring factory settings solves it, autosave write again, but that's not an…
ok thanks, yes it won't happen on a blank file in factory settings, but I'm sure it'll keep happening on my end as it plagued my projects this year. But knowing it comes from the persitant data…
Autorig pro creator did not recall any of his like 40K+ users reporting this bug, I guess maybe because animators don't render so much, dunno, but I don't think I have much addon that could be…
Ah ok, well on my workfiles where the bug is live (not these cleaned-up files) I just have to press f12 while being on any frame, and that's it the current frame is now "cursed" and that's now…
Ah no need to render in theory, the bug is already present in the file, if you enter pose mode, select bones, move on the timeline, directly when opening the file. scrolling plays the animation…
Thanks Richard, yes that's it. here is the updated file where I had the bug for the first time, I verified and it does come from persistant data, even if the file is from January 2023, the…
Hi @iss I've just had a breakthought with that bug, the root cause is Cycles persistant data !! The bug appeared again today as I'm nearing the end of this project, so I felt discouraged, but I…
OK FOUND THE SOURCE !!! it's Cycles persistant data !!! I was sure it was something core to blender, not auto-rig or any of my projects.
Persitant data actually bakes-in the armature pose to…
Yes, if the last render is EEVEE, the bug does not appear anymore. If you render in Cycles, the armature will snap into the last renderd frame pose, no matter the frame you're on currently.
YES, confirmed, I did a new render, and the bug moved to that frame !!! so it is indeed something linked with rendering:
It is really…
As a proof, so now my armature snaps to the pose it has on that frame. Maybe there's something wrong happening with the "preserve data", it feels like blender is only able to recall the bones…
Ok the bug re-appeared, but this time there is no connexion between an empty and a bones, and no collection instances of this character, so as I guessed it can be triggered by a number of…