Auto-Save doesn't work in Edit Mode #107421

New Issue

michael campbell · 2023-04-28T06:13:27+02:00

michael campbell commented

2023-04-28 06:13:27 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98

Blender Version
Broken: version: 3.5.1 Release Candidate, branch: blender-v3.5-release, commit date: 2023-04-21 11:31, hash: 93dac7da2c6a
Worked: 3.4

Short description of error
Autosave intermittently doesn't work (2 mins)

I was using blender all day today, but when I had a crash just now, I chose to recover from autosaves, and there were only blend files from yesterday in there. I was using the same version of Blender yesterday, so I'm not sure why it would suddenly not be working. I wouldn't have noticed if Blender hadn't crashed, and that's so rare that perhaps it's leading to the problem going un-noticed :)

The blend file that just crashed wasn't saved, but the ones I was working on earlier were, and there are no autosaves for them in the temp folder either.

Exact steps for others to reproduce the error

Save a .blend file with any name
Go to Edit mode
Delete all the mesh and add another one (like Suzane)
Wait about 2 minutes without exiting Edit mode
Open the generated Auto-Save file (File > Recover > Auto Save...)

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98 **Blender Version** Broken: version: 3.5.1 Release Candidate, branch: blender-v3.5-release, commit date: 2023-04-21 11:31, hash: `93dac7da2c6a` Worked: 3.4 **Short description of error** Autosave intermittently doesn't work (2 mins) ![image](/attachments/b0d00ab6-2cce-4c22-8de6-6cbec0c96cf7) I was using blender all day today, but when I had a crash just now, I chose to recover from autosaves, and there were only blend files from yesterday in there. I was using the same version of Blender yesterday, so I'm not sure why it would suddenly not be working. I wouldn't have noticed if Blender hadn't crashed, and that's so rare that perhaps it's leading to the problem going un-noticed :) The blend file that just crashed wasn't saved, but the ones I was working on earlier were, and there are no autosaves for them in the temp folder either. **Exact steps for others to reproduce the error** - Save a .blend file with any name - Go to Edit mode - Delete all the mesh and add another one (like Suzane) - Wait about 2 minutes without exiting Edit mode - Open the generated Auto-Save file (`File` > `Recover` > `Auto Save...`)

image.png

42 KiB

michael campbell added the

labels 2023-04-28 06:13:27 +02:00

Germano Cavalcante commented

2023-04-28 22:44:11 +02:00

Auto-Save works as far as I can test.

I forced Blender to close through Debugger. But, to test, you can also just close Blender without saving.

I could be wrong, but apparently changes in edit mode are not saved in the file. You have to exit edit mode to sort of update the original mesh. The original mesh is the one used for saving.

Is this what you are witnessing? Auto-Save not saving mesh in edit mode?

Perhaps Blender could treat edited meshes differently and apply changes to the original mesh on every Auto-Save.

Even without confirming what's going on, I think Auto-Save in edit mode is something developers need to consider. So I'll set the report as "Needs Info From Developers".

Auto-Save works as far as I can test. I forced Blender to close through Debugger. But, to test, you can also just close Blender without saving. I could be wrong, but apparently changes in edit mode are not saved in the file. You have to exit edit mode to sort of update the original mesh. The original mesh is the one used for saving. Is this what you are witnessing? Auto-Save not saving mesh in edit mode? Perhaps Blender could treat edited meshes differently and apply changes to the original mesh on every Auto-Save. Even without confirming what's going on, I think Auto-Save in edit mode is something developers need to consider. So I'll set the report as "Needs Info From Developers".

Germano Cavalcante changed title from ~~autosave intermittently doesn't work~~ to Auto-Save doesn't work in Edit Mode

2023-04-28 22:50:34 +02:00

Germano Cavalcante added

Status

Needs Info from Developers

and removed

labels 2023-04-28 22:51:06 +02:00

Germano Cavalcante commented

2023-04-28 22:51:34 +02:00

I edited the description to something that might be replicable

michael campbell commented

2023-04-28 22:54:13 +02:00

Edit mode wasn't the issue for me. I'd been working all day in several files in the motion tracker workspace, compositor and general rendering work. But non of the files had an auto save present in the temp folder when I checked at the end of the day.

