Page MenuHome

Drivers/Auto-run Scripts issue on reload
Closed, ResolvedPublic


System Information
Windows 8.1 64 bit, nVidia GT740

Blender Version
Broken: 2.77a
Worked: 2.74

Short description of error
You make something act basing on a driver. All works perfectly.
Then you close the file, reopen it, and it tells you that the Auto-Run Scripts is not enabled.

Exact steps for others to reproduce the error
You make something act basing on a driver. All works perfectly.
Then you close the file, reopen it, and it tells you that the Auto-Run Scripts is not enabled.
Workaround: Open the preferences, disable and re-enable the Auto-Run Scripts option, save the prefs.
Note: you also have to move to the next frame and back, in order for the driver variable to update.

Event Timeline

Luca Crisi (BugFinder) raised the priority of this task from to Needs Triage by Developer.
Luca Crisi (BugFinder) updated the task description. (Show Details)
Luca Crisi (BugFinder) set Type to Bug.

In user Preferences you must set Auto Run Scripts to true if you want to automatically run your drivers, else you will get the message: "Auto Run Scripts disabled, Reload?" which gives you the opportunity to 'Reload' the file with drivers enabled.. This is not a bug, but by design to prevent unwanted data execution.
Closing as Invalid.

Obviously, Auto-run python scripts is always enabled in my preferences.

Reopen my report, because the bug persists.

It's too easy to close bug reports without even trying to reproduce them!

You didn't even read my report.

I said You make something act basing on a driver. All works perfectly.
It wouldn't work, if Auto-run python scripts was disabled!!

@Luca Crisi (BugFinder)
Can you provide a small example .blend file to test? If so & the bug is reproducible. (provide steps needed to reproduce with your .blend) I'll re-open.

Sure, I will.
Thank you.

OK, here's an example file.
You'll notice IMMEDIATELY, on openin that there's an error.
Even if your preferences are set for Auto-running the scripts.

Some Screenshots can help,I guess?

Thank you

It seems I found a faster workaround to this problem:

  • Soon after loading the file, click "Reload trusted" and then confirm.

It seems to work well, as if you followed the 4 steps above.
But it's still a workaround.

So? Still not fixed?
Who will tell me this time that this is a feature?

Can't reproduce.
At loading, I don't have "Reload trusted" option when Auto-run is on, and saved on my userprefs. Driver is working correctly.

Did you tried on another computer ?
Did you check on console if there is some error / warning message ? (at load, at userprefs saving)

Yes I tried on 2 different computers.

By the way, I recently noticed that it also happens when I set #frame * 0.05 (well, the multiplier is NOT mandatory) on either a location or a rotation axis (or more).
This is because Blender implicitly creates a driver for that continuous rotation or translation.

Did you check on console ... No, I will investigate on that (fisrt of all I must discover how can I access that "Console").

Thank you for your suggestion.

OK, checked - NO ERRORS.
Only the DRAG of having to click RELOAD TRUSTED.

Julian Eisel (Severin) reopened this task as Open.May 17 2016, 3:48 PM

Can't reproduce either. I have the assumption that this is caused by the error prone filepath handling of windows. The code that checks if autorun is enabled works quite different for windows to allow case insensitive path comparisons. The changes made to the file browser that have been made since 2.74 might really well have caused such a regression.
Has anyone tried to reproduce on Win(8.1)?

@Luca Crisi (BugFinder), you can try to load the file from a filepath without any spaces and upper case letters.

Julian Eisel (Severin) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.May 17 2016, 3:48 PM

... Windows can handle spaces and mixed case letters since at least 20 years... (Windows 95).
I always use both spaces and mixed case characters.
But I can try.

I just need a couple of hours to render a *low-res and very noisy* picture (yes I know Blender Render does it better and faster, but I've choosen Cycles since 1.5 years now and I only use that one - with all its limits).

In Blender 2.75 there was a HORRIBLE regression which introduced underscores in place of spaces - Which was really DISGUSTING.
But it has been fixed in Blender 2.75a.

I'll be back!

hi, under correct usage you would do the following:

1/ enable auto run drivers
2/ Save User Settings in the User Preferences window
3/ restart blender

Following this convention you should have no more issues with drivers & be able to open blend files with drivers with no problems or pop ups.
Note: your last comment is unrelated & this is not the forum for yelling about things.

Closing as Invalid.

Talked with @Brendon Murphy (meta-androcto) over IRC, really don't see a reason to close this yet. It's possible this is a real bug, but it can also be a user error. @Luca Crisi (BugFinder), would you mind updating your current userpref.blend again? Would help investigating.

Well, this was really what I tried first: Verify that my Autorun scripts was enabled in the preferences.
I thought it was logic that Blender was complaining for a distraction by my side.

But It was already set.

I also tried renaming a test file with all small caps and underscores in place of spaces, but...
It didn't work either.

Sorry, @Julian Eisel (Severin), it didn't help (luckily for me - or I should rethink all my work habits).

My userpref file, in case someone wants to analyze it.
Thank you for your efforts!

hi, you didn't upload the userpref file.

I have tested your test file in the original task on win 7 64 bit. I found no issue at all with it.
Once I had set Auto Run Scripts to be the default, there was no problem or warnings associated with your file & the running of drivers.

There's a difference between Ctrl/U Save Start Up File (creates file called startup.blend), this file handles screen layouts & default start objects.
& the Save User Settings Button in the User Preferences window (Creates file called userpref,blend), this file handles settings in user preferences including Auto Run Scripts & addons activation.

Your initial 'bug' by your description, strongly suggests you were saving Ctrl/U & not pressing the Save User Settings button.
Please upload your userpref.blend so we can test.

Here is my userpref.blend.
Hopefully it uploads this time?

Do you need my startup.blend{F313445} as well?
I will upload it too.

Thank you

Damn! It seems I can't upload userpref.blend!!

Damn! It seems I can't upload userpref.blend!!

@Luca Crisi (BugFinder), hi again, here's your fixed userprefs.blend

here's a screenshot of what I believe causes the issue you had:

You can see here that the Excluded Paths button is activated but no path set. If you deactivate the empty excluded paths menu item (press the x button then save user settings) everything works as expected.

I'll refer this forward to devs as it may well be considered a bug.

Thanks for time to continue through & help us find result.

Thank you!

1 - I opened an empty scene, fixed the Preferences and saved.
2 - I opened a problematic file, and... the bug was GONE!!

Thank you, Thank you, Thank you!!

Now I have another problem ("double visualization" in editing).

I have a "double" representation of the edited object, instead of being a single solid thing.
This is confusing: The "fill" is smaller than the "wireframe", instead of being attached to it.

Shall I open another bug report?
Maybe it's a simple setting I'm just not aware of, but I can't even explain it in words...

Hey, so this seems like a bug, but I can't recreate here. Guess it's a Win-only bug then.

Bastien Montagne (mont29) claimed this task.

Please do not mix issues in reports, new problem requires a new report (this one totally looks like a graphic driver issue though, please first ensure you have latest one installed).

This one is considered solved (invalid actually, was mere lack of knowledge about how userpref saving works).

Thank you!

1 - I opened an empty scene, fixed the Preferences and saved.
2 - I opened a problematic file, and... the bug was GONE!!

Thank you, Thank you, Thank you!!

To be considered SOLVED.

Julian Eisel (Severin) reopened this task as Open.Jun 2 2016, 11:32 PM

@Bastien Montagne (mont29), if I got things correctly we still have a wrong behavior on Win here: Apparently, even if auto-run is enabled, enabling path excluding without setting a path simply excludes all files from auto-running. Works fine on Linux.