Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.4.0.17 No longer retains previously used Printer/Process preset #896

Closed
Ming-MCS opened this issue Dec 19, 2022 · 2 comments
Closed

v1.4.0.17 No longer retains previously used Printer/Process preset #896

Ming-MCS opened this issue Dec 19, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Ming-MCS
Copy link

Describe the bug
The new update of the slicer (1.4.0.17) no longer remembers the previously used presets in the Printer and Process categories which was present v1.3.1.1. Reopening the slicer now will switch the Printer preset to the system preset, instead of the one I had previously selected

To Reproduce
Steps to reproduce the behavior:

  1. Open the slicer
  2. Switch Printer/Process preset
  3. Do a print (or not)
  4. Exit application
  5. Reopen application

Expected behavior
In v1.3.1.1, whenever the presets were switched (I have custom presets made for both Printer, Filament, and Process categories) and the application was closed, reopening the application would retain the Printer and Process presets that were selected before closing (Filament does not do this, and it would be great if it did as well). This would mean that every time I exported from Fusion360 directly into the slicer, I would only need to change the filament type and send it off to print. In v1.4.0.17, The Printer preset is now automatically defaulted to the system preset, which in turn also resets the Process preset to the default system preset, meaning I would now need to switch the Printer, Filament, and Process presets to the desired one before printing

  • OS: Windows 10 22H2
  • Slicer: v1.4.0.17
@Ming-MCS Ming-MCS added the bug Something isn't working label Dec 19, 2022
@bambu123
Copy link
Collaborator

Please help to do these steps:

  1. Rename %APPDATA%\BambuStudio to BambuStudio1
  2. Open Bambu Studio (need re-login)
  3. Do something to see if this issue reproduce
  4. If it doesn't reproduce, please zip BambuStudio1 and send it to us (you can remove directory plugins to reduce package size)

@Ming-MCS
Copy link
Author

It's working now after renaming the folder and letting the slicer regenerate the configurations. Must've been some bloat in the configs from older versions of the slicer, but it's all good now.

Thanks

c2h5oh pushed a commit to c2h5oh/BambuStudio that referenced this issue May 31, 2023
Adds and corrects printer profiles for Qidi printers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants