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

Cura Settings Migration Issue - VaseMode #458

Closed
FormerLurker opened this issue Feb 25, 2020 · 2 comments
Closed

Cura Settings Migration Issue - VaseMode #458

FormerLurker opened this issue Feb 25, 2020 · 2 comments
Assignees
Labels
bug possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch

Comments

@FormerLurker
Copy link
Owner

When migrating manual cura settings to Octolapse V0.4, IsVaseMode can be NULL, which will throw an error on print start (cancelling the print depending on the octolapse main settings).

As a workaround, if you encounter this issue, just open your printer profile and click 'Save'. That will fix the problem.

@FormerLurker FormerLurker self-assigned this Feb 25, 2020
FormerLurker added a commit that referenced this issue Feb 26, 2020
@FormerLurker
Copy link
Owner Author

I think this is fixed as well. If you want to test it, you can import your settings from the 0.4.0rc1.dev2 backup you sent me. That was apparently the one that caused an issue.

Turns out, I didn't fix the migration. I just made the vase_mode calculation work with nulls :)

@FormerLurker FormerLurker added the possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch label Feb 26, 2020
@FormerLurker
Copy link
Owner Author

I think even if you don't try importing your settings from dev2 that I can close this issue, since I have the same file and it works for me. If you do try importing the old settings, make sure you export your current settings so you can re-import them after the test. For now I'm going to close this issue, but will re-open it if you have any additional problems.

Thanks again!

Closed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch
Projects
None yet
Development

No branches or pull requests

1 participant