Ultimaker Cura 4.7 is available!

[ghostkeeper 105]

> What should do the users with printers with shared heaters?

 

From our understanding, those users, if they choose to stay with 4.6 or modify that QML file to show the checkmark, should disable the Shared Heater checkbox and only print single extrusion prints. Because if they print dual extrusion prints, the filaments will collide in the nozzle.

If you think this is not an issue, please share your opinion here: https://github.com/Ultimaker/Cura/issues/8148 . You can read an explanation of the issue here: https://github.com/Ultimaker/Cura/issues/8148#issuecomment-674429133 . We've tested this behaviour and verified that indeed both filaments will always be brought to the nozzle tip at the same time, and thus mechanically collide in the nozzle. That issue thread would benefit greatly from some proof of how the feature can work correctly.

[nallath 1,120]

38 minutes ago, ymoret said:

I'm also having issues with materials since the Cura 4.7 update. All material settings are grayed out and I have no more material in the list.
Did I do something wrong?
 

The UM2 doesn't have material settings with the slicer, they live in the printer. So the view that you have is as it should be.

[wireless 0]

4 hours ago, wireless said:

Just wanted to add to the knowledge out there.

I've been using Cura 4.6.1 with an Artillery Genius on Windows 10 for several months and got it tuned very nicely with printer profiles from 3DN and with several material profiles created by myself.

 

Yesterday after spending most of the day on a new Fusion 360 design, I went to print my new masterpiece (!), saw the invite to update to Cura 4.7, and that's when the pain started.

 

Experience:-

• version 4.7 installed OK after being 'allowed' to remove my previous installation, but NOT ALLOWED to remove my config files
• restarted v 4.7, only to be unexpectedly taken through the process of creating a new printer profile
• none of my material profiles was present
• set up a new default printer and then went to re-install my 3DN '.curaprofile' files. These generated an error "Could not find a quality type adaptive for the current configuration."
• Decided to go back to v4.6.1 and that best way to do that was to restore the Windows 10 machine to the last 'restore' status of 9 days ago.
• Cura 4.6.1 was installed and 4.7 was not - so far, so good. Tried to run 4.6, but no amount of coaxing would make it run. Investigations showed that there were lots of v4.7 files still present in the system

