Package Details: substance-designer 12.2.1-1

Git Clone URL: https://aur.archlinux.org/substance-designer.git (read-only, click to copy)
Package Base: substance-designer
Description: Node-based, non-destructive PBR material authoring tool.
Upstream URL: https://www.allegorithmic.com/products/substance-designer
Keywords: gamedev material pbr substance
Licenses: custom
Submitter: spacepluk
Maintainer: t-ask (lehthanis, Rain_Shinotsu)
Last Packager: Rain_Shinotsu
Votes: 10
Popularity: 0.000000
First Submitted: 2016-08-26 08:33 (UTC)
Last Updated: 2022-08-29 00:51 (UTC)

Pinned Comments

Rain_Shinotsu commented on 2022-09-28 19:58 (UTC) (edited on 2022-10-02 22:22 (UTC) by Rain_Shinotsu)

Hi everyone:

We're just a couple of days out from the closing of the substance3d site. From what I gather, that means it's the end of updates for this AUR package, unless there's a surprise build upstream before the end of the month.

If you wish to continue getting new versions of the Substance suite, I highly suggest picking it up on Steam, because that is the only place where Linux builds will be maintained anymore. You might want to wait until "Substance 3D Designer 2023" is available, though, as then you'll get more updates for your money.

In case, for whatever reason, anyone wants to continue using this (Allegorithmic) package, I'll see about finding a way for users to download the builds themselves after the site's closing (maybe archive.org would help?). I already downloaded every build for myself, so if all else fails, I could just re-upload individual builds on a case basis, but I can see that idea not being popular.

Also, quick reminder: download your license file! If you want to continue using this package after EOL, you'll need it to authenticate yourself. Log into the substance3d site and go to the "Licenses" tab to find it.

Update: Now that the Substance accounts are EOL, users can no longer access their accounts, but it's still possible to redownload your old perpetual license keys. Adobe explains how in their Substance account end-of-life FAQ. As for downloading packages, I have bad news and good news. Bad news: I don't think I'll be publishing the build archive I've been working on. Between redirecting users, potential licensing issues, and security implications, it's pretty much a logistical nightmare. Good news: The existing official download links still work, so people can continue downloading the builds as long as they have the links. (No guarantees these AUR packages will stay up forever, though, sorry.)

Latest Comments

1 2 3 4 Next › Last »

Rain_Shinotsu commented on 2022-09-28 19:58 (UTC) (edited on 2022-10-02 22:22 (UTC) by Rain_Shinotsu)

Hi everyone:

We're just a couple of days out from the closing of the substance3d site. From what I gather, that means it's the end of updates for this AUR package, unless there's a surprise build upstream before the end of the month.

If you wish to continue getting new versions of the Substance suite, I highly suggest picking it up on Steam, because that is the only place where Linux builds will be maintained anymore. You might want to wait until "Substance 3D Designer 2023" is available, though, as then you'll get more updates for your money.

In case, for whatever reason, anyone wants to continue using this (Allegorithmic) package, I'll see about finding a way for users to download the builds themselves after the site's closing (maybe archive.org would help?). I already downloaded every build for myself, so if all else fails, I could just re-upload individual builds on a case basis, but I can see that idea not being popular.

Also, quick reminder: download your license file! If you want to continue using this package after EOL, you'll need it to authenticate yourself. Log into the substance3d site and go to the "Licenses" tab to find it.

Update: Now that the Substance accounts are EOL, users can no longer access their accounts, but it's still possible to redownload your old perpetual license keys. Adobe explains how in their Substance account end-of-life FAQ. As for downloading packages, I have bad news and good news. Bad news: I don't think I'll be publishing the build archive I've been working on. Between redirecting users, potential licensing issues, and security implications, it's pretty much a logistical nightmare. Good news: The existing official download links still work, so people can continue downloading the builds as long as they have the links. (No guarantees these AUR packages will stay up forever, though, sorry.)

cerise commented on 2022-05-18 04:08 (UTC)

@Rain_Shinotsu cleanBuild and it's working, tysm!! <3

Rain_Shinotsu commented on 2022-05-18 02:11 (UTC) (edited on 2022-05-18 09:26 (UTC) by Rain_Shinotsu)

Whoops, I forgot to tweak the download link now that version 12 is out. Thanks for pointing it out! I probably wouldn't have caught it myself.

It should be fixed now, alongside substance-player; please try it again.

cerise commented on 2022-05-17 23:41 (UTC)

404 error for the new rpm link? Error details

Rain_Shinotsu commented on 2022-02-27 10:38 (UTC) (edited on 2022-02-28 10:40 (UTC) by Rain_Shinotsu)

Something about a recent OS update might have messed with the libcrypt library, because I recently tried opening Painter (7.4.1) and Designer (11.3.1) and neither even showed the splash screen. Rerunning them via terminal revealed that libcrypt.so.1 was missing.

You can confirm whether the file exists for you by opening a terminal in the /usr/lib folder and running ls -al libcrypt*; somewhere in the list should be libcrypt.so.1. If not, install the libxcrypt-compat package and it should be back on your system and Painter and Designer should work again.

Note that this was all done on EndeavourOS, so maybe it isn't an issue for Arch users. Even so, I added it as a dependency. Existing users should only have to install the new package, but new users will now have it bundled in when they install the software for the first time.

Rain_Shinotsu commented on 2021-12-24 18:37 (UTC) (edited on 2022-02-27 10:44 (UTC) by Rain_Shinotsu)

@t-ask Thanks for confirming it works for you. Also, we appreciate your continuing to maintain the package despite not having a license.

@dmitsuki Thanks to you too for sharing your fix. I installed progl and used it to launch Designer, and it started up fine for me too. I'll update my .desktop file to account for that. (I'll probably do the same for the other Substance apps for good measure.)

Maybe I should have thought to try the proprietary driver, considering that the documentation stated that Mesa drivers aren't supported. I was hesitant to install it (after all, it seemed the other apps worked without it), but I suppose proprietary drivers for proprietary software is par for the course.

dmitsuki commented on 2021-12-24 02:13 (UTC) (edited on 2021-12-24 02:27 (UTC) by dmitsuki)

It didn't work for me. I had to install progl and run it with the progl command. If using the steam version, you can use progl %command%

I'm on Arch, not Manjaro

Just opened Manjaro, it did indeed open with progl as well.

https://wiki.archlinux.org/title/AMDGPU_PRO

t-ask commented on 2021-12-22 12:51 (UTC) (edited on 2021-12-22 12:52 (UTC) by t-ask)

@Rain_Shinotsu Here (Arch Linux) it starts without issues. Material library renders fine. Although, I don't have the full license any more it starts without issues.

Rain_Shinotsu commented on 2021-12-21 23:46 (UTC) (edited on 2021-12-22 05:57 (UTC) by Rain_Shinotsu)

If I run the latest version (11.3.1), it crashes immediately and prompts me to send an error report. Running it from the terminal yields abort (core dumped) "/opt/Adobe/Adobe_Substance_3D_Designer/Adobe Substance 3D Designer" and exits. I haven't seen this issue in Painter (7.4.1) or Sampler (3.1.2). I sent a crash report to Adobe; I'll see if they get back to me on it.

(Note: this is on Manjaro, which I know isn't Arch, so maybe it works for Arch users?)

1 2 3 4 Next › Last »