Lock Interface toggle will not toggle #85244

Closed
opened 2021-01-31 06:29:04 +01:00 by Joshua · 26 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40

Blender Version
Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-30 20:50, hash: 40061911d2
Worked: (newest version of Blender that worked as expected)

Short description of error
Lock Interface option is randomly toggled on and getting locked and cannot be toggled off. This occurs in the newest 2.92 Beta, but I have experienced it in 2.90, 2.80-.82.

Exact steps for others to reproduce the error
No known steps. Literally just happens at random in my experience. The issue transfers with .blend files. I have tried appending scenes into new .blend files and the issue comes with it.
Provided a .blend where the option will not toggle off.

Lock Interface Bug.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40 **Blender Version** Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-30 20:50, hash: `40061911d2` Worked: (newest version of Blender that worked as expected) **Short description of error** Lock Interface option is randomly toggled on and getting locked and cannot be toggled off. This occurs in the newest 2.92 Beta, but I have experienced it in 2.90, 2.80-.82. **Exact steps for others to reproduce the error** No known steps. Literally just happens at random in my experience. The issue transfers with .blend files. I have tried appending scenes into new .blend files and the issue comes with it. Provided a .blend where the option will not toggle off. [Lock Interface Bug.blend](https://archive.blender.org/developer/F9605842/Lock_Interface_Bug.blend)
Author

Added subscriber: @vfxninjaeditor

Added subscriber: @vfxninjaeditor
Joshua changed title from Lock Interface toggle is will not toggle to Lock Interface toggle will not toggle 2021-01-31 06:29:18 +01:00

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

Just an FYI:
I was able to unlock on my machine, 1-30 build.
OSX High Sierra.

Just an FYI: I was able to unlock on my machine, 1-30 build. OSX High Sierra.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Works here as well

**System Information**
Operating system: Linux-5.9.16-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01
version: 2.92.0 Beta, branch: master, commit date: 2021-01-31 13:31, hash: `rBa9b53daf23ba`

@vfxninjaeditor : just to make sure:
Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.

Works here as well ``` **System Information** Operating system: Linux-5.9.16-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01 version: 2.92.0 Beta, branch: master, commit date: 2021-01-31 13:31, hash: `rBa9b53daf23ba` ``` @vfxninjaeditor : just to make sure: Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.

Added subscriber: @johannes.wilde

Added subscriber: @johannes.wilde

I have the same problem in some scenes with latest builds of 2.92 and 2.93. On latest 2.91 however everything works fine

PopOS 20.10

I have the same problem in some scenes with latest builds of 2.92 and 2.93. On latest 2.91 however everything works fine PopOS 20.10

In #85244#1114686, @johannes.wilde wrote:
I have the same problem in some scenes with latest builds of 2.92 and 2.93. On latest 2.91 however everything works fine

PopOS 20.10

With the latest Builds and resetting to Factory Defaults it works for me now.

> In #85244#1114686, @johannes.wilde wrote: > I have the same problem in some scenes with latest builds of 2.92 and 2.93. On latest 2.91 however everything works fine > > PopOS 20.10 With the latest Builds and resetting to Factory Defaults it works for me now.

Added subscriber: @slowburn

Added subscriber: @slowburn

Looks like this is caused by a corrupted userpref.blend file in *AppData\Roaming\Blender Foundation\Blender\2.93\config*. Doing a factory reset fixes the issue but after a few days it appeared again for me, so it would be great to have a proper fix, because resetting and reconfiguring everything from scratch is quite a lot of work. Wouldn't want to do it every time. Please look into the file, maybe you'll find the cause of this bug. Note that simply opening this file doesn't cause setting to lock up, you have to put it into *Blender\2.xx\config* directory. Another strange thing is that Blender 2.91 seems immune to this bug. If I replace the original userpref file in 2.91 directory with corrupted one, the Lock Interface setting doesn't get stuck, whereas for 2.92 and 2.93 it does.
userpref(corrupted).blend

Looks like this is caused by a corrupted userpref.blend file in *AppData\Roaming\Blender Foundation\Blender\2.93\config\*. Doing a factory reset fixes the issue but after a few days it appeared again for me, so it would be great to have a proper fix, because resetting and reconfiguring everything from scratch is quite a lot of work. Wouldn't want to do it every time. Please look into the file, maybe you'll find the cause of this bug. Note that simply opening this file doesn't cause setting to lock up, you have to put it into *Blender\2.xx\config\* directory. Another strange thing is that Blender 2.91 seems immune to this bug. If I replace the original userpref file in 2.91 directory with corrupted one, the Lock Interface setting doesn't get stuck, whereas for 2.92 and 2.93 it does. [userpref(corrupted).blend](https://archive.blender.org/developer/F9889055/userpref_corrupted_.blend)
Member

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

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

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

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

Still cannot reproduce with the (corrupted?) userpref.blend [but of course I dont have all the Addons installed that the userpref wants to load...]

Could you check one more time:

thx in advance.

Still cannot reproduce with the (corrupted?) userpref.blend [but of course I dont have all the Addons installed that the userpref wants to load...] Could you check one more time: - if this can be reproduced in a fresh 3.0 build from https://builder.blender.org/download/daily/ for you? - if so, please try enabling your Addons one-by-one and check if any of them might be the culprit here. thx in advance.

No, I cannot reproduce this issue with 3.0 build. But recently I had a similar problem where Lock Interface would turn on whenever I did a render. I could still uncheck it, but it was really annoying to toggle it all the time. So I deleted 3.0 folder in AppData to get a fresh start, therefore I don't have all add-ons installed. I'll try to reinstall them gradually and watch if Lock Interface starts acting up again.

No, I cannot reproduce this issue with 3.0 build. But recently I had a similar problem where Lock Interface would turn on whenever I did a render. I could still uncheck it, but it was really annoying to toggle it all the time. So I deleted 3.0 folder in AppData to get a fresh start, therefore I don't have all add-ons installed. I'll try to reinstall them gradually and watch if Lock Interface starts acting up again.

Added subscriber: @PMA33

Added subscriber: @PMA33

Hello, I have had the same issue here (3 Alpha), reverting to default interface solved the problem, but ... I have already reset the interface to default some days ago (for a crashing problem #91676) so the issue should not have appeared in my case.
I saw the same problem on 2.93, restoring the default interface once again solved it and restoring the saved preferences restored also the issue... you can see that on this poor video, preference windows is not visible, I am loading the default preferences and then my custom one 2021-09-26 12-32-54.mkv.
I reinstalled all the add-ons I use without problem for the moment.

Hello, I have had the same issue here (3 Alpha), reverting to default interface solved the problem, but ... I have already reset the interface to default some days ago (for a crashing problem #91676) so the issue should not have appeared in my case. I saw the same problem on 2.93, restoring the default interface once again solved it and restoring the saved preferences restored also the issue... you can see that on this poor video, preference windows is not visible, I am loading the default preferences and then my custom one [2021-09-26 12-32-54.mkv](https://archive.blender.org/developer/F10607458/2021-09-26_12-32-54.mkv). I reinstalled all the add-ons I use without problem for the moment.

Hi, may be something interesting here 2021-09-26 18-50-44.mkv
The lodify add-on seem to be the culprit ...

Updating the add-on solve the problem, for me.

heu .... not totally, the locking option is re-checked after each render .... and stay in its last state when the add-on is disabled....

After some research this issue was described in Github but there is few information about its resolution ...

Hi, may be something interesting here [2021-09-26 18-50-44.mkv](https://archive.blender.org/developer/F10613201/2021-09-26_18-50-44.mkv) The lodify add-on seem to be the culprit ... Updating the add-on solve the problem, for me. heu .... not totally, the locking option is re-checked after each render .... and stay in its last state when the add-on is disabled.... After some research this issue was described in Github but there is few information about its resolution ...
Member

For reference, the github issue is https://github.com/DB3D/Lodify/issues/1

Can everyone confirm this is the culprit?

For reference, the github issue is https://github.com/DB3D/Lodify/issues/1 Can everyone confirm this is the culprit?
Author

Can confirm! Turning off Lodify just solved the issue for me.

Can confirm! Turning off Lodify just solved the issue for me.

Yea, for me as well. Although I could only reproduce the issue in 3.0 if I loaded earlier userpref file that was corrupted. So just enabling the addon might not cause the problem right away, making it harder to detect.

Yea, for me as well. Although I could only reproduce the issue in 3.0 if I loaded earlier userpref file that was corrupted. So just enabling the addon might not cause the problem right away, making it harder to detect.
Member

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

Changed status from 'Needs User Info' to: 'Archived'
Member

Dont have the Addon installed, but apparently LODify needs this to be ON
https://github.com/DB3D/Lodify/blob/master/Lodify.py#L1058

  • Locking the interface on render is mandatory, as cycles don't like mesh data exchange while
    calculating (cause instant-crash).

There is a setting for this "mandatory interface render lock", you might be able to turn this OFF? (and only turn it ON when realy using the LODify features?)

In any case, this is something that is caused by an external Addon, nothing to be done from the Blender side.
Will close, thx reporting (and investigating!) everyone.

Dont have the Addon installed, but apparently LODify needs this to be ON https://github.com/DB3D/Lodify/blob/master/Lodify.py#L1058 > - Locking the interface on render is mandatory, as cycles don't like mesh data exchange while > calculating (cause instant-crash). There is a setting for this "mandatory interface render lock", you might be able to turn this OFF? (and only turn it ON when realy using the LODify features?) In any case, this is something that is caused by an external Addon, nothing to be done from the Blender side. Will close, thx reporting (and investigating!) everyone.

Added subscriber: @dodododorian

Added subscriber: @dodododorian

Hello I'm the creator of Lodify
I'm sorry for the trouble caused here

It is clearly stated in the documentation (devtalk) of this plugin that the locking interface toggle is mandatory in order to work, this plugin will change the mesh data while cycles might be calculating, and that can/will cause crashes.

"render.interface_lock will be enabled with this addon, this can be disable in the options (but expect some crashes if removed)"

This shall be fixed once lodify will do the mesh data switching with the help of Geometry node

Hello I'm the creator of Lodify I'm sorry for the trouble caused here It is clearly stated in the documentation (devtalk) of this plugin that the locking interface toggle is mandatory in order to work, this plugin will change the mesh data while cycles might be calculating, and that can/will cause crashes. "*render.interface_lock will be enabled with this addon, this can be disable in the options (but expect some crashes if removed)*" This shall be fixed once lodify will do the mesh data switching with the help of Geometry node

It's okay, man. You were trying to solve a problem that shouldn't be there in the first place, we appreciate the effort.
Although that warning was really easy to miss amongst all the text. It would be best to also add a warning to the addon description inside of blender for things like that.

It's okay, man. You were trying to solve a problem that shouldn't be there in the first place, we appreciate the effort. Although that warning was really easy to miss amongst all the text. It would be best to also add a warning to the addon description inside of blender for things like that.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#85244
No description provided.