Autokey function hinders execution of drivers #95364

New Issue

Ajlan Altug · 2022-01-31T17:44:04+01:00

Ajlan Altug commented

2022-01-31 17:44:04 +01:00

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

Blender Version
Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: dc2d180181
Worked: Never (2.80+)

Open General template
Enable auto-keyframing in preferences for new scenes
Create new scene
Add cube
To Location X type #frame
Scrub timeline

Driver won't update

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77 **Blender Version** Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `dc2d180181` Worked: Never (2.80+) - Open General template - Enable auto-keyframing in preferences for new scenes - Create new scene - Add cube - To Location X type `#frame` - Scrub timeline Driver won't update

Ajlan Altug commented

2022-01-31 17:44:04 +01:00

Added subscriber: @noc2

Ajlan Altug commented

2022-01-31 18:24:52 +01:00

Ok, this is definitely a bug!! I just reset my entire startup file and created new layouts and the problem still persists. Custom layouts do stop channel drivers from executing!

Ajlan Altug commented

2022-01-31 18:31:30 +01:00

Ok, found the culprit. The "Auto Keying" button makes this happen. If you have it active by default in your prefs and/or if it's active, time based drivers will not be executed. Which is BS really, as it should have absolutely nothing to do with driver execution.

Note that this does not apply for already applied channel drivers. It basically occurs with new drivers created in a given session while auto-keying is active!

Ok, found the culprit. The "Auto Keying" button makes this happen. If you have it active by default in your prefs and/or if it's active, time based drivers will not be executed. Which is BS really, as it should have absolutely nothing to do with driver execution. Note that this does not apply for already applied channel drivers. It basically occurs with new drivers created in a given session while auto-keying is active!

Richard Antalik commented

2022-02-01 04:07:10 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-02-01 04:07:10 +01:00

I can reproduce issue with provided file, but not just by enabling auto keying. Can you provide steps how to recreate bad file from scratch?

Richard Antalik commented

2022-02-01 04:07:17 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Ajlan Altug commented

2022-02-01 04:22:27 +01:00

Hi Richard. Turns out the problem stems from the autokey function itself. Go into prefs and check the option for having autokey on in all sessions. Reopen Blender and with autokey enabled, create a time based driver on any channel (#frame) You'll see that it won't work as expected, ie. it will always be zero although from the driver edit panel you'll see that the driver is able to read the current frame but can not output it. Turn off the autokey function from the UI and repeat the process on some other parameter, you'll see that this time round, the driver will work correctly and as expected.

Ajlan Altug changed title from ~~Something in my startup blend file is hindering execution of drivers~~ to Autokey function hinders execution of drivers

2022-02-01 04:23:25 +01:00

Richard Antalik commented

2022-02-02 00:15:34 +01:00

I can reproduce when I enable auto keyframing for new scenes. Is this option you reffer to? I don't use this feature very often.

Richard Antalik commented

2022-02-02 00:19:06 +01:00

Changed status from 'Needs User Info' to: 'Confirmed'

Ajlan Altug commented

2022-02-02 00:36:23 +01:00

In #95364#1299646, @iss wrote:
I can reproduce when I enable auto keyframing for new scenes. Is this option you reffer to? I don't use this feature very often.

Yup, that's it. But you don't need to have it turned on for all sessions for the bug to occur I guess, just turning autokeying on from within the interface in every new session does cause a time based driver to not function properly afaicr. Could you also give that a whirl just to confirm?

As for Autokeying, I have it on at all times, as no animator will ever work without it switched on, in any DCC application afaik :)

> In #95364#1299646, @iss wrote: > I can reproduce when I enable auto keyframing for new scenes. Is this option you reffer to? I don't use this feature very often. Yup, that's it. But you don't need to have it turned on for all sessions for the bug to occur I guess, just turning autokeying on from within the interface in every new session does cause a time based driver to not function properly afaicr. Could you also give that a whirl just to confirm? As for Autokeying, I have it on at all times, as no animator will ever work without it switched on, in any DCC application afaik :)

Ajlan Altug commented

2022-02-10 19:24:21 +01:00

Hi. 3.1 release is a month ahead. Is there any chance this bug fix could be included in it?

Cheers :)

AJ

Hi. 3.1 release is a month ahead. Is there any chance this bug fix could be included in it? Cheers :) AJ

Ajlan Altug commented

2022-03-02 01:53:36 +01:00

Can I please have some confirmation whether the bug fix for this one has been added to 3.1 release? It is a legit confirmed bug.

Richard Antalik commented

2022-03-02 23:59:59 +01:00

Once fix is implemented, this report will be closed automatically. It would be great if it could be fixed right away, but there are about 1600 other confirmed bugs.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Autokey function hinders execution of drivers #95364