Cura 4.7.1 VERY slow to load

[davchr 1]

Cura 4.7.1 was running fine.  I installed Cura 4.8 and 4.8 loaded and ran VERY slow.  More than 5 minutes to load the software.  Loading model files, rotating objects, etc. were painfully slow.  I tried 4.7.1 again and it now has the same issues. I uninstalled 4.8 and 4.7.1 and re-installed 4.7.1 and it still runs painfully slow.  I ran Creality Slicer, which is based on a Cura engine and it runs fine.  How can I get Cura 4.7, 4.8, or any other version running again on my Windows 10 desktop?

[davchr 1]

A little more info.  Cura uses between 0% (most of the time) and 0.1% of the CPU time while loading on my i7 machine.

[Wright301 0]

Did you ever get a solution to this problem ? My PC recently went through an update ( Windows 10 ) , before the update Cura 4.8.0 ran fine, now after the update Cura is very very slow to the point I can’t use it.. yesterday it took half an hour to load !!! But today I tried turning the wi-fi off on the laptop, and hey presto Cura runs fine, no stalling, it runs as fast as it once did !!! Very confusing

[ahoeben 1,965]

1 hour ago, Wright301 said:

But today I tried turning the wi-fi off on the laptop, and hey presto Cura runs fine

 

Do you have a network drive mapped to the driveletter X:? If so, try mapping it to a different drive-letter.

[Wright301 0]

2 hours ago, ahoeben said:

 

Do you have a network drive mapped to the driveletter X:? If so, try mapping it to a different drive-letter.

I do, I will try that, but it was working fine before the update, and the X drive has been there for months 🤔

[Wright301 0]

O.M.G That worked, changed from X to W and hey presto Cura is back working as it should be... now that’s defo something wrong in the program 🙈

[ahoeben 1,965]

It is an artifact of the buildsystem. The source files are on a drive labeled X: at Ultimaker, and for some reason Cura keeps looking for the files in their "original" location before using the files installed in your program files folder. If there's an inaccessible drive X, each file will result in a timeout after ~20 seconds or so before continuing. There are many files.

 

Why X:? Because it was deemed less prevalent than the previously used 😧 drive.

The D drive used collide with removable drives, which caused a similarly annoying issue that Windows told the user there was not disk in drive D a couple hundred times.

 

I'm not quite sure why the buildsystem doesn't use an ntfs junction instead of a driveletter. That would forego the entire drive letter thing. Better still would be to stop Cura from trying to find the files in their "original location" in the first place.

[Wright301 0]

Beggars belief, QA is in question now 😳

[jhonb 0]

Thanks for this solution ahoeben. This has been driving me nuts for a few months. Problem solved.

[derpreis 0]

Thank you, this worked wonderfully. müllbox

 

[nallath 1,123]

This shouldn't be a problem for 4.9.1 anymore