Bump mapping in cycles is not shown on the viewport when the material use node groups #48613

Closed
opened 2016-06-08 15:26:14 +02:00 by Matias Mendiola · 6 comments

Bump mapping in cycles is not shown on the viewport when the material use node groups

System Information:
Windows 10 64bit (SP 1) - NVIDIA GeForce GTX 560

Blender Version
2.77, branch: master, commit date: 2016-06-06 11:55, hash: fd7068e, type: Release

Short description of error
When displaying material shader in the viewport with Cycles the bump mapping is not shown if the material use node groups.

Exact steps for others to reproduce the error

  • Build a material that use an image texture conected to the displacement output that also use a node group
  • Apply the material to an object
  • Select material as viewport shading method
  • The material bump is not shown on the viewport

bump_mapping_viewport.JPG

bump_mapping_viewport_bug.blend

Bump mapping in cycles is not shown on the viewport when the material use node groups **System Information:** Windows 10 64bit (SP 1) - NVIDIA GeForce GTX 560 **Blender Version** 2.77, branch: master, commit date: 2016-06-06 11:55, hash: fd7068e, type: Release **Short description of error** When displaying material shader in the viewport with Cycles the bump mapping is not shown if the material use node groups. **Exact steps for others to reproduce the error** - Build a material that use an image texture conected to the displacement output that also use a node group - Apply the material to an object - Select material as viewport shading method - The material bump is not shown on the viewport ![bump_mapping_viewport.JPG](https://archive.blender.org/developer/F316450/bump_mapping_viewport.JPG) [bump_mapping_viewport_bug.blend](https://archive.blender.org/developer/F316449/bump_mapping_viewport_bug.blend)
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @mendio

Added subscriber: @mendio
Sergey Sharybin self-assigned this 2016-06-08 15:31:59 +02:00

This issue was referenced by 6d111a233c

This issue was referenced by 6d111a233cd65433564ffb106bb9e0c6f34939e8

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author
Member

The problem was resolved but now I found that Blender crash using node groups connected with displacement output in at least two situations

Situation 1:

  • Select material shader for the viewport
  • Make a material that use a node group with image texture inside and conected to the displacement output
  • Duplicate the node group (CTRL+D) -> Blender crash

Situation 2:

  • Make a new material
  • Add two diferent material output nodes
  • Add a node group with image texture inside
  • Connect the node group with one of the displacement output
  • Duplicate de node group (viewport in solid mode)
  • Select material shader for the viewport -> Blender crash

I've put these comment here because I think are related with the last fix, but maybe I should open a new bug report? just let me know

The problem was resolved but now I found that Blender crash using node groups connected with displacement output in at least two situations **Situation 1:** - Select **material shader** for the viewport - Make a material that use a node group with image texture inside and conected to the displacement output - Duplicate the node group (CTRL+D) -> Blender crash **Situation 2:** - Make a new material - Add two diferent material output nodes - Add a node group with image texture inside - Connect the node group with one of the displacement output - Duplicate de node group (viewport in solid mode) - Select material shader for the viewport -> Blender crash I've put these comment here because I think are related with the last fix, but maybe I should open a new bug report? just let me know

It's always a bad idea to start reporting multiple issues to the same report. Your thing is a new issue and to be handled separately.
Using same report for all related issues will quickly become difficult to manege.

That would help if you open a new report and put two .blend files prepared for the state of hitting Shift-D. I'll check it tomorrow.

It's always a bad idea to start reporting multiple issues to the same report. Your thing is a new issue and to be handled separately. Using same report for all related issues will quickly become difficult to manege. That would help if you open a new report and put two .blend files prepared for the state of hitting Shift-D. I'll check it tomorrow.
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#48613
No description provided.