Page MenuHome

Adjust Last Operation panel is grayed out
Confirmed, NormalPublic

Description

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: rBc6cda3c09cd0
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:

Exact steps for others to reproduce the error

  1. Open file.
  2. Move vertices or do some action, so you can open Adjust Last Operation panel
  3. Open Adjust Last Operation panel
  4. Click on arrow to change numerical value

All fields are grayed out until cursor leaves "hot area"

Event Timeline

YAFU (YAFU) updated the task description. (Show Details)Sun, May 10, 4:57 PM
YAFU (YAFU) updated the task description. (Show Details)

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.

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.

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.

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:

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

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 (ISS) renamed this task from Sometimes Operator Menu becomes unresponsive to Adjust Last Operation panel is grayed out.Mon, May 11, 2:39 PM
Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.
Richard Antalik (ISS) updated the task description. (Show Details)

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.

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 (jbakker) This seems like it's verging on a "Known Issue," would you agree?