Adjust Last Operation panel is grayed out #76618

Open
opened 2020-05-10 16:54:05 +02:00 by YAFU · 15 comments

System Information
Operating system: Linux-5.4.0-14-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-07 21:33, hash: c6cda3c09c
Broken in all 2.8x too

Short description of error
The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur.

Here a video with an example with Smooth Vertices, but the problem can occur with any action showing operator panel:
operator_bug.mp4

Exact steps for others to reproduce the error
bug_operator.blend

  • Open file.
  • Move vertices or do some action, so you can open Adjust Last Operation panel
  • Open Adjust Last Operation panel
  • Click on arrow to change numerical value
    All fields are grayed out until cursor leaves "hot area"
**System Information** Operating system: Linux-5.4.0-14-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-07 21:33, hash: `c6cda3c09c` Broken in all 2.8x too **Short description of error** The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur. Here a video with an example with Smooth Vertices, but the problem can occur with any action showing operator panel: [operator_bug.mp4](https://archive.blender.org/developer/F8526371/operator_bug.mp4) **Exact steps for others to reproduce the error** [bug_operator.blend](https://archive.blender.org/developer/F8526372/bug_operator.blend) - Open file. - Move vertices or do some action, so you can open Adjust Last Operation panel - Open Adjust Last Operation panel - Click on arrow to change numerical value All fields are grayed out until cursor leaves "hot area"
Author

Added subscriber: @YAFU

Added subscriber: @YAFU
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

I tested on my system. POP!_OS 20.04 (Ubuntu 20.04 based distribution) with a GTX 1050ti driver 440.82. Here's what I've found:
The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur.

So for the developers, here's the exact sets to reproduce:

  1. Start Blender with default settings.
  2. Open a compositing window along side your 3D viewport and enable "Use nodes".
  3. Make an adjustment to any object in the 3D viewport.
  4. Interact with the "Last Operator" panel in the 3D viewport.
  5. The "Last Operator" panel will now appear grayed out and you will be unable to interact with it until you move your mouse off of the panel and back onto it.
  6. If you then disable "Use nodes" in the compositor or close the compositor window, the "Last Operator" panel will operate as expected.
I tested on my system. POP!_OS 20.04 (Ubuntu 20.04 based distribution) with a GTX 1050ti driver 440.82. Here's what I've found: The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur. So for the developers, here's the exact sets to reproduce: 1. Start Blender with default settings. 2. Open a compositing window along side your 3D viewport and enable "Use nodes". 3. Make an adjustment to any object in the 3D viewport. 4. Interact with the "Last Operator" panel in the 3D viewport. 5. The "Last Operator" panel will now appear grayed out and you will be unable to interact with it until you move your mouse off of the panel and back onto it. 6. If you then disable "Use nodes" in the compositor or close the compositor window, the "Last Operator" panel will operate as expected.
Author

Oh, it was that. Thank you!
The strangest thing is that this occurs from 2.80 inclusive. I was almost certain that this could be due to a problem with KDE compositor because apparently this had not been reported and I was the only one having the problem in so long.

Oh, it was that. Thank you! The strangest thing is that this occurs from 2.80 inclusive. I was almost certain that this could be due to a problem with KDE compositor because apparently this had not been reported and I was the only one having the problem in so long.
Member

It's not KDE. I'm using Gnome.
It is also a kind of edge case which is why it probably hasn't been reported.

It's not KDE. I'm using Gnome. It is also a kind of edge case which is why it probably hasn't been reported.
Author

Wait. Under the same circumstances with compositor and with "Use nodes" enabled, the problem also occurs in Blender 2.7x, but only in Operator in Tool Shelf panel, not in F6 operator. Open in 2.7x:
bug_operator_2.7x.blend


The question is I don't recall having the problem. Maybe nvidia driver is also involved? Currently using 440.64 version.

Wait. Under the same circumstances with compositor and with "Use nodes" enabled, the problem also occurs in Blender 2.7x, but only in Operator in Tool Shelf panel, not in F6 operator. Open in 2.7x: [bug_operator_2.7x.blend](https://archive.blender.org/developer/F8526958/bug_operator_2.7x.blend) ``` ``` The question is I don't recall having the problem. Maybe nvidia driver is also involved? Currently using 440.64 version.

Added subscriber: @iss

Added subscriber: @iss

In #76618#928335, @Alaska wrote:
I tested on my system. POP!_OS 20.04 (Ubuntu 20.04 based distribution) with a GTX 1050ti driver 440.82. Here's what I've found:
The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur.

So for the developers, here's the exact sets to reproduce:

  1. Start Blender with default settings.
  2. Open a compositing window along side your 3D viewport and enable "Use nodes".
  3. Make an adjustment to any object in the 3D viewport.

This seems to be more specific. Possibly only changes in edit mode?

In any case I think I can confirm this with this info

Edit: it looks like you have to click on arrow to change value to cause this

> In #76618#928335, @Alaska wrote: > I tested on my system. POP!_OS 20.04 (Ubuntu 20.04 based distribution) with a GTX 1050ti driver 440.82. Here's what I've found: > The last operator panel only grays out if the compositor tab is open and "use nodes" is enabled. If you close the window for the compositor or turn off "Use nodes", the issue doesn't occur. > > So for the developers, here's the exact sets to reproduce: > 1. Start Blender with default settings. > 2. Open a compositing window along side your 3D viewport and enable "Use nodes". > 3. Make an adjustment to any object in the 3D viewport. This seems to be more specific. Possibly only changes in edit mode? In any case I think I can confirm this with this info Edit: it looks like you have to click on arrow to change value to cause this
Richard Antalik changed title from Sometimes Operator Menu becomes unresponsive to Adjust Last Operation panel is grayed out 2020-05-11 14:39:35 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Another strange problem: If the redo panel is already active and you turn "Use Nodes" on, then adjusting any of the properties in the redo panel will turn "Use Nodes" off.

Another strange problem: If the redo panel is already active and you turn "Use Nodes" on, then adjusting any of the properties in the redo panel will turn "Use Nodes" off.
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

The problem happens because the redo panel is set to disable when there's a job running, and the compositor job runs for every 3D viewport change. I'm not sure what the right solution is.

Not starting the compositor job if there's nothing to update would probably be the best way to solve this, but that seems fairly involved.

@Jeroen-Bakker This seems like it's verging on a "Known Issue," would you agree?

The problem happens because the redo panel is set to disable when there's a job running, and the compositor job runs for every 3D viewport change. I'm not sure what the right solution is. Not starting the compositor job if there's nothing to update would probably be the best way to solve this, but that seems fairly involved. @Jeroen-Bakker This seems like it's verging on a "Known Issue," would you agree?

This is still happening by the way, 3 years later on 3.6.3.
Really glad this was the first result on google because already had another crazy bug today with autosaves.

This is still happening by the way, 3 years later on 3.6.3. Really glad this was the first result on google because already had another crazy bug today with autosaves.

it still happen in blender 4.0.2, here how i fix it, pick any object, enter edit mode, add a cude, the panel appear work well, exit edit mode, everything back to normal

it still happen in blender 4.0.2, here how i fix it, pick any object, enter edit mode, add a cude, the panel appear work well, exit edit mode, everything back to normal
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
6 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#76618
No description provided.