FS#75133 - [superslicer] alpha version use stable config. May result in lost of config

Attached to Project: Community Packages
Opened by Lukas (Lukas1818) - Tuesday, 21 June 2022, 22:41 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 14 August 2022, 19:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The current Superslicer is an alpha version and use the stable config path. This may result in hours of fine-tuning of the printer profile being lost. The package should use the alpha directory `DSLIC3R_ALPHA=ON` or preferentially should be stable version.
Additional info:
* package version(s) 1:2.4.58.2-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Sunday, 14 August 2022, 19:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  1:2.4.58.4-1
Comment by Lukas (Lukas1818) - Sunday, 24 July 2022, 14:40 GMT
was fixed with 1:2.4.58.3-1 can be closed
Comment by Wilhelm Schuster (wlhlm) - Monday, 01 August 2022, 04:26 GMT
  • Field changed: Percent Complete (100% → 0%)
This does not appear to have been fixed: https://github.com/archlinux/svntogit-community/blob/0fc1dc8f98b0e2f931e7c8f7b147d6b2528fd880/trunk/PKGBUILD#L102
Comment by Lukas (Lukas1818) - Monday, 01 August 2022, 09:54 GMT
2.4.58.3 is as stable version. So super slicer stable use the stable config now.

Previously the package was an alpha version, witch does use the stable config.

So this issues was (unintentionally) fixed by the update to 2.4.58.3.
Comment by Wilhelm Schuster (wlhlm) - Monday, 01 August 2022, 11:12 GMT
I see. I was following the guidance in [1]:

> There shouldn't have much bugs left. Maybe some problems still with "avoid crossing perimeters". The stabl.e release is still the 2.3.57.12 [...]

Sorry for the noise then.

[1]: https://github.com/supermerill/SuperSlicer/releases/tag/2.4.58.3
Comment by Lukas (Lukas1818) - Monday, 01 August 2022, 11:30 GMT
It does look your are right and 2.3.57.12 is an alpha version and the github label is wrong, see https://github.com/supermerill/SuperSlicer/issues/2865.
Sorry for the confusion.

So this issue does still exist and the bug report should keep open.

So after the deletion of aur/superslicer-stable it is not possible anymore to install a stable version of superslicer?
Comment by Wilhelm Schuster (wlhlm) - Wednesday, 03 August 2022, 22:42 GMT
Which config path do the official builds (i.e. AppImage) for 2.4.58.3 use?
Comment by Lukas (Lukas1818) - Saturday, 06 August 2022, 16:17 GMT
> Which config path do the official builds (i.e. AppImage) for 2.4.58.3 use?

At my system the config is stored at `~/.config/SuperSlicer` for stable and `~/.config/SuperSlicer-alpha` for the alpha version.
This might be different at your system, dependent on your environment variables.

You can simple set the `DSLIC3R_ALPHA` cmakeflag to ON to use the official alpha path or to OFF for using the official stable path.
see https://github.com/archlinux/svntogit-community/blob/0fc1dc8f98b0e2f931e7c8f7b147d6b2528fd880/trunk/PKGBUILD#L106

At earlier version `~/.SuperSlicer` and `~/.slcir3++` were also used.

Loading...