Superslicer 2.5.59.2 Download !EXCLUSIVE!
Dulce Gleitz
Please do not add superslicer to stable branch of manjaro.
Superslicer was move from aur to community. But the current community version is an alpha version, witch dose use the stable config directory (see FS#75133). This may result in a damage config and hours of fine-
tuing are lost.
Because of this I think Supersilcer should only add to manjaro, if the arch package use a stable version.
Furthermore it has also an aur package as optional dependency. So when superslicer will be added to manjaro superslicer-profiles should also been added to manjaro.
When an AUR package is imported to the Arch community repo, it is deleted from the AUR. If Manjaro blacklisted superslicer, then it would not be available at all. There are pending deletion requests for the associated AUR packages.
Your superslicer settings are saved to flat files (at least on linux/macos, windows idk it could go to registry hell and don't care to know). Find those and check that the image file path is being saved to the config file.
The bed surface is an image (png), the bed model is an STL file. The STL could be maniuplated....in superslicer, actually, or in tinkercad. Then point to your modified STL.
The voron bed STL files actually come in very handy for modeling mods that need to fit the bed/bedframes.
I've been running superslicer nightlybuild localy to get the latest goodies, is there a way to choose a specific build (nightly/RC) somehow ? I'm not fluent with docker images and I don't know what to change for it to work
Cheers !