Upgrading to the latest driver, 572.16, breaks support for AO baking in Substance Painter. Reverting back to 566.36 fixes the problem, and this behavior is 100% reproducible on multiple systems. This problem was reported to me by LevelCap when he was trying to bake on the 5090. However, in his case, he can’t revert drivers, so he’s stuck until this problem is addressed.
2 Likes
Hi @JohnLogostini, welcome to the forums and thank you for reporting this!
I opened a bug internally so that this can be addressed.
Can you maybe check if the newest hotfix driver by any chance fixes this already?
Thanks!
One more thing, which GPU did you use in your testing?
I was using a 3090 and LevelCap was using a 5090 same problem on both
Thanks!
So, if you add --force-optix to your launch arguments, the baking works once again. Adobe said this looks like you guys probably broke the DXR API with the latest driver. As a test, I tried baking in Painter 2020 and got the exact same output. Just to reiterate, adding --force-optix to the launch argument in Steam does function.
Painter 2020
Painter 2024 with OptiX
1 Like
Same exact baking issue here. I was going mad all day figuring out the issue, Finally I went back to Nov. 12th driver and that fixed it. I was using RTX 4060 laptop gpu. Hopefully the next new driver would fix this issue
How do you add the command in substance painter ?
In Steam, you can add it to the launch arguments for Creative Cloud. Though I have never tested this, you should be able to add it to the shortcut.
Steam
Creative Cloud
"C:\Program Files\ADOBE\Substance Painter\2025\SubstancePainter.exe" --force-optix
I don’t have Creative Cloud, but it would probably look something like that. You just need to verify that in your shortcut, the path is enclosed in quotes, then add --force-optix to the end.
1 Like
Hello John, did you try the latest studio driver as well ? Is this issue also happening in latest Studio driver ?
Yes both have the same problem
1 Like
@MarkusHoHo Any Updates? this is still a problem
Sorry, no definitive news yet. The issue has been reproduced, nothing more to announce.
I count that as an update thanks
1 Like
I hope Nvidia will release the update soon, I can’t even try the DLSS 4 (in KCD2) due to this issue because then I’ve to update the drivers to 572.16, It’s just so frustrating. Please fix it ASAP.
PS: My Nvidia app version is 11.0.2.312 and driver version is 566.36
If your looking to update you can uses the --force-optix workaround for the time being