Ultimaker Cura 3.1 | Beta

[Msuurmond 28]

@Msuurmond

I already deleted the 'beethefirst_beetf_0.6_tpu.inst.cfg' file and I still having crashes in the new 3.1 beta (and I don't have the Cura 2.7).

Hi,

These bugs are fixed but we are not sure if 'old' single extruder machines work correctly now. Could you uninstall 3.1-BETA, remove the 3.1 config folder and install:

https://we.tl/vzvre7ovfH (New version of 3.1-BETA)

We would like to hear your findings.

[amagro 3]

Bad news:

[Msuurmond 28]

Could you share a log and did you manually modify these *.cfg files?

[amagro 3]

No, I did not manually modify the cfg file.

I think I need to do a clean install, there's a lot of old files in the system from the previous versions.

log: https://we.tl/qpFWHu5xw1

Edited November 28, 2017 by Guest

[amagro 3]

Hi,

I finnaly did a clean install, and now 3.1 beta is working.

But there's another issue, I cannot import old profiles, genereted in 3.0.4.

Is strange because Cura confirmed that the profile was successfully imported, and then nothing appears on the profile list.

As you can see in the image bellow I tryed three times to import the same profile.

-

Cura profile: https://we.tl/t3dZn5y5RC

[amagro 3]

Reinstall 3.1 beta, and I'm getting the same problem.

Here's the log: https://we.tl/KZVTglLSVc

[Msuurmond 28]

Reinstall 3.1 beta, and I'm getting the same problem.

Here's the log: https://we.tl/KZVTglLSVc

 

Good too hear that the 3.1-BETA is working with a clean install.

Usually when profiles don't show up, Cura thinks they are not compatible with the current selected printer. We will have a look at the log files tomorrow.

[amagro 3]

Usually when profiles don't show up, Cura thinks they are not compatible with the current selected printer. We will have a look at the log files tomorrow.

It's strange because I installed the 3.0.4, configured the same exact custom printer as in the 3.1.0 beta, and did not have any problem importing the old profile, as you can see in the image below.

-

[Msuurmond 28]

We have fixed this in a new build: Could you try it? https://we.tl/BUkblDTVBX

[danilius 118]

I can't get 3.1 to send files to Octoprint even though it does connect correctly, it does not display an error message when failing the upload, where can I find a log file?

[danilius 118]

Never mind, I found the log file and here is the error:

ERROR - OctoPrintPlugin.OctoPrintOutputDevice._startPrint [479]: An exception occurred in network connection: name 'global_container_stack' is not defined

Note that Cura is actually connecting OK, and can monitor the print in progress just fine.

[ahoeben 1,948]

ERROR - OctoPrintPlugin.OctoPrintOutputDevice._startPrint [479]: An exception occurred in network connection: name 'global_container_stack' is not defined

 

Thanks for the report. I will fix this for the 3.1 final release. As a workaround for now, you can disable support for writing to the sdcard in the OctoPrint webinterface. After that you may have to connect to the octoprint instance again in Cura.

Update: Here's the fix: https://github.com/fieldOfView/OctoPrintPlugin/commit/d5414e

Edited December 1, 2017 by Guest

[ChrisRiddell 13]

We have fixed this in a new build: Could you try it? https://we.tl/BUkblDTVBX

 

On that build Layer View does not work the models just stay grayed out.

[XYZDesignPro 70]

The 5 view buttons in the upper right corner are a very nice, and welcome addition.

[Msuurmond 28]

We have fixed this in a new build: Could you try it? https://we.tl/BUkblDTVBX

On that build Layer View does not work the models just stay grayed out.

3.0.4 did work?

Could you post you logfiles please?

[ChrisRiddell 13]

We have fixed this in a new build: Could you try it? https://we.tl/BUkblDTVBX

On that build Layer View does not work the models just stay grayed out.

3.0.4 did work?

Could you post you logfiles please?

After rebooting the system it started working their was nothing in the logs every looked normal.

[Msuurmond 28]

 

 

 

We have fixed this in a new build: Could you try it? https://we.tl/BUkblDTVBX

 

On that build Layer View does not work the models just stay grayed out.

 

3.0.4 did work?

Could you post you logfiles please?

 

After rebooting the system it started working their was nothing in the logs every looked normal.

 

Strange, but good to hear it all works for you now. Keep us posted on your findings!

[amagro 3]

@Msuurmond

Now I can manually import the old profiles, but there is another strange issue with the profiles. The 3.1beta is not automatically importing the profiles from 3.0.4, but is showing the settings of one of them (TPU200 (24Nov)). And when I manually imported a profile to 3.1beta - that already exists on 3.0.4, the Cura renumber the profile indicating that already exists in 3.1beta, but as we can see in the image is not showing on the Profile list. 

Edited December 4, 2017 by Guest

[Msuurmond 28]

@Msuurmond

Now I can manually import the old profiles, but there is another strange issue with the profiles. The 3.1beta is not automatically importing the profiles from 3.0.4, but is showing the settings of one of them (TPU200 (24Nov)). And when I manually imported a profile to 3.1beta - that already exists on 3.0.4, the Cura renumber the profile indicating that already exists in 3.1beta, but as we can see in the image is not showing on the Profile list. 

Did you try with a clean 3.1 settings folder? Otherwise previous BETA's might have made 'corrupt' profiles that conflict/don't get generated in a correct way.

[amagro 3]

Yes, I cleaned 3.1 settings folder before installing it.

Folders deleted:

C:\Users\"user"\AppData\Local\cura\3.1

C:\Users\"user"\AppData\Roaming\cura\3.1

Is there another folder that I should delete?

[Msuurmond 28]

Yes, I cleaned 3.1 settings folder before installing it.

Folders deleted:

C:\Users\"user"\AppData\Local\cura\3.1

C:\Users\"user"\AppData\Roaming\cura\3.1

Is there another folder that I should delete?

No that are all the folders. What happens when you create a new custom profile? Does it show and work correctly then?

[amagro 3]

Yes, it's seems everything right.

[danilius 118]

That fix did not work for me, in fact it prevented the Octoprint plugin from showing up at all.

ERROR - OctoPrintPlugin.OctoPrintOutputDevice._startPrint [479]: An exception occurred in network connection: name 'global_container_stack' is not defined

Thanks for the report. I will fix this for the 3.1 final release. As a workaround for now, you can disable support for writing to the sdcard in the OctoPrint webinterface. After that you may have to connect to the octoprint instance again in Cura.

Update: Here's the fix: https://github.com/fieldOfView/OctoPrintPlugin/commit/d5414e

[ahoeben 1,948]

That fix did not work for me, in fact it prevented the Octoprint plugin from showing up at all.

Could you please test the 3.1 final that was released today?

(I think you might have copy/pasted the fix including the "+" at the beginning of the line, which is just meant to show that the respective line is added to the code; it should not actually be included in the code)

[ManuelW 2]

Hey there, Cura 3.1 (release) ignores my temperature settings for the nozzle.

Cura always set the temp to 220°C in the gcode file.