search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.14k stars 2.07k forks source link

Profile is reverting to default #10664

Closed kanawati975 closed 2 years ago

kanawati975 commented 3 years ago

Application Version

4.12.0-Beta

Platform

Windows 10

Printer

Voron

Reproduction steps

Modified print settings as I wanted, and attempted to create a personalized profile with my settings.

Actual results

The changes are reverted and the profile got back to default settings and ignored all the changes I made. Also the save attempt is not visible, as if it's not saved at all.

Expected results

Like previous versions I expected to have my saved settings in the personalized profile

Checklist of files to include

Additional information & file uploads

cura.log

fvrmr commented 3 years ago

Hi @kanawati975 thank you for your report. Do you mean your profiles from previous Cura versions are not showing? Or creating a new profile (based on an other profile) in 4.12 beta?

kanawati975 commented 3 years ago

@fvrmr No. I wanted to create a new print Profile based on the "Fast" Preset with my own preferences. When I wanted to save it as new profile, all the changes I made has gone and everything was reverted to the preset. No old profiles were added/imported.

Ghostkeeper commented 2 years ago

These are the reproduction steps I'm executing:

  1. Add the Voron2 300 printer by VoronDesign.
  2. Close the machine settings dialogue.
  3. Change the infill density to 42%.
  4. Click on the profile drop-down (currently saying "Fast") and select "Create profile from current settings/overrides..."
  5. In the pop-up, give the new profile a name ("bla") and confirm.

Then I'm seeing the infill density at 42%, which is correct. The selected profile is "bla". The revert arrow at infill density disappeared.

Are you using a different printer from Voron?

One thing that could maybe be an issue is that I'm seeing errors from a Moonraker plug-in in your log. It could be that these errors are occurring when listening to a signal that the profile changed, which would interrupt other things listening to that signal like the updating of the settings list. But I'm only giving this a 10% chance of actually being the cause.

no-response[bot] commented 2 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.