DDS Normal maps not rendering for certain DDS versions #56248

Closed
opened 2018-08-06 01:06:06 +02:00 by Geoff Gerber · 5 comments

System Information
Win10, Nvidia 970

Blender Version
Broken: 2.79b (I haven't tested on previous versions, but this has been an issue I've run into for a while.)

Summary:
When using a normal map from some DDS files, Blender can display the image fine in UV/Image Editor, but when plugged into a normal map node, the normals don’t show. If you take that DDS file and open/resave in GIMP, the normals do show. If you take that DDS file and pack it into the project, the normals also work properly.

Steps to reproduce:

  • Extract the linked Blend file, which contains a simple cube and node layout.
  • Set the view port to rendered mode.
  • Attach the brick_a_ddn-gimp.ddsImage Texture node to the Separate RGB node (DDS mixes up R and G for normals). The rendered image should show some nice pretty normals.
  • Attach the brick_a_ddn-orig.dds (ATI2 DDS File) Image Texture node to the Separate RGB node. The normals disappear, and you just see a flat surface on the cube.
  • Pack the brick_a_ddn-orig.dds into the project (UV/Image editor, open the brick_a_ddn-orig.dds file, and go Image -> Pack Image).
  • Refresh the viewport, and poof, you have normals again.

Also attached is a tif file converted from the orig DDS, which also works properly.

So while I have a workaround to get by this issue, it’s not ideal. I’m setting up a texture library, and don’t want to have to muddle with the original files to make them work properly. Nor do I want to pack all the images into the Blend file, since if I want to modify the textures in the future, it won’t apply to all the existing Blend files.

Blend file (zipped)

DDSIssue.zip

**System Information** Win10, Nvidia 970 **Blender Version** Broken: 2.79b (I haven't tested on previous versions, but this has been an issue I've run into for a while.) **Summary:** When using a normal map from some DDS files, Blender can display the image fine in UV/Image Editor, but when plugged into a normal map node, the normals don’t show. If you take that DDS file and open/resave in GIMP, the normals do show. If you take that DDS file and pack it into the project, the normals also work properly. **Steps to reproduce:** - Extract the linked Blend file, which contains a simple cube and node layout. - Set the view port to rendered mode. - Attach the brick_a_ddn-gimp.ddsImage Texture node to the Separate RGB node (DDS mixes up R and G for normals). The rendered image should show some nice pretty normals. - Attach the brick_a_ddn-orig.dds (ATI2 DDS File) Image Texture node to the Separate RGB node. The normals disappear, and you just see a flat surface on the cube. - Pack the brick_a_ddn-orig.dds into the project (UV/Image editor, open the brick_a_ddn-orig.dds file, and go Image -> Pack Image). - Refresh the viewport, and poof, you have normals again. Also attached is a tif file converted from the orig DDS, which also works properly. So while I have a workaround to get by this issue, it’s not ideal. I’m setting up a texture library, and don’t want to have to muddle with the original files to make them work properly. Nor do I want to pack all the images into the Blend file, since if I want to modify the textures in the future, it won’t apply to all the existing Blend files. [Blend file (zipped) ](https://1drv.ms/u/s!Ahz_oM1_DqLRg7R3gjfm1FFAKunEFA) [DDSIssue.zip](https://archive.blender.org/developer/F4133316/DDSIssue.zip)
Author

Added subscriber: @Geoffrey-Gerber

Added subscriber: @Geoffrey-Gerber

Added subscribers: @brecht, @mont29

Added subscribers: @brecht, @mont29
Brecht Van Lommel was assigned by Bastien Montagne 2018-08-06 09:02:54 +02:00

That’s probably and OIIO library issue, @brecht?

That’s probably and OIIO library issue, @brecht?
Brecht Van Lommel was unassigned by Dalai Felinto 2019-12-23 16:36:03 +01:00

Added subscriber: @kosblend

Added subscriber: @kosblend
Philipp Oeser removed the
Interest
Render & Cycles
label 2023-02-09 13:58:13 +01:00
Aras Pranckevicius added
Status
Resolved
and removed
Status
Confirmed
labels 2023-08-17 10:34:08 +02:00

Should be working fine in Blender 3.6 and 4.0

Should be working fine in Blender 3.6 and 4.0
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#56248
No description provided.