So it wasn't a case of there being a file in there with an out of date mesh, but more the case no autosave files had been generated.

Edit mode wasn't the issue for me. I'd been working all day in several files in the motion tracker workspace, compositor and general rendering work. But non of the files had an auto save present in the temp folder when I checked at the end of the day. So it wasn't a case of there being a file in there with an out of date mesh, but more the case no autosave files had been generated.

Jesse Yurkovich commented

2023-04-28 23:12:49 +02:00

Another possibility is that there's an Operator active - like say a modal hooked to a timer (which still counts as active). You can repro this with the Operator Modal Timer template in the script editor. As long as that operator is active, no auto-saves will occur.

Germano Cavalcante commented

2023-04-28 23:30:06 +02:00

Edit mode wasn't the issue for me. I'd been working all day in several files in the motion tracker workspace, compositor and general rendering work. But non of the files had an auto save present in the temp folder when I checked at the end of the day.

So it wasn't a case of there being a file in there with an out of date mesh, but more the case no autosave files had been generated.

Without being able to replicate the problem there is not much we can do unfortunately.

> Edit mode wasn't the issue for me. I'd been working all day in several files in the motion tracker workspace, compositor and general rendering work. But non of the files had an auto save present in the temp folder when I checked at the end of the day. > > So it wasn't a case of there being a file in there with an out of date mesh, but more the case no autosave files had been generated. Without being able to replicate the problem there is not much we can do unfortunately.

michael campbell commented

2023-04-28 23:33:19 +02:00

oh, is there a way to check if there's a modal/timer running from within Blender?

Germano Cavalcante commented

2023-04-28 23:40:11 +02:00

I don't know an easy way to do this without compiling Blender.
modal handlers can be added by addons (low quality addons).
The best would be to disable addons and test Auto-Save.

I don't know an easy way to do this without compiling Blender. modal handlers can be added by addons (low quality addons). The best would be to disable addons and test Auto-Save.

michael campbell commented

2023-04-29 16:37:07 +02:00

Yeah, no new addons installed or used that have modals in between.

I did install this one though
https://github.com/s-leger/blenderTracking/blob/master/space_clipEditor_refine_solution.py

But it doesn't have any timers, modals, or queues.

Here's my folders for comparison.

Restarting Blender just now and it started creating autosaves again. I think it's maybe a problem with continuing working with Blender after the PC has been in sleep mode, or maybe one of the operators in the camera tracking workspace. I used Solve camera motion, clean and filter tracks, and detect features. I also noticed that undo also stopped working for deleted camera markers around the same time as noticing this issue.

Perhaps autosave doesn't automatically save every 2 mins unless it detects changes in the scene? And changes in motion tracking are not being detected by it? Because my autosave isn't getting updated every 2 mins, it's still stuck at 15:30 as the latest, even though it's now 15:36 and I have it set to 2 mins.

Yeah, no new addons installed or used that have modals in between. I did install this one though ![image](/attachments/f4da81c3-136f-4ded-8467-e508beaff64a) https://github.com/s-leger/blenderTracking/blob/master/space_clipEditor_refine_solution.py But it doesn't have any timers, modals, or queues. Here's my folders for comparison. ![image](/attachments/76edbf84-b4a3-4862-bf9b-9beee384c8cd) Restarting Blender just now and it started creating autosaves again. I think it's maybe a problem with continuing working with Blender after the PC has been in sleep mode, or maybe one of the operators in the camera tracking workspace. I used Solve camera motion, clean and filter tracks, and detect features. I also noticed that undo also stopped working for deleted camera markers around the same time as noticing this issue. Perhaps autosave doesn't automatically save every 2 mins unless it detects changes in the scene? And changes in motion tracking are not being detected by it? Because my autosave isn't getting updated every 2 mins, it's still stuck at 15:30 as the latest, even though it's now 15:36 and I have it set to 2 mins.

image.png

1.0 MiB

image.png

86 KiB

michael campbell commented

2023-04-29 16:40:16 +02:00

Although I just made some other changes to the rotation of objects and things, and still no new autosave. hmm. I'm wondering if it's creating one autosave, and then no longer creating new ones after that.

michael campbell commented

2023-04-29 17:13:20 +02:00

