Python expression window does not show image texture source image change operations #68054
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#68054
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Debian 10
Graphics card: Intel HD 4000
Blender Version
Broken: v 2.81 Alpha, Date 2019-07-30 20:50, Hash: 5359b7a03307 (latest daily linux 64-bit)
The scripting workspace Python expression output window does not display the executed Python expression when an image texture's input image is changed into another. That is, if two images are loaded in the image texture, opening the dropdown menu displaying available images and changing the image into another does not show the Python expression that can be used to complete the same task via the Python console.
On the other hand, if, for example, the default Principled BSDF shader's "distribution" field is changed from its dropdown menu, the following Python expression is printed:
Exact steps for others to reproduce the error
Added subscriber: @gekko
Added subscriber: @lichtwerk
Can confirm, #68053 is a bit related, will put on my desk for investigation...
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Generating the proper 'python path' is not always working, especially with ugly things like 'root' node trees of other IDs. Thanks for the report, but that's not considered a bug, although enhancements are possible here for sure.