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

New Issue

Germano Cavalcante · 2023-05-05T20:20:25+02:00

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

Blender Version
Broken: 3.5.1, 3.6
Worked: maybe 3.4

Short description of error
Investigated in #107421 by @3di.
It's still unclear when this happens, but it could be replicated with the attached file.
The function void wm_autosave_timer(Main *bmain, wmWindowManager *wm, wmTimer * /*wt*/) in wm_files.cc skips AutoSave if any modal operators are running.
In this case, this can happen with the "CLIP_OT_solve_camera" operator even after the operation is theoretically completed.

Exact steps for others to reproduce the error

Unzip attached .blend file
Go to "Motion Tracking" workspace
In the solve tab, press Solve Camera Motion

Auto Save stops saving or saves very late.

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

**Blender Version** Broken: 3.5.1, 3.6 Worked: maybe 3.4 **Short description of error** Investigated in #107421 by @3di. It's still unclear when this happens, but it could be replicated with the attached file. The function `void wm_autosave_timer(Main *bmain, wmWindowManager *wm, wmTimer * /*wt*/)` in `wm_files.cc` skips AutoSave if any modal operators are running. In this case, this can happen with the `"CLIP_OT_solve_camera"` operator even after the operation is theoretically completed. **Exact steps for others to reproduce the error** - Unzip attached .blend file - Go to "Motion Tracking" workspace - In the solve tab, press `Solve Camera Motion` Auto Save stops saving or saves very late. https://www.dropbox.com/s/lmvuecn638kloax/no%20autosave.zip?dl=0

Germano Cavalcante added the

labels 2023-05-05 20:20:26 +02:00

Jesse Yurkovich added

and removed

labels 2023-05-07 02:47:56 +02:00

Sergey Sharybin commented

2023-05-08 12:05:08 +02:00

The only scenario where I can reproduce this is if one clicks on the "Solve" button and does not give any input after the solver is finished. The reason for this is because the modal handler of the operator checks for the job to exist, so there needs to be an event passed to the modal handler after the job is finished.

This behavior is the same with F12. So if that is the problem you're encountering it is not limited to this operator, and not to the VFX module.

If that is not the issue you're running into, then we need to know more details.

The only scenario where I can reproduce this is if one clicks on the "Solve" button and does not give any input after the solver is finished. The reason for this is because the modal handler of the operator checks for the job to exist, so there needs to be an event passed to the modal handler after the job is finished. This behavior is the same with F12. So if that is the problem you're encountering it is not limited to this operator, and not to the VFX module. If that is not the issue you're running into, then we need to know more details.

Sergey Sharybin added

Status

Needs Information from User

and removed

Status

Confirmed

labels 2023-05-08 12:05:21 +02:00

Pratik Borhade commented

2023-08-17 07:25:02 +02:00

@mano-wii ^

Pratik Borhade commented

2023-12-29 08:17:00 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Pratik Borhade closed this issue

2023-12-29 08:17:03 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-12-29 08:17:04 +01:00

Sign in to join this conversation.