Cura: 4.7.1 Crashes When Adding New Non-Networked Printer

Created on 26 Sep 2020  路  7Comments  路  Source: Ultimaker/Cura

I'm trying to add a Creality Ender 3 to Cura. This consistently happens every time.

Application version
4.7.1

Platform
Windows 10

Printer
Anycubic i3 Mega Selected
Trying to install a Creality Ender 3

Reproduction steps

  1. 3 printers already installed. Anycubic i3 Mega, Kingroon KP3, Custom FFF printer. Attempting to install Ender 3.
  2. Settings, Printer, Manage Printers, Add Printer, Add Non-Networked Printer.

Screenshot(s)
NA

Actual results
Cura hard crashes when I click the Add Non-Networked Printer button. I actually did get to the list of selectable printers once, but when I selected the Creality Ender 3 and clicked the Add button...Cura crashed.
cura.log

Expected results
New printer added

Project file
No project started yet.

Log file
cura.log

Additional information
(Extra information relevant to the issue.)

Bug

Most helpful comment

So disable the optimizer and try again.

And if that worked, please open an issue at https://github.com/fieldOfView/Cura-StartOptimiser/issues

All 7 comments

I confirmed this problem is isolated to 4.7.1 because reverting back to 4.6.2 solved the problem.

Removing all of the plugins from 4.7.1 did not change the crashing issue.

After adding the new printer in 4.6.2, I tried re-installing 4.7.1 and the new printer did not appear on the list of printers. I'm switching back to 4.6.2 for the time being until this bug is fixed.

Removing all of the plugins from 4.7.1 did not change the crashing issue.

You didn't disable them. The logs show that the startOptimizer plugin is still active. The logs also indicate that a certain file that the ender needs is not available. I suspect that that file is prevented from being loaded by the optimizer.

So disable the optimizer and try again.

So disable the optimizer and try again.

And if that worked, please open an issue at https://github.com/fieldOfView/Cura-StartOptimiser/issues

After disabling the optimizer...then uninstalling the optimizer completely and upgrading to 4.7.1, the problem persisted.

I uninstalled 4.7.1 and went to my c:\user\ME\appdata\local\cura folder and renamed it cura_old. I then reinstalled 4.7.1 and it worked fine. Something must have gotten messed up in cache.

So for me, the problem is resolved.

Did you rename c:\user\ME\appdata\local\cura or c:\user\ME\appdata\roaming\cura? Both exist, and the distrinction is important. The former only has cache, whereas the latter has all of the configurations in it.

I renamed it cura_old. The settings were intact when I ran 4.7.1.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wi1k1n picture wi1k1n  路  3Comments

mnswamp1 picture mnswamp1  路  3Comments

JRRN picture JRRN  路  3Comments

thopiekar picture thopiekar  路  3Comments

probonopd picture probonopd  路  3Comments