Blender 2.9 external renderer shader node bug #80780

Closed
opened 2020-09-14 18:45:26 +02:00 by Nandeya charles · 27 comments

System Information
Operating system: windows 10 64 bit
Graphics card: RTX 2060 super

Blender Version
Broken: Blender 2.90 official / but it happen since a while now with older blender version
Worked: reported once here : https://developer.blender.org/T76381

Short description of error

Blender doesn't save animation keyframe input (color/Value ...) in shader node with luxcore render engine.
From the blendluxcore Devs it is a blender issue.

Exact steps for others to reproduce the error

1/ install luxcore render engine from here : https://luxcorerender.org/download/

2/ in blender switch to Luxcore engine

3/ add a shader matte (or any shader)

4/ animate any shader value of your choice.

**System Information** Operating system: windows 10 64 bit Graphics card: RTX 2060 super **Blender Version** Broken: Blender 2.90 official / but it happen since a while now with older blender version Worked: reported once here : https://developer.blender.org/T76381 **Short description of error** Blender doesn't save animation keyframe input (color/Value ...) in shader node with luxcore render engine. From the blendluxcore Devs it is a blender issue. Exact steps for others to reproduce the error 1/ install luxcore render engine from here : https://luxcorerender.org/download/ 2/ in blender switch to Luxcore engine 3/ add a shader matte (or any shader) 4/ animate any shader value of your choice.

Added subscriber: @sharlybg

Added subscriber: @sharlybg
Nandeya charles changed title from Blender 2.8 external renderer shader node bug to Blender 2.9 external renderer shader node bug 2020-09-14 18:45:38 +02:00

Added subscriber: @juang3d

Added subscriber: @juang3d

This is kind of super important for any third party render engine

This is kind of super important for any third party render engine

Added subscriber: @iss

Added subscriber: @iss

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

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

I can confirm, that preview is not updated when scrubbing timeline, Render is updated.

@sharlybg do you have link to ticket in luxcore bugtracker?

I can confirm, that preview is not updated when scrubbing timeline, Render is updated. @sharlybg do you have link to ticket in luxcore bugtracker?

As it is a blender bug i didn't open a bug issue on Luxcore bug tracker. But just in cases it is needed here is the link to the BlendLuxcore bug tracker : blendluxcore bug tracker

As it is a blender bug i didn't open a bug issue on Luxcore bug tracker. But just in cases it is needed here is the link to the BlendLuxcore bug tracker : [blendluxcore bug tracker ](https://github.com/LuxCoreRender/BlendLuxCore/issues)

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

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

In #80780#1017258, @sharlybg wrote:
As it is a blender bug i didn't open a bug issue on Luxcore bug tracker. But just in cases it is needed here is the link to the BlendLuxcore bug tracker : blendluxcore bug tracker

You said "From the blendluxcore Devs it is a blender issue." So I assumed you reported this and they said it's bug in Blender, I also confirmed this on that basis. It would definitely help if we knew why this is bugh in Blender.

Since I have not triaged this really, we need to have another look. But to triage this issue we need example file that demonstrates the bug. I would assume that the node or tree is not doing something sometimes, but I need to know that exactly. Having example file is best because both of us can test if things are working correctly.

Sorry if I misunderstand something.

> In #80780#1017258, @sharlybg wrote: > As it is a blender bug i didn't open a bug issue on Luxcore bug tracker. But just in cases it is needed here is the link to the BlendLuxcore bug tracker : [blendluxcore bug tracker ](https://github.com/LuxCoreRender/BlendLuxCore/issues) You said "From the blendluxcore Devs it is a blender issue." So I assumed you reported this and they said it's bug in Blender, I also confirmed this on that basis. It would definitely help if we knew why this is bugh in Blender. Since I have not triaged this really, we need to have another look. But to triage this issue we need example file that demonstrates the bug. I would assume that the node or tree is not doing something sometimes, but I need to know that exactly. Having example file is best because both of us can test if things are working correctly. Sorry if I misunderstand something.

Sorry for late reply. Here is the file :

Test blend.blend

Tried the file in Blender 2.83LTS + Blendluxcore 2.4 official and it work. But Blender 2.83LTS + Blendluxcore 2.5 don't.
will test blender 2.9 official + 2.5 and 2.4 blendluxcore.

