Jump to content
Ultimaker Community of 3D Printing Experts
SandervG

Introducing Ultimaker Cura 3.3 | Beta

Recommended Posts

17 hours ago, rebekah_harper said:

Am I the only one with a UM3 where this beta doesn’t work???? 

No response to my comments or log file.

 

No - you're not alone - welcome to the club... ;)

It's the same here...

 

https://community.ultimaker.com/topic/22192-introducing-ultimaker-cura-33-beta/?page=3&tab=comments#comment-205243

 

Edited by tinkergnome

Share this post


Link to post
Share on other sites
22 hours ago, rebekah_harper said:

this should be it.

 

I just enjoy being part of the process.  

 

I always run the last full version and a beta. 

cura.log

Hi,

 

From the log files we see there is still a UM2+ loaded, that would indicate the clean install hasn't removed the config folder. Could you try to zip the config folder and share it?

Share this post


Link to post
Share on other sites
5 hours ago, rebekah_harper said:

I will sort out the configuration files once I find them.

 

this log file comes from a post windows reset.  I added the UM2+ first as I run one of them too. But unlike before the rest it also behaved as the UM3 and failed so now both printers fail to work with 3.3

 

 

It looked like Cura wanted to add a UM3 with a custom material for which it could not fin the profilel. Could that be possible?

We fixed this in the upcoming stable.

Share this post


Link to post
Share on other sites
On 4/21/2018 at 10:35 PM, ninjapigeon said:

Help appreciated!

-launch Cura 3.3 Beta after installing.  Agree to license. Can see a pop-up for "allow" of something behind a "select/name your printer" window.

-select my printer (UM3, named "Ultimaker 3" or even "BldrBot")

-window disappears as does all of Cura 3.3. (auto-quit)

 

Ideas? Suggestions?

incidentally, 15mb log for first launch? wow.

So, fixed this myself.

 

Seems the programmers on 3.3 took an assumption that didn't fit my profile. I have a smallish SSD to run Windows, and launch my apps from a RAID1 HDD setup.

After 3.3 released today, and i removed every config/install/appData file for my previous Cura installs, i had the same error.

This time the log said something along the lines of "file not found on expected drive".

Uninstall it all again, reinstall on the default C: drive.. lo and behold it works, and i'm printing now from 3.3.

:(

 

TL;DR - fixed, only if i installed on my default C: drive. Lame Ultimaker, lame.

Share this post


Link to post
Share on other sites
1 hour ago, ninjapigeon said:

So, fixed this myself.

 

Seems the programmers on 3.3 took an assumption that didn't fit my profile. I have a smallish SSD to run Windows, and launch my apps from a RAID1 HDD setup.

After 3.3 released today, and i removed every config/install/appData file for my previous Cura installs, i had the same error.

This time the log said something along the lines of "file not found on expected drive".

Uninstall it all again, reinstall on the default C: drive.. lo and behold it works, and i'm printing now from 3.3.

:(

 

TL;DR - fixed, only if i installed on my default C: drive. Lame Ultimaker, lame.

Yes we just found out of this bug after the release and are working on a fix. Sorry!

Share this post


Link to post
Share on other sites

Version 3.3 (on Windows 10 - 64 bit) installs fine, and uninstalls the older version 3.2.1. Upon starting Cura 3.3, I see the logo splash screen and the changelog window, which then shuts down Cura. No orphan executables, nothing in the Windows logs.

Have uninstalled/reinstalled, and restarted Windows, but with the same result.

Share this post


Link to post
Share on other sites
3 hours ago, Ghostfather said:

Version 3.3 (on Windows 10 - 64 bit) installs fine, and uninstalls the older version 3.2.1. Upon starting Cura 3.3, I see the logo splash screen and the changelog window, which then shuts down Cura. No orphan executables, nothing in the Windows logs.

Have uninstalled/reinstalled, and restarted Windows, but with the same result.

I had the same issue on my end. Try deleting your Cura config folders from both your AppData/Local and AppData/Roaming directories. Ended up working for me.

 

Note: Make sure you save any custom profiles you have before doing this.

Share this post


Link to post
Share on other sites
On 3/28/2018 at 12:40 AM, smartavionics said:

Thanks for the mention @SandervG, I will put together a topic that describes the new bridging features and the associated settings.

Great work with scaleable extra prime. One little sugestion is a check box called combing only. Where scaleable extra prime only applies to moves which haven't had a retraction

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Ultimaker Cura | a new interface
      We're not only trying to always make Ultimaker Cura better with the usual new features and improvements we build, but we're also trying to make it more pleasant to operate. The interface was the focus for the upcoming release, from which we would already like to present you the first glance. 
        • Like
      • 114 replies
    • "Back To The Future" using Generative Design & Investment Casting
      Designing for light-weight parts is becoming more important, and I’m a firm believer in the need to produce lighter weight, less over-engineered parts for the future. This is for sustainability reasons because we need to be using less raw materials and, in things like transportation, it impacts the energy usage of the product during it’s service life.
        • Like
      • 12 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!