Wrong API for activating Denoise_data pass with python #62610

Closed
opened 2019-03-15 12:59:26 +01:00 by Henri Hebeisen · 12 comments

System Information
Operating system: Windows 7
Graphics card: GTX Titan

Blender Version
Broken: blender-2.80-388ff003e28b-win64

Short description of error

I have to do a batch process on many blender files and I need to activate the denoising data in each viewlayer. When I manually activate the Denoising Data button, the python command is bpy.context.scene.denoising_store_passes = True . However it is impossible to retrieive this command from the python console as I get this error message :

Traceback (most recent call last):
  File "<blender_console>", line 1, in <module>
AttributeError: 'Scene' object has no attribute 'denoising_store_passes'

Also, as this is an option per View Layer, this command should be accessible from the same data like other passes, something like :

bpy.context.scene.view_layers["Perso"].use_denoising_data = True

Thanks a lot,

Henri

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 7 Graphics card: GTX Titan **Blender Version** Broken: blender-2.80-388ff003e28b-win64 **Short description of error** I have to do a batch process on many blender files and I need to activate the denoising data in each viewlayer. When I manually activate the Denoising Data button, the python command is bpy.context.scene.denoising_store_passes = True . However it is impossible to retrieive this command from the python console as I get this error message : ``` Traceback (most recent call last): File "<blender_console>", line 1, in <module> AttributeError: 'Scene' object has no attribute 'denoising_store_passes' ``` Also, as this is an option per View Layer, this command should be accessible from the same data like other passes, something like : ``` bpy.context.scene.view_layers["Perso"].use_denoising_data = True ``` Thanks a lot, Henri **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @HenriHebeisen

Added subscriber: @HenriHebeisen
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Shouldn't the command be bpy.context.view_layer.cycles.denoising_store_passes?

Shouldn't the command be `bpy.context.view_layer.cycles.denoising_store_passes`?
Author

Hello Jacques,

Thanks for your answer. You are right, it is the right command and it works !Thanks. However, the command displayed on screen is wrong :

bug_blender.jpg

Thanks a lot for your help.
Henri

Hello Jacques, Thanks for your answer. You are right, it is the right command and it works !Thanks. However, the command displayed on screen is wrong : ![bug_blender.jpg](https://archive.blender.org/developer/F6829837/bug_blender.jpg) Thanks a lot for your help. Henri
Member

Ah that's right.

Ah that's right.
Member

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Member

Did this ever work correctly?

I don't know how that path is computed, yet..

Did this ever work correctly? I don't know how that path is computed, yet..

Added subscriber: @brecht

Added subscriber: @brecht

I don't think it ever worked, see #25746 (Adding keyframes to nested custom properties (IDProperties) of a bone fails) and rna_path_from_ID_to_idpgroup.

To solve this we'd need to add an iterator over all ID props in an ID, or a much deeper design change.

I don't think it ever worked, see #25746 (Adding keyframes to nested custom properties (IDProperties) of a bone fails) and `rna_path_from_ID_to_idpgroup`. To solve this we'd need to add an iterator over all ID props in an ID, or a much deeper design change.
Member

Can we determine at runtime whether a certain path is correct or not? We should at least not show wrong data paths...

Can we determine at runtime whether a certain path is correct or not? We should at least not show wrong data paths...

Right, that should be possible. Not sure why it even finds a path now.

Right, that should be possible. Not sure why it even finds a path now.
Member

Closed as duplicate of #61525

Closed as duplicate of #61525
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
3 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#62610
No description provided.