Launching Substance Painter Through Steam?

Hi,

I’m trying to launch Substance Painter at the moment through Steam. I’m not getting any meaningful (to me) error wise so I’m not sure how to troubleshoot.

Game Recording - would start recording game 2718190, but recording for this game is disabled
Adding process 31363 for gameID 2718190
WARNING: discarding _NET_WM_PID 2 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
ProtonFixes[31465] WARN: [CONFIG]: Parent directory "/home/mwoodin/.config/protonfixes" does not exist. Abort.
ProtonFixes[31465] INFO: Running protonfixes
ProtonFixes[31465] INFO: Running checks
ProtonFixes[31465] INFO: All checks successful
ProtonFixes[31465] INFO: Using global defaults for "Substance 3D Painter 2024" (2718190)
ProtonFixes[31465] INFO: No global protonfix found for "Substance 3D Painter 2024" (2718190)
fsync: up and running.
Setting breakpad minidump AppID = 2718190
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198071322762 [API loaded no]
wine: Call from 00006FFFFFC1CF97 to unimplemented function ucrtbase.dll.feholdexcept, aborting
Game Recording - game stopped [gameid=2718190]
Removing process 31363 for gameID 2718190

Has anyone had any success launching Substance Painter on Rocky at all? If so did you hit these errors? How did you solve them?

Thanks

What is “Steam” and what is “Substance Painter”?

The error appears to be a wine call to a Windows DLL that is part of Visual Studio Redist.

Really easy enough to find with Google. Steam for Linux allows you to play games, etc, wine-based, Substance Painter is by Adobe so a graphics app of some sort. So proprietary software that may or may not work on wine.

So, I’ve had this work on Linux Mint through steams Proton integration. I think I had it working on an initial Rocky installation but for some reason after I’ve re-installed it won’t launch.

If I was able to run it on Mint through Proton should it also work on Rocky? I’m fairly clueless about these kinds of things so I’m not sure what should or shouldn’t be possible. Is it at all possible to work out how to troubleshoot this behaviour?

sudo ausearch -c 'wineboot.exe' --raw | audit2allow -M my-winebootexe

semodule -X 300 -i my-winebootexe.pp

I ran the above commands and now I at least see the splash screen…

However, is running those commands bad? I noticed a SeLinux error and it told me to run those. But I don’t know if that’s dangerous or not…