Normals corrupted (?) when packing external files #50280

Closed
opened 2016-12-20 16:26:45 +01:00 by Oliver Villar · 9 comments

System Information
Windows 10, 64bit
32GB RAM
nVidia GTX 980
Intel i7 3940k

Blender Version
Broken: 2.78a

Short description of error
When using the node group included in the .blend and packing external files, somehow the model or the textures/material/normals or something else get corrupted (affecting normals, especifically) and the only way to make it work again is appending the node group into a new .blend and load the textures again. Even in a new file, if textures are packed again, the problem also appears. I've noticed that it doesn't happen directly, only after saving and reloading the file. Attaching images with correct/incorrect result and .blend. (Looks like a problem with the normals, other textures look correct, but normals get messed up. Recalculating normals doesn't solve the problem).

Exact steps for others to reproduce the error

  1. Append the node group PBR_Hybrid (included in .blend file attached) in a new .blend file.
  2. Load some PBR textures (got mine from here: http://www.textures.com/download/substance0046/127949) and connect them to the node.
  3. Pack external files.
  4. Save the file.
  5. Close Blender.
  6. Open the saved file.

PBR.blend

Corrupted Result:
2016-12-20_15-43-08.jpg
Expected Result:
PBR_Suzzane.png

**System Information** Windows 10, 64bit 32GB RAM nVidia GTX 980 Intel i7 3940k **Blender Version** Broken: 2.78a **Short description of error** When using the node group included in the .blend and packing external files, somehow the model or the textures/material/normals or something else get corrupted (affecting normals, especifically) and the only way to make it work again is appending the node group into a new .blend and load the textures again. Even in a new file, if textures are packed again, the problem also appears. I've noticed that it doesn't happen directly, only after saving and reloading the file. Attaching images with correct/incorrect result and .blend. (Looks like a problem with the normals, other textures look correct, but normals get messed up. Recalculating normals doesn't solve the problem). **Exact steps for others to reproduce the error** 1) Append the node group PBR_Hybrid (included in .blend file attached) in a new .blend file. 2) Load some PBR textures (got mine from here: http://www.textures.com/download/substance0046/127949) and connect them to the node. 3) Pack external files. 4) Save the file. 5) Close Blender. 6) Open the saved file. [PBR.blend](https://archive.blender.org/developer/F420579/PBR.blend) Corrupted Result: ![2016-12-20_15-43-08.jpg](https://archive.blender.org/developer/F420590/2016-12-20_15-43-08.jpg) Expected Result: ![PBR_Suzzane.png](https://archive.blender.org/developer/F420592/PBR_Suzzane.png)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @OliverVillar

Added subscriber: @OliverVillar

Added subscriber: @Sergey

Added subscriber: @Sergey

What are the steps of reproducing the error with your .blend file? Opening it, unpacking files, re-opening and render gives exactly the same result as original file from you.

Also, it would help if you simplify shaders before submitting a bug report.

What are the steps of reproducing the error with your .blend file? Opening it, unpacking files, re-opening and render gives exactly the same result as original file from you. Also, it would help if you simplify shaders before submitting a bug report.
Author

The .blend file attached is the corrupted one (can't possibly pack the textures without corrupting it). To try it, follow the steps described in the report, first appending the PBR_Hybrid node group included in a new .blend.

I didn't modify the shader because I only experienced this problem with this particular combination of nodes, so I thought I'd keep it as is. However, it's most probably something with the normals, as disabling normal maps everything looks good (but again: the problem with the normals only happens after the external files have been packed, the file is saved, and the .blend is loaded again).

If you need a more thorough explanation I could record a video showcasing the problem so you can assess better what may be going on.

The .blend file attached is the corrupted one (can't possibly pack the textures without corrupting it). To try it, follow the steps described in the report, first appending the PBR_Hybrid node group included in a new .blend. I didn't modify the shader because I only experienced this problem with this particular combination of nodes, so I thought I'd keep it as is. However, it's most probably something with the normals, as disabling normal maps everything looks good (but again: the problem with the normals only happens after the external files have been packed, the file is saved, and the .blend is loaded again). If you need a more thorough explanation I could record a video showcasing the problem so you can assess better what may be going on.

The .blend file attached is the corrupted one (can't possibly pack the textures without corrupting it). To try it, follow the steps described in the report, first appending the PBR_Hybrid node group included in a new .blend.

You can use relative image path and pack everything to .zip archive.

I didn't modify the shader because I only experienced this problem with this particular combination of nodes, so I thought I'd keep it as is. However, it's most probably something with the normals, as disabling normal maps everything looks good (but again: the problem with the normals only happens after the external files have been packed, the file is saved, and the .blend is loaded again).

We need to minimize shader in order to troubleshoot it anyway. You have more or less clue how it works and can reproduce the error easily. It is just much more efficient if you minimize the shader rather than that will be doing 1.5 people who currently does the bug tracker.

Don't see how the normals could be a problem, they are generated from geometry and not stored in the file.

What is also unclear is what is the exact problem you're pointing by the images? The first image being less glossy? Or difference in the "dirt" islands?

If you need a more thorough explanation I could record a video showcasing the problem so you can assess better what may be going on.

Videos are useless, just provide very simple file which demonstrates the particular problem, without any other possible variables interfering the troubleshooting process.

> The .blend file attached is the corrupted one (can't possibly pack the textures without corrupting it). To try it, follow the steps described in the report, first appending the PBR_Hybrid node group included in a new .blend. You can use relative image path and pack everything to .zip archive. > I didn't modify the shader because I only experienced this problem with this particular combination of nodes, so I thought I'd keep it as is. However, it's most probably something with the normals, as disabling normal maps everything looks good (but again: the problem with the normals only happens after the external files have been packed, the file is saved, and the .blend is loaded again). We need to minimize shader in order to troubleshoot it anyway. You have more or less clue how it works and can reproduce the error easily. It is just much more efficient if you minimize the shader rather than that will be doing 1.5 people who currently does the bug tracker. Don't see how the normals could be a problem, they are generated from geometry and not stored in the file. What is also unclear is what is the exact problem you're pointing by the images? The first image being less glossy? Or difference in the "dirt" islands? > If you need a more thorough explanation I could record a video showcasing the problem so you can assess better what may be going on. Videos are useless, just provide very simple file which demonstrates the particular problem, without any other possible variables interfering the troubleshooting process.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Aaron Carlisle self-assigned this 2017-01-05 20:26:09 +01:00
Member

No news in over a week... closing

No news in over a week... closing
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#50280
No description provided.