I have spent a few hours now in tracking down remnants of Cura software on my system, and together with frequent re-boots have got a 'fresh' install of v4.6, but it will still not either load my 'curaprofiles', nor has it found my materials presets. I guess there must still be data on my installation somewhere, so I'm now on the long path to recalling all the setups necessary to get my 3D printer back to the quality I'm used to (at the moment I'm trying to solve retraction issues that I never had before).

 

Having read through the forums, and having requested support from Cura (but told that I don't qualify), I'm still not sure what I should have done differently.  I have really enjoyed using Cura to date, but.....

 

 

UPDATE: Clearly Windows 10 needed some "quiet time".   After some 2 or 3 hours, Cura 'suddenly' discovered other printers including mine. After that, it was quite 'happy' to allow me to import my 'curaprofiles'. Bizarre!

 

So, with the exception of the lost custom materials, that's me back to where I was 24 hours ago - with a functional Cura v4.6 again.

 

Having got my workflow back, I think I'll stick with v4.6 for now.....

 

[eldarius1 0]

I'm having troubles with the sewings in cura 4.7, I place it in the back but when I print, the sewings are placed in random positions

[Longtoke 25]

On 8/31/2020 at 9:57 PM, nallath said:

You can always go back a version and delete whatever profiles the beta creates. I have never seen a case where installing the beta would destroy profiles already present on the machine.

So yeah; If people don't provide any feedback, we will only focus on Ultimaker printers. At the point that we get bug reports (that contain actionable information), we will strive to solve them. Case in point; We already have a patch release available.

 

Creating FOSS is a collaboration. You don't have to upgrade, but if people that don't pay me don't put in any effort, why should we?

As for any complaints on how the software currently works; You can also discuss those things with us! By all means post the things that you like / don't like on the github. Discussing workflow (and suggesting new ways it should work) or documenting existing workflow (because it might work as intended, but people don't understand it?) is also a way to contribute to open source. It's not just writing code that is important. Even seemingly simple things like telling people that didn't fill in the bug template to do so will greatly help us (since now it takes up valuable time from developers!)
 

 

The fact that you have engaged in this conversation is testament to your dedication, I empathize with your frustrations on some levels but......

 

14 hours ago, Rabbit-o said:

 

Make announcements before hiding or deleting features..

 

 

Just one example of part of the issue that I think is being overlooked. 

 

It would be immensely helpful if each "patch" and/or beta had a specific list of what changes have occurred. You can't honestly expect high uptake of beta's and new releases when you leave people in the dark. While there's notes accompanying releases etc, they need to be far more comprehensive.

 

Even a simple "We undertook a change to how Cura internally references profiles", would say to the end user don't be surprised if your printers start g-code has been altered and/or it requires you to remake the printer profile from scratch. 

 

The more informed people are about what changes have been undertaken, the better able they are to assess what impacts trialing a beta will have beforehand. 

[bazxa 1]

Cura Team

 Fabulous, thanks

Barry

[GregValiant 1,251]

I've double checked, and nowhere in SandervG's opening post is it mentioned that casual visitors to this thread should wear helmets and body armor.  There really should have been some kind of warning.

[HoltzAlex 0]

I found a bug with the new Cura 4.7 where using dual nozzles, regardless of what is selected in the build plate adhesion section, it does not change what nozzle is being called to extrude. With having extruder 2 selected, it still called on extruder 1. When selecting extruder 1, my custom start gcode is run. Not sure what is going on with this since the preview option shows the correct extruder being called.

[HoltzAlex 0]

1 hour ago, HoltzAlex said:

I found a bug with the new Cura 4.7

So the main issue is not with the build plate adhesion, but more with the start g-code. When I remove the following code, 

G28 ;Home

G29

G1 Z15.0 F6000 ;Move the platform down 10mm

There is not an issue with the extruder. When this code is included then the extruder is always set as T0 as the starting extruder.

[Ghene 24]

So... is the patch safe to install?

 

[Janek 1]

Something bad is happened with "Z Seam Alignment"="Sharpest Corner" and "Seam Corner Preference"="Hide Seam".

Same project file with same settings give really different results for 4.6.1 and 4.7.0.

4.7.0 exposes the seam instead of hiding and it is not the sharpest corner anyhow. 
Same layer view on pictures (one pic. is on orthographic and other is on perspective view). 
 

 

Edited September 9, 2020 by Janek

[Arktron 0]

Cura genera error de partida ... Estaba funcionando bien con la version 4.7.0, pero al actualizar a la 4.7.1 dejo de cargar. A los segundo de iniciar e ingresar a configurar la impresora, estas no cargan y se cae el software.

 

Favor ayuda---

[ahoeben 1,948]

@Arktron could you please try to ask your question in english? It is not my native language either, but it helps if we all speak the same language. If you cannot use english, please post in the appropriate forum section (see https://community.ultimaker.com/forum/122-languages/ ). Also if you want anybody to be able to help you, please provide more information; like what printer you use, and what is going wrong.

[nallath 1,120]

18 hours ago, Janek said:

Something bad is happened with "Z Seam Alignment"="Sharpest Corner" and "Seam Corner Preference"="Hide Seam".

Same project file with same settings give really different results for 4.6.1 and 4.7.0.

4.7.0 exposes the seam instead of hiding and it is not the sharpest corner anyhow. 
Same layer view on pictures (one pic. is on orthographic and other is on perspective view).

 

Please report the issue on github.

[Janek 1]

28 minutes ago, nallath said:

Please report the issue on github.

Sorry I am not github specialist and I have no time for becoming it as well at moment. I use older version till it will be fixed.

[HunteR7411 3]

2 minutes ago, Janek said:

Sorry I am not github specialist and I have no time for becoming it as well at moment. I use older version till it will be fixed.

The problem is it wont be fixed unless they can track it via github. 

[nallath 1,120]

52 minutes ago, Janek said:

Sorry I am not github specialist and I have no time for becoming it as well at moment. I use older version till it will be fixed.

You don't have to be a specialist. It's quite literally filling out some information that we need.

[Janek 1]

OK! I will check it out later and report on Github.

[Daniel.Ortiz 0]

Tried printing a Benchy with the default Ender 3 Pro settings on Cura 4.7 and it produces blobs towards the bow of the benchy. Reverted back to Cura 4.5 and it got rid of this problem. Not sure if its a bug or not but Cura significantly slows down the print speed on curves with this new version leading to fuzzy, ugly curved surfaces.

 

 

EDIT: I do not have pictures of my bad benchys but can provide pictures if need be!

Edited September 11, 2020 by Daniel.Ortiz

[ChrisRowland 0]

I also have a problem with Cura 4.7.1, Windows 64 bit version.

 

I've been running 4.6.1 sucessfully and saw the invitation to upgrade so did.  The install process worked.

But starting Cura doesn't.  I get to the window asking for me to contribute by sending anonymous data and click on 'Next'

Cura silently closes. No error messages, nothing.

The same multiple times, even after a restart.

 

Has anyone tried this with W10?  It seems pretty solid and as I've not even got to the point of selecting a printer seems pretty generic.

 

Will return to 6.7

 

Chris

 

[bazxa 1]

I worked with W10 64 for me but my prints were not  as good and I don't have enough knowledge to identify defects specifically. Also changed printers at the same time, it could be that.  None of the behaviour that you are reporting.

 

[ChrisRowland 0]

Not really much behaviour, more lack of behaviour.

 

I've uninstalled 4.7.1 and reinstalled 4.6.1 but if there's any more feedback I could provide - log files for example - I could install 4.7.1 again and try it.

 

I'd need to be able to continue to use 4.6.1 but it seems to be possible to install two versions.  I now know not to uninstall the previous version and not to delete my profiles.

 

Chris

[yzorg 9]

Hi guys.
i maybe saw a little flaw in Cura there. otherwise perfect software. Love it. 
i am on MacOs Catalina newest and have Cura 4.7.1

 

- The text on the tab "Monitor" has quite a different font for its "I" compared to the rest of the letters.

it has serifs the rest not.
 

[ricardo2004 0]

Hi all!

 

Is there a way to configure the colors that is being used to show at preview, the new version is showing in a strong blue, the old one was a yellow light, it was better to see. 

 

Thank you!!

 

.Ricardo Moreira 

[Torgeir 242]

Hi Ricardo,

 

Welcome in here.

 

It depends a little, -the "newer" Cura versions show the color of the filament, however, if you go to setup under general -there is one of the first named "Theme". At default "Ultimaker" is set, press "Ultimaker" and see the variants.

A restart of Cura is needed for changes to take place.

 

Thanks

Torgeir.