• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Packed maps are not displaying correctly in the 3D view as intended

Community Beginner ,
Nov 15, 2024 Nov 15, 2024

Copy link to clipboard

Copied

Issue: Packed maps are not displaying correctly in the 3D view as intended.

 

Details:
In my case:

  • ORM Map: R = AO, G = Roughness, B = Metallic
  • Normal + Height Map: RGB = Normal, A = Height (or RG = Normal, B = Height)

While the full texture is correctly applied to the corresponding material property, the specific channels (e.g., R, G, B, or A) defined in the Output node's "Usage" tags panel are not being used as configured. Instead, the entire texture appears to be applied indiscriminately.

 

Steps to Reproduce:

  1. Right-click in the node canvas and select "View Outputs in 3D View."
  2. Each output routes to the correct material parameter (e.g., AO, Roughness, Metallic), but the individual channels specified in the Output node's "Usage" tags panel are not isolated as expected.
  3. This can be observed in the accompanying screenshot.

 

Relevance: For game development, utilizing packed maps is a standard optimization technique to minimize texture memory usage. Accurate channel mapping from packed textures is crucial for this workflow to function as intended.


Images to support the above information below:

JeffSee_0-1731710024815.png

JeffSee_1-1731710293559.png

 

 

Idea Under review
TOPICS
3D View , Bugs & Crashes , Substance Graph

Views

142

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Dec 05, 2024 Dec 05, 2024

Hi @JeffSee,

 

Thank you for the message.

 

I've shared it with the rest of the team.

 

To be honest, this isn't one of our current priority, but a workaround would be to build your own custom Shader.

 

Best regards,

 

Status Under review

Votes

Translate

Translate
6 Comments
Community Beginner ,
Nov 15, 2024 Nov 15, 2024

Copy link to clipboard

Copied

How can I edit the subject to be, "Packed maps are not displaying correctly in the 3D view as intended"? The original subject is not as descriptive.

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 16, 2024 Nov 16, 2024

Copy link to clipboard

Copied

I've edited the title for you

Dave

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 16, 2024 Nov 16, 2024

Copy link to clipboard

Copied

Add the usual single channel outputs and use those for the 3D view.

Then add the packed outputs as additional outputs in whatever format works for your 3D game software

2024-11-16_12-29-56.jpg

 

When you export outputs you can choose which to export and turn off the unused single channel outputs in the export dialogue

2024-11-16_12-30-58.jpg

 

Dave

 

 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Dec 03, 2024 Dec 03, 2024

Copy link to clipboard

Copied

Thanks Dave,

 

I have been doing what you suggested for quite some time but it is not an optimal solution. Especially given that you provide the user this ability to set different outputs in the output nodes options. If you provide the end user the ability to specify multiple outputs with channel and data type selections, this should display as such in the 3D view and in the export dialog. There is just a lack of consistency from a UI/UX standpoint here that I would love to be taken into consideration for future releases of the software. Especially due to this being a common practice (packed maps) in both Games and Film now. Thank you for considering this a bug and feature request.

Votes

Translate

Translate

Report

Report
Community Expert ,
Dec 03, 2024 Dec 03, 2024

Copy link to clipboard

Copied

Just for clarity, I do not work for Adobe. I am an Adobe software user, like you.

I have tagged your post as an idea rather than a bug.

 

Dave

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 05, 2024 Dec 05, 2024

Copy link to clipboard

Copied

LATEST

Hi @JeffSee,

 

Thank you for the message.

 

I've shared it with the rest of the team.

 

To be honest, this isn't one of our current priority, but a workaround would be to build your own custom Shader.

 

Best regards,

 

Cyril Dellenbach (Micro) | QA Support Artist | Adobe
Status Under review

Votes

Translate

Translate

Report

Report