I've just found that it works until I run the solve camera operator. After that autosaves stop getting created, but there are no messages in the console saying 'unable to autosave' which apparently should happen if it fails.

Germano Cavalcante commented

2023-05-02 16:01:59 +02:00

I've just found that it works until I run the solve camera operator. After that autosaves stop getting created, but there are no messages in the console saying 'unable to autosave' which apparently should happen if it fails.

Do you mean Solve Camera Motion in Movie Clip Editor?
I tested it with a simple video and some tracks, but Auto-Save still works.
(I also checked the date of the generated AutoSave file).

But I noticed that as long as we keep the File Browser window open, Auto Save doesn't work. Was this your case?

> I've just found that it works until I run the solve camera operator. After that autosaves stop getting created, but there are no messages in the console saying 'unable to autosave' which apparently should happen if it fails. Do you mean `Solve Camera Motion` in Movie Clip Editor? I tested it with a simple video and some tracks, but Auto-Save still works. (I also checked the date of the generated AutoSave file). But I noticed that as long as we keep the File Browser window open, Auto Save doesn't work. Was this your case?

Germano Cavalcante referenced this issue

2023-05-02 17:49:57 +02:00

WM: don't skip AutoSave if modal operator is 'fileselect' #107555

michael campbell commented

2023-05-02 18:58:27 +02:00

yes that's the one, solve motion camera.

No I didn't have the file browser open.

yes that's the one, solve motion camera. ![image](/attachments/60693128-985f-43b4-8cb8-ff79b82e6785) No I didn't have the file browser open.

image.png

60 KiB

Germano Cavalcante commented

2023-05-02 19:44:29 +02:00

Please provide clearer steps on how to reproduce the bug. A .blend file for example would help.

Avoid flooding the page.

I tested it with a simple video and some tracks, but Auto-Save still works.

Please provide clearer steps on how to reproduce the bug. A .blend file for example would help. Avoid flooding the page. > I tested it with a simple video and some tracks, but Auto-Save still works.

michael campbell commented

2023-05-02 21:03:33 +02:00

open file. set up as above. solve camera. If doesn't happen, try both clean up operations (clean tracks/filter tracks) then resolve again.

https://www.dropbox.com/s/lmvuecn638kloax/no%20autosave.zip?dl=0

open file. set up as above. solve camera. If doesn't happen, try both clean up operations (clean tracks/filter tracks) then resolve again. https://www.dropbox.com/s/lmvuecn638kloax/no%20autosave.zip?dl=0

Germano Cavalcante commented

2023-05-05 20:11:10 +02:00

open file. set up as above. solve camera. If doesn't happen, try both clean up operations (clean tracks/filter tracks) then resolve again.

https://www.dropbox.com/s/lmvuecn638kloax/no%20autosave.zip?dl=0

I can confirm now! The "CLIP_OT_solve_camera" operator keeps running even after it is resolved.
It is indeed a bug.
But since this report is edited, waiting for input from developers and with comments that mention different things, I will create another report.

Thanks for the find.

> open file. set up as above. solve camera. If doesn't happen, try both clean up operations (clean tracks/filter tracks) then resolve again. > > https://www.dropbox.com/s/lmvuecn638kloax/no%20autosave.zip?dl=0 I can confirm now! The "CLIP_OT_solve_camera" operator keeps running even after it is resolved. It is indeed a bug. But since this report is edited, waiting for input from developers and with comments that mention different things, I will create another report. Thanks for the find.

Germano Cavalcante referenced this issue

2023-05-05 20:20:27 +02:00

'Solve Camera Motion' operator sometimes prevents Auto Save from running #107665

Pratik Borhade commented

2023-09-18 06:46:18 +02:00

Going over the report description, I suspect this is same as #101710 (make sense if memfile is used for auto save file)
@mano-wii ^

Going over the report description, I suspect this is same as #101710 (make sense if `memfile` is used for auto save file) @mano-wii ^

Germano Cavalcante commented

2023-09-18 14:33:25 +02:00

You're right @PratikPB2123 ! It's the same problem.
(When editing the original report I didn't realize I was creating a duplicate).

You're right @PratikPB2123 ! It's the same problem. (When editing the original report I didn't realize I was creating a duplicate).

Germano Cavalcante closed this issue