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

AO baking error in substance painter

Community Beginner ,
Feb 04, 2025 Feb 04, 2025

Copy link to clipboard

Copied

I got an error when doing bake ambient occlusion.
the AO display looks inappropriate, with strange patterns, completely unable to detect the angles on my object. On all the 3D objects that I use, the results are the same.
Here I give an example of only using a cube because the results will be more certain, it is impossible to experience a wrong backface or UV. but the result is still like this.
AO.pngexpand imagewith AO.pngexpand image what do I have to do ? This bug occurred suddenly.

 

Bug Unresolved
TOPICS
Automatic UV unwrapping , Baking , Bugs & Crashes , Color Management , Discussion , UV Tiles

Views

2.0K

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 Correct answer

Adobe Employee , Feb 05, 2025 Feb 05, 2025

Hi,

 

Thank you for reporting.

 

Unfortunately, this is an issue we're facing with Nvidia latest driver.

 

  • You can try this fix, but from users feedback it doesn't work for everyone.
  • You can also try to disable the GPU Raytracing (Edit > Settings > General > Baking options > Enable GPU Raytracing) 
  • Utlimately, you can rollback to a previous driver version

 

For the information, we're currently in discussion with Nvidia to find a fix a soon as possible.

 

Best regards,

 

Votes

Translate

Translate
11 Comments
New Here ,
Feb 04, 2025 Feb 04, 2025

Copy link to clipboard

Copied

had the same issue, after I updated my GPU driver in the weekend
I was using the latest NVIDIA Studio Driver 572.16 reverted back to 566.36 - resolved for me, for now

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Feb 05, 2025 Feb 05, 2025

Copy link to clipboard

Copied

Hi,

 

Thank you for reporting.

 

Unfortunately, this is an issue we're facing with Nvidia latest driver.

 

  • You can try this fix, but from users feedback it doesn't work for everyone.
  • You can also try to disable the GPU Raytracing (Edit > Settings > General > Baking options > Enable GPU Raytracing) 
  • Utlimately, you can rollback to a previous driver version

 

For the information, we're currently in discussion with Nvidia to find a fix a soon as possible.

 

Best regards,

 

Cyril Dellenbach (Micro) | QA Support Artist | Adobe

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 13, 2025 Feb 13, 2025

Copy link to clipboard

Copied

The new NVidia driver released today, Feb. 13th, 2025, did not fix the issue.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 18, 2025 Feb 18, 2025

Copy link to clipboard

Copied

Facing de same issue, still not resolved in Nvidia 572.42 drivers published 13 feb 2025. I have an RTX 4070 Laptop GPU.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 23, 2025 Feb 23, 2025

Copy link to clipboard

Copied

adding --force-optix in the launch arguments solved the issue, but both studio and game drivers for nvidia still have this issue on Jan 30th. If anyone is trying to figure out how to add the launch arguments you can add non steam applications to steam and use the launch arguments in the properties. fixed it for me at least.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 24, 2025 Feb 24, 2025

Copy link to clipboard

Copied

I found that you can add the Low Poly mesh into the "High Poly parameters", and this fixes the issue on limited testing, as seen in the "blue" chair images

Votes

Translate

Translate

Report

Report
New Here ,
Feb 24, 2025 Feb 24, 2025

Copy link to clipboard

Copied

Screenshot 2025-02-24 123736.pngexpand image

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 25, 2025 Feb 25, 2025

Copy link to clipboard

Copied

No, setting it to Use Low Poly as High Poly does not fix it either. Tested on multiple models. So far the only fix is to roll back to the older driver.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 25, 2025 Feb 25, 2025

Copy link to clipboard

Copied

Not what I said, I did not use the "Use Low Poly Mesh as High Poly Mesh" checkbox, I added the Low Poly fbx mesh to the "High Definition Meshes" list. The same low poly mesh I am using for the project is being used again in the High Definition Meshes lister.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 25, 2025 Feb 25, 2025

Copy link to clipboard

Copied

Gotcha, yes that appears to work. Thank you. Shouldn't be necessary, but here we are.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 27, 2025 Feb 27, 2025

Copy link to clipboard

Copied

LATEST

The new driver published today, 27th feb, version 572.60 fix the issue ! 🙂

Votes

Translate

Translate

Report

Report
Resources