Particle Info Node Does Not Consider Time Remapping #77307

Closed
opened 2020-06-03 15:14:33 +02:00 by Atomic · 10 comments

System Information
Operating system:version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 16:22, hash: 6f985574b7, type: Release
build date: 2020-05-08, 21:30:40
Graphics card: gtx660

Blender Version
Broken: (example: 2.80, edbf15d3c0, master, 2018-11-28, as found on the splash screen)
Worked: (newest version of Blender that worked as expected)

Short description of error
Particle Age Attribute Is Wrong When Time Is Remapped

Exact steps for others to reproduce the error
Open the attached file and activate Rendered viewport shading (Cycles).
Scrub the timeline and you'll see the the particles inherit colors based upon their age.
Press F12 and you will discover that all particles are rendered green. This is because the OLD field in the time remapping section is not equal to the NEW field.
If you set the NEW value equal to the OLD value, the colors render correctly.

The attributes presented by the particle info node should take into account the time remapping values.

OR

Better yet, why don't we have a Timeline info node that provides basic information about the start, end frame, fps and time remapping? If this node existed more complicated node graphs could be crafted.
Particles2 - Copy.blend

**System Information** Operating system:version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 16:22, hash: 6f985574b775, type: Release build date: 2020-05-08, 21:30:40 Graphics card: gtx660 **Blender Version** Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) Worked: (newest version of Blender that worked as expected) **Short description of error** Particle Age Attribute Is Wrong When Time Is Remapped **Exact steps for others to reproduce the error** Open the attached file and activate Rendered viewport shading (Cycles). Scrub the timeline and you'll see the the particles inherit colors based upon their age. Press F12 and you will discover that all particles are rendered green. This is because the OLD field in the time remapping section is not equal to the NEW field. If you set the NEW value equal to the OLD value, the colors render correctly. The attributes presented by the particle info node should take into account the time remapping values. OR Better yet, why don't we have a Timeline info node that provides basic information about the start, end frame, fps and time remapping? If this node existed more complicated node graphs could be crafted. [Particles2 - Copy.blend](https://archive.blender.org/developer/F8574196/Particles2_-_Copy.blend)
Author

Added subscriber: @AtomP

Added subscriber: @AtomP
Member

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

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

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

I tried looking into this a bit and noticed a couple of things:

  • rendering is wrong, yes
  • I think the remapping values are actually taken into account [if you have old<>new 100<>50, and compare scrubbing to 400 instead of 200 the results are actually the same]
  • however, there is something weird going on with updating here
  • when in the timeline scrubbing, pressing the mouse (not releasing!) somewhere in the timeline will most certainly yield to "wrong" (green -- same as rendering) results, yet when you release chances are good that result return back to the correct result.

This might help tracking down where the updates in the timeline as well as rendering might go wrong, needs further investigation...
note: change_frame_applyis done in both modal as well as confirming when scrubbing in the timeline

If this was just about particles, I would not hold my breath here [since particle nodes are around the corner], but this might also be an issue with setting CFRA (current frame) elsewhere?

I tried looking into this a bit and noticed a couple of things: - rendering is wrong, yes - I think the remapping values are actually taken into account [if you have old<>new 100<>50, and compare scrubbing to 400 instead of 200 the results are actually the same] - however, there is something weird going on with updating here - when in the timeline scrubbing, **pressing** the mouse (not releasing!) somewhere in the timeline will most certainly yield to "wrong" (green -- same as rendering) results, yet when you **release** chances are good that result return back to the correct result. This might help tracking down where the updates in the timeline as well as rendering might go wrong, needs further investigation... note: `change_frame_apply`is done in both modal as well as confirming when scrubbing in the timeline If this was just about particles, I would not hold my breath here [since particle nodes are around the corner], but this might also be an issue with setting `CFRA` (current frame) elsewhere?

Added subscriber: @Ifandbut

Added subscriber: @Ifandbut
when in the timeline scrubbing, pressing the mouse (not releasing!) somewhere in the timeline will most certainly yield to "wrong" (green -- same as rendering) results, yet when you release chances are good that result return back to the correct result.

Can confirm on Blender 2.83.

``` when in the timeline scrubbing, pressing the mouse (not releasing!) somewhere in the timeline will most certainly yield to "wrong" (green -- same as rendering) results, yet when you release chances are good that result return back to the correct result. ``` Can confirm on Blender 2.83.
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Just for quick reference, this is what is happening:

2020-06-18 13-01-10.mp4

Just for quick reference, this is what is happening: [2020-06-18 13-01-10.mp4](https://archive.blender.org/developer/F8630060/2020-06-18_13-01-10.mp4)

This issue was referenced by 23132fcdc1

This issue was referenced by 23132fcdc136d1238d9980c2a9bf6d058e846cc7

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Kévin Dietrich self-assigned this 2021-08-17 21:42:57 +02:00
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#77307
No description provided.