Sorry for late reply. Here is the file : [Test blend.blend](https://archive.blender.org/developer/F8892650/Test_blend.blend) Tried the file in Blender 2.83LTS + Blendluxcore 2.4 official and it work. But Blender 2.83LTS + Blendluxcore 2.5 don't. will test blender 2.9 official + 2.5 and 2.4 blendluxcore.

Thanks for example file, but that is not quite what I meant. This would require us to work not only with Blendr code, but also with Luxcore's. We should not need to use Luxcore to demonstrate this bug if it is bug in Blender.

Thanks for example file, but that is not quite what I meant. This would require us to work not only with Blendr code, but also with Luxcore's. We should not need to use Luxcore to demonstrate this bug if it is bug in Blender.

Tested with Blender 2.9 + Blendluxcore 2.4 and it work.

Tested with Blender 2.9 + Blendluxcore 2.4 and it work.

Added subscriber: @BYOB

Added subscriber: @BYOB

@BYOB Hi, I don't know if you know about this issue, but since you are Luxcore dev can you share some information that can help us track and fix this?

@BYOB Hi, I don't know if you know about this issue, but since you are Luxcore dev can you share some information that can help us track and fix this?

With Blender 2.9 and latest BlendLuxCore v2.5 I can not reproduce the problem.

With Blender 2.9 and latest BlendLuxCore v2.5 I can not reproduce the problem.

Blender 2.9 and latest BlendLuxCore v2.5 same issue with two files :

Test blend.blend

XX0001-0100.avi

and this one

0001-0070.avi

#76381.blend

Blender 2.9 and latest BlendLuxCore v2.5 same issue with two files : [Test blend.blend](https://archive.blender.org/developer/F8894899/Test_blend.blend) [XX0001-0100.avi](https://archive.blender.org/developer/F8894898/XX0001-0100.avi) and this one [0001-0070.avi](https://archive.blender.org/developer/F8894906/0001-0070.avi) [#76381.blend](https://archive.blender.org/developer/F8894905/T76381.blend)

You should include a description what the actual bug is.
I thought the problem was that keyframes can't be set on properties of custom nodes, or don't show up in the UI.

However, the actual problem is that keyframes on custom node properties are either not evaluated or not updated when doing a final render of the full animation with Ctrl+F12. Rendering individual frames with F12 works as expected, and the keyframes show up in the UI as yellow/green on the node properties.

I can reproduce the issue with Blender 2.9 and BlendLuxCore v2.5 (have not tested other versions of either).

You should include a description what the actual bug is. I thought the problem was that keyframes can't be set on properties of custom nodes, or don't show up in the UI. However, the actual problem is that keyframes on custom node properties are either not evaluated or not updated *when doing a final render of the full animation with Ctrl+F12*. Rendering individual frames with F12 works as expected, and the keyframes show up in the UI as yellow/green on the node properties. I can reproduce the issue with Blender 2.9 and BlendLuxCore v2.5 (have not tested other versions of either).

I have put together a minimal script to show the issue without requiring the installation of the BlendLuxCore addon:

custom_node_props_test.zip

  • Open scene in Blender 2.9
  • Press "run script" in the text editor on the left
  • Hover the mouse over the float property of the node on the right, and set a keyframe with I
  • Advance 10 frames, change the value (e.g. to 20) and set another keyframe
  • Go back to frame 1, and again advance 10 frames. Check the console, it will show an output like this:
frame: 1
my_float_prop: 1.0
---
frame: 2
my_float_prop: 1.6515774726867676
---
frame: 3
my_float_prop: 3.3978052139282227
---
frame: 4
my_float_prop: 5.925926208496094
---
frame: 5
my_float_prop: 8.923182487487793
---
frame: 6
my_float_prop: 12.076818466186523
---
frame: 7
my_float_prop: 15.074075698852539
---
frame: 8
my_float_prop: 17.602191925048828
---
frame: 9
my_float_prop: 19.34842300415039
---
frame: 10
my_float_prop: 20.0
---
  • Render with Ctrl+F12
  • Check the console again, it will show an output like this:
Saved: 'C:\tmp\0001.png'
 Time: 00:00.41 (Saving: 00:00.00)

frame: 2
my_float_prop: 20.0
---
Saved: 'C:\tmp\0002.png'
 Time: 00:00.01 (Saving: 00:00.00)

frame: 3
my_float_prop: 20.0
---
Saved: 'C:\tmp\0003.png'
 Time: 00:00.01 (Saving: 00:00.00)

frame: 4
my_float_prop: 20.0
---
Saved: 'C:\tmp\0004.png'
 Time: 00:00.01 (Saving: 00:00.00)

frame: 5
my_float_prop: 20.0
---
Saved: 'C:\tmp\0005.png'
 Time: 00:00.01 (Saving: 00:00.00)

frame: 6
my_float_prop: 20.0
---
Saved: 'C:\tmp\0006.png'
 Time: 00:00.00 (Saving: 00:00.00)

frame: 7
my_float_prop: 20.0
---
Saved: 'C:\tmp\0007.png'
 Time: 00:00.00 (Saving: 00:00.00)

frame: 8
my_float_prop: 20.0
---
Saved: 'C:\tmp\0008.png'
 Time: 00:00.00 (Saving: 00:00.00)

frame: 9
my_float_prop: 20.0
---
Saved: 'C:\tmp\0009.png'
 Time: 00:00.01 (Saving: 00:00.00)

frame: 10
my_float_prop: 20.0
---
Saved: 'C:\tmp\0010.png'
 Time: 00:00.00 (Saving: 00:00.00)

frame: 10
my_float_prop: 20.0
---

So, in a frame_change_post handler, the custom property is animated correctly, but during final render animation it is not updated.

I have put together a minimal script to show the issue without requiring the installation of the BlendLuxCore addon: [custom_node_props_test.zip](https://archive.blender.org/developer/F8895289/custom_node_props_test.zip) * Open scene in Blender 2.9 * Press "run script" in the text editor on the left * Hover the mouse over the float property of the node on the right, and set a keyframe with I * Advance 10 frames, change the value (e.g. to 20) and set another keyframe * Go back to frame 1, and again advance 10 frames. Check the console, it will show an output like this: ``` frame: 1 my_float_prop: 1.0 --- frame: 2 my_float_prop: 1.6515774726867676 --- frame: 3 my_float_prop: 3.3978052139282227 --- frame: 4 my_float_prop: 5.925926208496094 --- frame: 5 my_float_prop: 8.923182487487793 --- frame: 6 my_float_prop: 12.076818466186523 --- frame: 7 my_float_prop: 15.074075698852539 --- frame: 8 my_float_prop: 17.602191925048828 --- frame: 9 my_float_prop: 19.34842300415039 --- frame: 10 my_float_prop: 20.0 --- ``` * Render with Ctrl+F12 * Check the console again, it will show an output like this: ``` Saved: 'C:\tmp\0001.png' Time: 00:00.41 (Saving: 00:00.00) frame: 2 my_float_prop: 20.0 --- Saved: 'C:\tmp\0002.png' Time: 00:00.01 (Saving: 00:00.00) frame: 3 my_float_prop: 20.0 --- Saved: 'C:\tmp\0003.png' Time: 00:00.01 (Saving: 00:00.00) frame: 4 my_float_prop: 20.0 --- Saved: 'C:\tmp\0004.png' Time: 00:00.01 (Saving: 00:00.00) frame: 5 my_float_prop: 20.0 --- Saved: 'C:\tmp\0005.png' Time: 00:00.01 (Saving: 00:00.00) frame: 6 my_float_prop: 20.0 --- Saved: 'C:\tmp\0006.png' Time: 00:00.00 (Saving: 00:00.00) frame: 7 my_float_prop: 20.0 --- Saved: 'C:\tmp\0007.png' Time: 00:00.00 (Saving: 00:00.00) frame: 8 my_float_prop: 20.0 --- Saved: 'C:\tmp\0008.png' Time: 00:00.00 (Saving: 00:00.00) frame: 9 my_float_prop: 20.0 --- Saved: 'C:\tmp\0009.png' Time: 00:00.01 (Saving: 00:00.00) frame: 10 my_float_prop: 20.0 --- Saved: 'C:\tmp\0010.png' Time: 00:00.00 (Saving: 00:00.00) frame: 10 my_float_prop: 20.0 --- ``` So, in a `frame_change_post` handler, the custom property is animated correctly, but during final render animation it is not updated.

Any update about this issue fix ?

Any update about this issue fix ?

@BYOB Thanks a lot for minimal example file. I checked this in 2.90 and I can confirm this issue, but I can't reproduce in latest 2.91.

@sharlybg can you download latest development build from https://builder.blender.org/download/ and check if problem is still there?

@BYOB Thanks a lot for minimal example file. I checked this in 2.90 and I can confirm this issue, but I can't reproduce in latest 2.91. @sharlybg can you download latest development build from https://builder.blender.org/download/ and check if problem is still there?
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Any update here, @sharlybg ?

Any update here, @sharlybg ?

Lastest 2.91 and luxcore give black screen in render viewport so it is impossible to test.

Lastest 2.91 and luxcore give black screen in render viewport so it is impossible to test.

Official 2.90.1 and blendluxcore 2.4 Work :

2.4.avi

Official 2.90.1 and blendluxcore 2.5 Don't Work in Final render : But strangelly work in viewport.

2.5.avi

Official 2.90.1 and blendluxcore 2.4 Work : [2.4.avi](https://archive.blender.org/developer/F8990695/2.4.avi) Official 2.90.1 and blendluxcore 2.5 **Don't** Work in Final render : **But strangelly work in viewport**. [2.5.avi](https://archive.blender.org/developer/F8990700/2.5.avi)
Member

Is it the same bug as #71908 (Keyframed parameters are not preserved when frame_change_post handler is used) ?

Is it the same bug as #71908 (Keyframed parameters are not preserved when frame_change_post handler is used) ?

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

Changed status from 'Needs User Info' to: 'Archived'
Richard Antalik self-assigned this 2020-10-15 18:54:31 +02:00

I with provided example script I still have no issues in 2.91. Also if the issue truly boils down to what is in provided example file, then it is not the same issue as #71908.

Since I can reproduce issue in 2.90 and not in 2.91 I will close this report now. If this bug can be reproduced in 2.91 please comment here or open new report.

I with provided example script I still have no issues in 2.91. Also if the issue truly boils down to what is in provided example file, then it is not the same issue as #71908. Since I can reproduce issue in 2.90 and not in 2.91 I will close this report now. If this bug can be reproduced in 2.91 please comment here or open new report.
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
5 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#80780
No description provided.