New to Cura - when I clicked the notification to upgrade my 4.4.1 installation, it put a second 4.5 install on my HD. Is there a way to simply upgrade? Or migrate my 4.4.1 settings over?
11 hours ago, MaverickNH said:New to Cura - when I clicked the notification to upgrade my 4.4.1 installation, it put a second 4.5 install on my HD. Is there a way to simply upgrade? Or migrate my 4.4.1 settings over?
It should automatically migrate your 4.4.1 settings.
15 hours ago, DavidEDW said:Does anyone know what happened to the NX plugin?
It needs to be updated to the latest SDK before it will work with 4.5. It's an external contribution so we need to clear this with them.
Thanks nallath - then I can uninstall V4.4.1?
Edited by MaverickNHHi, installed this on my Mac, but can't run the application as I get the error
"Ultimaker Cura" can't be opened because apple cannot check it for malicious software.
Is there a workaround for this?
Thanks
H
On Mac you have to right click the application, then select Open. A window appears to confirm that you really want wo open it. You have to do this step only for the first time, then a simple double click is enough to open Cura.
On 2/28/2020 at 2:08 PM, MaverickNH said:Thanks nallath - then I can uninstall V4.4.1?
Yes, you can uninstall 4.4.1 (check first, if 4.5 works), but DON'T remove configutation files / settings (I made this mistake once and hopefully never do it again ;-) ).
Keep in mind that most 3rd party printer profiles are provided by the community and not by Ultimaker.
-
2
That's how the profile was provided to us. We can't (and won't) test all the third party machine profiles.
-
3
@nallath , If we find a small bug with a 3rd party installed profile, can we correct it or only the author has the rights ?
23 minutes ago, hussainsail2002 said:@nallath , If we find a small bug with a 3rd party installed profile, can we correct it or only the author has the rights ?
You can make a pull request with optimizations for third party profiles. If they pass our checks, we can then merge them.
-
1
2 hours ago, nallath said:That's how the profile was provided to us. We can't (and won't) test all the third party machine profiles.
The legacy profile did not have this issue, and the issue has been reported during the beta.
The question is, why did you change a working profile to one that is inferior, and then make it a hassle to import the legacy profile? It'd be better to continue using what works, rather than to have some rando give you a profile which you distribute without testing.
Sloppy work.
-
1
4 hours ago, Spandex_Spatula said:
The legacy profile did not have this issue, and the issue has been reported during the beta.
@Spandex_Spatula Just following up on this - can you show me where was it reported?
QuoteSloppy work.
We accept contributions for third-party printer definitions, but we do not test or maintain them, as nallath states above. There are 200 third-party definitions in Cura, we don't have each printer to test. We take definitions contributed by the community, and take it on good faith that they're tested adequately.
If you haven't already, please make an issue report on GitHub and we'll try to get this straightened out. If you have made one already, please refer me to it.
-
1
The new version of Cura seems to take forever to slice larger models now. The older version would take no time at all.
On 3/2/2020 at 5:01 PM, Spandex_Spatula said:Sloppy work.
one of the only few slicers that host the definitions of so many printers,
Its also pretty powerful , on par with paid ones like simplify3D.
-
2
20 minutes ago, Mad_Al said:The new version of Cura seems to take forever to slice larger models now. The older version would take no time at all.
You can verify this by slicing a model in each version, and then examining the log. Each version will log how long a slice takes, e.g.
2020-03-04 09:45:16,489 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onSlicingFinishedMessage [663]: Slicing took 3.141117572784424 seconds
41 minutes ago, Mad_Al said:The new version of Cura seems to take forever to slice larger models now. The older version would take no time at all.
19 minutes ago, maht said:
You can verify this by slicing a model in each version, and then examining the log. Each version will log how long a slice takes, e.g.
2020-03-04 09:45:16,489 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onSlicingFinishedMessage [663]: Slicing took 3.141117572784424 seconds
@Mad_Al Just tried it with the attached model (which ships on the USB stick of the UMS3).
4.4.1
2020-03-04 14:06:44,025 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onSlicingFinishedMessage [663]: Slicing took 8.200138330459595 seconds
4.5
2020-03-04 14:03:06,005 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onSlicingFinishedMessage [663]: Slicing took 7.160868167877197 seconds
1.039270162582398 seconds faster!
- maht unpinned and unfeatured this topic
Recommended Posts
DavidEDW 0
Does anyone know what happened to the NX plugin?
Link to post
Share on other sites