Object Info node random output always returns zero for lights with GPU render (Cycles) #57645

Closed
opened 2018-11-06 07:25:31 +01:00 by Alaska · 7 comments
Member

System Information:
CPU: Ryzen 5 2600
GPU: RX 570
OS: Windows 10 Homes

Blender Version:
Broken:
blender-2.79-1b974563b17 (2nd November 2018)
blender-2.80-b4dfe00fd60 (5th of November 2018)
Worked: In theory Blender 2.79b worked, but that's because Random dosn't output anything but zero on CPU or GPU.

Short description of error:
When a light object (Point, Spot, Sun, Hemi, Area) has a material that uses the Random output of the Object Info node, the output will always be zero if rendered using the GPU (Only tested on OpenCL).

Here's a few images:

  1. Node tree for lights
    Random Output.PNG
  2. CPU Render
    CPU.jpg
  3. GPU Render
    GPU.jpg
  4. CPU + GPU Rendering
    CPU+GPU.jpg
    Here's a file for Blender 2.8 to test it out yourself:
    Random returning zero.blend

Exact steps for others to reproduce the error:

  1. Start Blender
  2. Change the render engine to Cycles if it isn't already
  3. Create a light source and give it a node based "material"
  4. In the node editor for the light, add an object info node and attach the random out to something that controls the light (I used the Random output for the hue input in Hue Saturation Value node with a base of red to select the colour of the light)
  5. Duplicate the light source and place them around your scene so you have multiple randoms to compare
  6. Render the scene in the viewport with the CPU
  7. Render the scene in the viewport with the GPU and you'll find that the random output is always zero
**System Information:** CPU: Ryzen 5 2600 GPU: RX 570 OS: Windows 10 Homes **Blender Version:** **Broken:** blender-2.79-1b974563b17 (2nd November 2018) blender-2.80-b4dfe00fd60 (5th of November 2018) **Worked:** In theory Blender 2.79b worked, but that's because Random dosn't output anything but zero on CPU or GPU. **Short description of error:** When a light object (Point, Spot, Sun, Hemi, Area) has a material that uses the Random output of the Object Info node, the output will always be zero if rendered using the GPU (*Only tested on OpenCL*). Here's a few images: 1. Node tree for lights ![Random Output.PNG](https://archive.blender.org/developer/F5402803/Random_Output.PNG) 2. CPU Render ![CPU.jpg](https://archive.blender.org/developer/F5403121/CPU.jpg) 3. GPU Render ![GPU.jpg](https://archive.blender.org/developer/F5403122/GPU.jpg) 4. CPU + GPU Rendering ![CPU+GPU.jpg](https://archive.blender.org/developer/F5403129/CPU_GPU.jpg) Here's a file for Blender 2.8 to test it out yourself: [Random returning zero.blend](https://archive.blender.org/developer/F5403140/Random_returning_zero.blend) **Exact steps for others to reproduce the error:** 1. Start Blender 2. Change the render engine to Cycles if it isn't already 3. Create a light source and give it a node based "material" 4. In the node editor for the light, add an object info node and attach the random out to something that controls the light (*I used the Random output for the hue input in Hue Saturation Value node with a base of red to select the colour of the light*) 5. Duplicate the light source and place them around your scene so you have multiple randoms to compare 5. Render the scene in the viewport with the CPU 6. Render the scene in the viewport with the GPU and you'll find that the random output is always zero
Author
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
Brecht Van Lommel was assigned by Philipp Oeser 2018-11-06 13:27:49 +01:00
Member

Seems to be OpenCL only?
Cannot reproduce using CUDA on a 970m.

@brecht: mind having a look?

Seems to be OpenCL only? Cannot reproduce using CUDA on a 970m. @brecht: mind having a look?

Added subscriber: @ChristopherAnderssarian

Added subscriber: @ChristopherAnderssarian

I get the reported result.
Vega 64, Windows, Driver ver. 18.10.1

I get the reported result. Vega 64, Windows, Driver ver. 18.10.1

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Solved by a325bc6bf3.

Solved by a325bc6bf3.
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
4 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#57645
No description provided.