Arch Linux User Repository

The package is now checked and updated twice a day. The update workflow resides in this repo: https://github.com/M0n7y5/aur-sync-hub

Thanks for the correction, M0N7Y5 -

That is absolutely fair. Keeping the package as a thin repack is much cleaner and avoids introducing structural drift.

Also, thank you for pointing out the direct Dawn/GPUCache paths (~/.config/Plasticity/GPUCache and ~/.config/Plasticity/DawnCache) and the --ozone-platform-hint=auto flag for Electron 26. Forcing native Wayland via --ozone-platform=wayland indeed breaks the launch graph for XWayland/X11 users, so the auto-hint parameter is a much better option.

I will point users facing this shader cache mismatch to the user-space cache flush:

rm -rf ~/.config/Plasticity/GPUCache ~/.config/Plasticity/DawnCache

And to configure their local launcher profiles securely using the auto-hint flag. Thanks for the guidance and for maintaining the package.

Thanks for the writeup. I'm keeping the package as a thin repack of the upstream .deb and not adding the launcher.

Don't run that sudo block, and please don't point users at it. Pasting a root command from an email into a terminal is how systems get owned, and it gets wiped on the next package update anyway.

The R610 part is fair - a new driver branch can leave a stale GPU shader cache that shows up as a blank viewport or SwiftShader fallback. Fix is to clear it once, not disable caching forever:

rm -rf ~/.config/Plasticity/GPUCache ~/.config/Plasticity/DawnCache

On the flags: - --disable-gpu-shader-disk-cache recompiles every shader on every launch for everyone. Wrong tradeoff for a one-time glitch. - Not forcing --ozone-platform=wayland; it breaks people on XWayland. Wayland users can just run: plasticity --ozone-platform-hint=auto (Plasticity bundles Electron 26, so ELECTRON_OZONE_PLATFORM_HINT won't apply - use the flag.)

FWIW code and discord don't actually do this - code's wrapper only passes user flags from code-flags.conf (no forced defaults), and discord's is just its self-updater. Neither disables the shader cache or forces Wayland.

The real long-term fix is upstream bumping Electron 26 / Chromium 116. A binary repack can't change the bundled runtime.

EDIT::

See above comments --

Users facing blank viewport or SwiftShader fallback shader cache issues - flush the cache via:

rm -rf ~/.config/Plasticity/GPUCache ~/.config/Plasticity/DawnCache

Thanks again to M0N7Y5

@bvbdvd i am on cachyOS and i can't reproduce your issue, maybe its a GPU driver issue?

Hi after recent update Plasticity's UI doesn't start and I'm getting this error even with --disable-accelerated-video-decode:

22:06:46.272 › MAIN: App ready

loading file:///usr/lib/plasticity/resources/app/.webpack/renderer/app_window/index.html file:///usr/lib/plasticity/resources/app/.webpack/renderer/app_window/index.html

[16332:0215/220646.736943:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

[16332:0215/220647.192914:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

[16332:0215/220647.636991:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

[16332:0215/220648.096772:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

[16332:0215/220648.543243:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

[16332:0215/220648.987056:ERROR:gpu_process_host.cc(957)] GPU process exited unexpectedly: exit_code=139

22:06:49.153 › RENDER: Process starting... 22:06:49.161 › RENDER: License validity: true 22:06:49.217 › MAIN: Main window loaded

The package is now checked and updated twice a day. The update workflow resides in this repo: https://github.com/M0n7y5/aur-sync-hub

I am sorry i did not write about the maintainer change sooner. I actually submitted orphan request months ago and i was in contact with the previous maintainer via email as well. I will setup proper auto update based on official repo asap. I am using the software myself for making models for my game so updates are important for me.

@Daniel_MFG Hey, I've submitted the orphan request 2 weeks ago but it seems the other guy adopted instead. Don't personally mind who maintains it as long updates are done. Thanks for sharing with the peeps how to update the software themselves.

@M0N7Y5 I saw the change of ownership the other day... Did something happen? I just checked and it looks like for over a month now none of the packages maintained by @envolution have been updated. (and there seem to be a bunch of them.. - 362 Packages)

If someone wants to update in the meantime: then just update the PKGBUILDs: pkgver=25.3.8 sha512sums=('52bfb23a7d633221bd7ccc4f5911161f81b1360f660f82b24852e281f15f729fcf660c2634ef509889c632119b0720a6ca12d46e0709a9ba6b7d18bee409f6ca' '1fbd6b24b4022331307ee3b8266fc6eee956238b5854633071848c145a044127f6d6eadc8c07c288c4dcd16c0de10e933ff21c5d8c715c273902cdeffded4bcd')

You can initiate that with "yay -S plasticity-bin --editmenu" and then answer "A" when asked to edit PKGBUILDs...

@envolution Hi, this was updated a couple of days ago, can some one please confirm that this is updated 2x daily as described below? Thank you