SVM != OSL shaders #47323

Closed
opened 2016-02-04 12:25:58 +01:00 by kevin loddewykx · 12 comments

System Information
Windows 10 64 bit, Build 10586
Intel Core i7-4710MQ (Intel HD Graphics 4600)
GTX 880m 8gig VRAM

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Bug 1: Current master
Bug 2: Current master
Worked: (optional)
Bug 1: Don't know, oldest version I tested with was 2.74 and was broken.
Bug 2: 2.76b

Short description of error
Bug 1: The magic texture has no Fac when using OSL, but does work with SVM.
Error message in console when connecting a Fac output with a input of a another node:
"ERROR: ConnectShaders: "Fac" is not a parameter or global of layer "node_magic_texture_00000201AF660CB0" (shader "node_magic_texture")
ERROR: ConnectShaders: cannot connect a unknown (Fac) to a float (Val), invalid connection"
patch for Bug 1: patch.diff

Bug 2: The result of Fac by the Voronoi texture is different between OSL and SVM. Just connect a Voronoi Texture node with his Fac to a Diffuse Shader node and switch between OSL and SVM shading. Render results will be different. It occurs with both methods "Intensity" and "Cells"

Exact steps for others to reproduce the error
See above

**System Information** Windows 10 64 bit, Build 10586 Intel Core i7-4710MQ (Intel HD Graphics 4600) GTX 880m 8gig VRAM **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Bug 1: Current master Bug 2: Current master Worked: (optional) Bug 1: Don't know, oldest version I tested with was 2.74 and was broken. Bug 2: 2.76b **Short description of error** Bug 1: The magic texture has no Fac when using OSL, but does work with SVM. Error message in console when connecting a Fac output with a input of a another node: "ERROR: ConnectShaders: "Fac" is not a parameter or global of layer "node_magic_texture_00000201AF660CB0" (shader "node_magic_texture") ERROR: ConnectShaders: cannot connect a unknown (Fac) to a float (Val), invalid connection" patch for Bug 1: [patch.diff](https://archive.blender.org/developer/F279937/patch.diff) Bug 2: The result of Fac by the Voronoi texture is different between OSL and SVM. Just connect a Voronoi Texture node with his Fac to a Diffuse Shader node and switch between OSL and SVM shading. Render results will be different. It occurs with both methods "Intensity" and "Cells" **Exact steps for others to reproduce the error** See above

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @mageoftheforest

Added subscriber: @mageoftheforest

Current Master == 2.76.9 24eecb0

Current Master == 2.76.9 24eecb0
Thomas Dinges self-assigned this 2016-02-04 13:31:05 +01:00

This issue was referenced by f250aa9d86

This issue was referenced by f250aa9d86a35ae8bb6692a85ffe04610924fb08

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Thanks for the report, fixed the issue now. I could not see any render difference though.

Thanks for the report, fixed the issue now. I could not see any render difference though.

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

Bug 2 is indeed still present, was assuming this happens in Magic texture falsely. :/

Bug 2 is indeed still present, was assuming this happens in Magic texture falsely. :/

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

That’s an OSL bug according to http://lists.blender.org/pipermail/bf-committers/2016-February/046604.html

Closing as solved for now, we can always reopen should the bug persists after all platforms have been updated.

Also, @mageoftheforest please only report one issue per bug, otherwise it’s harder to track what’s actually fixed!

That’s an OSL bug according to http://lists.blender.org/pipermail/bf-committers/2016-February/046604.html Closing as solved for now, we can always reopen should the bug persists after all platforms have been updated. Also, @mageoftheforest please only report **one** issue per bug, otherwise it’s harder to track what’s actually fixed!

This issue was referenced by blender/cycles@05170d12d1

This issue was referenced by blender/cycles@05170d12d1e8e35ecd616ed09d356ceaa6ff2216
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#47323
No description provided.