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

Configuration file problem (4.6.2 => 4.7.0) #8310

Closed
Fabdu57 opened this issue Sep 3, 2020 · 11 comments
Closed

Configuration file problem (4.6.2 => 4.7.0) #8310

Fabdu57 opened this issue Sep 3, 2020 · 11 comments
Labels
Status: Duplicate Duplicate of another issue.

Comments

@Fabdu57
Copy link

Fabdu57 commented Sep 3, 2020

Hi,

I have a "big" problem with configuration file...
I updated some days ago Cura from 4.6.2 to 4.7.
On 4.6.2 I did some profiles that, by safety, i saved in ".curaprofile" on my computer. During the update, the profiles were automatically reset to version 4.7 (because I had not uninstalled the user preferences).

However, I just saw that I was missing a profile. So I tried to import it, I got a message telling me that the import was done (with its name), but it does not appear in the list.
If i try to import again, same message, but with "#2" at the end. But nothing in list and configuration.
If i try to import again, same message, but with "#3" at the end. But nothing in list and configuration.
If i try to import again, same message, but with "#4" at the end. But nothing in list and configuration.
(....)

Attached is the profile. If I import it again on 4.6.2 (which I reinstalled), it works without problems ...

How to solve this problem... ?

Thanks in advance,
Fabrice

Cura v2020.06.28 - Litophanie.zip

@rachael7
Copy link

rachael7 commented Sep 3, 2020

I had this problem with one of my profiles. It was importing it, but not making it available for the machine I was on, or maybe any machine at all. It did the same thing with adding copy numbers to the end. Eventually, I was able to track down the problem by comparing the profile to the other profiles that did work. There was one line that was different, I think it was 'quality_type'. In the working profiles, it was set to 'not_supported', but in the bad one, it was set to something else. To get at it, I had to open the .curaprofile file with a zip extractor, change the problem line, then put it back in the zip file. After I did that, it imported fine. It was still #5 or something like that, but I went in the folder C:\Users\my_user_name\AppData\Roaming\cura\4.7\quality_changes, deleted #1-4, then I was able to rename the one that worked in Cura to remove the unnecessary number.

@Fabdu57
Copy link
Author

Fabdu57 commented Sep 4, 2020

Thanks for your message.
Effectively i found on "C:\Users$user\AppData\Roaming\cura\4.7\quality_changes" the cfg file associate to my configuration:

creality_base_extruder_0_cura_v2020.06.28_-litophanie.inst.cfg
creality_ender3pro_cura_v2020.06.28
-_litophanie.inst.cfg

I tryes to delet them and tooh from 4.6 (C:\Users$user\AppData\Roaming\cura\4.7\quality_changes) both and put on 4.7, but still same problem... Then i tryes a second solution : import as you mention and rename file. Same, profile not appears on list.

I think that 4.7 version have a lot of bug... And that is a big bug that Ultimaker need to interven ASAPS...

@rburema rburema added the Status: Needs Info Needs more information before action can be taken. label Sep 4, 2020
@rburema
Copy link
Member

rburema commented Sep 4, 2020

Attached is the profile.

I don't see it here. Could you try that again? It may need zipping to appease github.

@Fabdu57
Copy link
Author

Fabdu57 commented Sep 4, 2020

Oh sorry i forget to put file...
Cura v2020.06.28 - Litophanie.zip

@no-response no-response bot removed the Status: Needs Info Needs more information before action can be taken. label Sep 4, 2020
@nallath
Copy link
Member

nallath commented Sep 4, 2020

Duplicate of #8229

@nallath nallath marked this as a duplicate of #8229 Sep 4, 2020
@nallath nallath closed this as completed Sep 4, 2020
@nallath nallath added the Status: Duplicate Duplicate of another issue. label Sep 4, 2020
@Fabdu57
Copy link
Author

Fabdu57 commented Sep 6, 2020

Duplicate of #8229

Sorry but ly problem is not solv...
Is a solution avaible or not ?!

@rburema
Copy link
Member

rburema commented Sep 6, 2020

@Fabdu57 No sorry, not yet. This one is closed because we're sure it's the same as #8229 (which is still open), and we like to keep issues that where already reported in the same place. To continue to conversation and/or to monitor the discussion/progress, you should go to that link, which goes to an open issue that is the same (or has the same underlying problem) as yours.

@Fabdu57
Copy link
Author

Fabdu57 commented Sep 11, 2020

This is not my problem that an other topic is open.
My problem is different, i am not the other people.

So i want my topic became again open and have help !

@konskarm
Copy link
Contributor

konskarm commented Sep 11, 2020

Hi @Fabdu57. The profile that you are trying to import is a draft profile which is not compatible with nozzles <0.6mm (for creality printers). The quality profile is correctly being imported, but it does not become available due to your selected nozzle. If you switch to a nozzle that contains a draft profile (e.g. 0.6mm), you should be able to see the quality profile you just imported.

I agree that currently it is not clear, so we are working on a solution to at least give a message as to why the profile is not visible (see #8363).

The reason this github issue is closed is that it is a duplicate of #8229 and we want to keep the discussion on duplicate issues in one centralized issue, so please move further comments on #8229.

@Fabdu57
Copy link
Author

Fabdu57 commented Sep 12, 2020

I don't reallly understand...
It works on 4.6.2, layer height is 0.12 and noozle 0.4.
So i don't really understand your answer in fact.... If it works on 4.6.2 and i can print, why not on 4.7 lol

@konskarm
Copy link
Contributor

konskarm commented Sep 14, 2020

In 4.6 it was actually a bug that was allowing all of the quality profiles to be shown, even if they were not compatible. We fixed that in 4.7 so as not to allow a configuration select a profile that doesn't match it, which can cause bad or even failed prints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue.
Projects
None yet
Development

No branches or pull requests

5 participants