prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.76k stars 1.93k forks source link

Upgrade to 2.3 deleted my print settings, strange color change at first layer #5796

Closed lindbergalec closed 3 years ago

lindbergalec commented 3 years ago

Version

2.3

Operating system type + version

MacOS Catalina 10.15.7

3D printer brand / version + firmware version (if known)

Creality Ender 3 Pro

Behavior

Is this a new feature request? No

lukasmatena commented 3 years ago

What was the previous version of PrusaSlicer that you were using? Was it any of the 2.3 alphas/betas?

lindbergalec commented 3 years ago

Hi,

I believe so, looking at my downloads, I see a 2.3 version from April

On Sat, Jan 16, 2021 at 7:53 AM Lukáš Matěna notifications@github.com wrote:

What was the previous version of PrusaSlicer that you were using? Was it any of the 2.3 alphas/betas?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/5796#issuecomment-761585955, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFUQTFZWZZW5QSEM3VTIZDS2GY7XANCNFSM4WFD7ECQ .

-- Alec Lindberg (425) 749-6673

zapdogster commented 3 years ago

I was using 2.3 RC3 on a Win 10 x64 machine. After installing PrusaSlicer-2.3.0+win64-202101111315 all of my print setting are gone except for two random ones I never use. I cannot seem to even restore all of the system ones, and there are none listed under print settings. 2021-01-16 17_43_38-PrusaSlicer-2 3 0 based on Slic3r

zapdogster commented 3 years ago

Update - I got all of my previous print settings back by activating a previous Configuration Snapshot.

lukasmatena commented 3 years ago

@lindbergalec The first alpha of 2.3.0 was released in October. Anyway, the reason I asked is that alphas and betas use different config directory than the rcs and finals, so I wanted to rule out a possibility that you created your profiles in a beta and are now surprised that they are gone. That would be normal (profiles need to be exported/imported in that case). But @zapdogster 's reply shows there is indeed something wrong.

@zapdogster Thanks. Could you please zip and send us your complete configuration directory (unless it contains some data you don't want to share) so we can have a look at what might have happened? (Help->Show Configuration Folder).

@lindbergalec Can you also get your profiles back by reverting to previous snapshot (Configuration -> Configuration Snapshots)? If so, could you please also send the zipped directory?

zapdogster commented 3 years ago

HI - So turns out restoring the Configuration Snapshot was only a temporary fix. The Print Setting disappeared the next time I started up the Slicer. I got them back permanently by:

However, sometime they seem to disappear again - not entirely sure on that as sometimes it comes back and other times it disappears??? So I'm not entirely sure this will work 100%. Tracking this behaviour.

zapdogster commented 3 years ago

PrusaSlicer.zip

Here are my config files after I restored the Print Settings.

rtyr commented 3 years ago

@zapdogster I can see that most of your custom profiles have 0.4mm nozzle diameter condition, so such profiles will not be visible for your custom "0.5mm Nozzle X" printer profile.

Only those two profiles you mentioned earlier are compatible with 0.5mm nozzle.

2021-01-16 17_43_38-PrusaSlicer-2 3 0 based on Slic3r

condi

zapdogster commented 3 years ago

Ahh - that was unknown to me.

So in mine, when I unclick All in the Dependencies, the "Compatible" line gets grey, and that print setting reappears in the Print Settings list for the 0.5mm nozzle. Personally I find the interaction of the two settings a bit confusing at this point, but I can work around that. Thanks again!!!

2021-01-18 09_51_39-Window

I am guessing I could just remove the printer condition for the Print Settings I would like to be generic to all Printer Settings?

Also, what does the Detach From System Preset do? and why would I use it? I read some post in the forums but don't quite understand it. That setting appears in at least 3 places: Print Settings. Filament Settings, and Printer Settings. image

rtyr commented 3 years ago

You can just remove and nozzle_diameter[0]==0.4 from the condition and save the profile. But since you can't use that profile anyway (incorrect settings for 0.5mm nozzle), you should rather make a separate profiles for 0.5mm nozzle with and nozzle_diameter[0]==0.5

condi2

zapdogster commented 3 years ago

Hi - so I think you are saying that in the Print Profiles, I should make new "copies" with parameters for a 0.5 nozzle and change the Compatible Printer Conditions for 0.5mm?

I did this along the way, and it seemed to work: image

I'm pretty new at this, but there seem to be a large number of "Dependency" options and it is very unclear to me how they interact (or don't interact)...

Thanks gny

rtyr commented 3 years ago

Don't do anything with "Compatible printers", just edit the condition.

rtyr commented 3 years ago

Hi, I believe so, looking at my downloads, I see a 2.3 version from April

@lindbergalec What was the filename?

lindbergalec commented 3 years ago

Reverting did seem to return the profiles, find attached, restarting the slicer also seemed to keep the returned settings. [image: Screen Shot 2021-01-21 at 4.14.48 PM.png]

On Tue, Jan 19, 2021 at 3:31 AM rtyr notifications@github.com wrote:

Hi, I believe so, looking at my downloads, I see a 2.3 version from April … <#m6760610715175147850>

@lindbergalec https://github.com/lindbergalec What was the filename?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/5796#issuecomment-762783744, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFUQTCSQIYLJ5AA7ORG4B3S2VUSLANCNFSM4WFD7ECQ .

-- Alec Lindberg (425) 749-6673

rtyr commented 3 years ago

I guess we can close this now.