Bring me your bugs! Cura 14.02-RC2 ready for testing.

[drayson 75]

UPDATE:

RC7 has the same behavior as RC6 freezing when switching into layer view.

Here are the error message details:

Beschreibung:

Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren. (Programm can not communicate with Win any more)

Problemsignatur:

Problemereignisname: AppHangB1

Anwendungsname: pythonw.exe

Anwendungsversion: 0.0.0.0

Anwendungszeitstempel: 4df4b9cc

Absturzsignatur: b59b

Absturztyp: 0

Betriebsystemversion: 6.1.7601.2.1.0.768.3

Gebietsschema-ID: 3079

Zusätzliche Absturzsignatur 1: b59beffc26edbb7a3166a5c85035fb52

Zusätzliche Absturzsignatur 2: aab2

Zusätzliche Absturzsignatur 3: aab2d75d7bad18789dcff594c3e578cd

Zusätzliche Absturzsignatur 4: b59b

Zusätzliche Absturzsignatur 5: b59beffc26edbb7a3166a5c85035fb52

Zusätzliche Absturzsignatur 6: aab2

Zusätzliche Absturzsignatur 7: aab2d75d7bad18789dcff594c3e578cd

 

[Nicolinux 288]

Daid,

this is not a bug, but potentially annyoing for everyone so it might be a worthwhile UM2 firmware improvement. I am posting it here because it is related to Cura and because I hope it will make it into the very next release.

Filament temperature is too high while changing material.

This leads to strands of filament stuck inside the bowden tube or strands that end with a big blob that won't pass the knurled bolt inside the extruder. Every second filament change I have to fish it out with a toothpick.

Not sure which temperature would be best for PLA, but lower than 220° in any case. Maybe 190°?

 

[takei-naodar 0]

I would say even less.... i tried it with even 90.... still leaves a bit of a string... lets say 80 possible....

 

[Daid 306]

just tried the RC6 multiple printer's function. it is good, but seems the different machine share the same

start/end.gcode. Is it a bug or specific start/end.gcode for each machine is not support yet?

It should have different start/end code for each machine. But looks like I managed to bug that... I'll fix it soon.

I really wanna try your update but Cura keeps crashing when i click print from usb. What to do ? i deleted all old files of cura

But in the RC7 on MacOS, already fixed it.

 

[thomas-roager 0]

It should have different start/end code for each machine. But looks like I managed to bug that... I'll fix it soon.

But in the RC7 on MacOS, already fixed it.

i used RC7 but still doesn't work :/

 

[Nicolinux 288]

Hi,

there is a bug with the layer preview when "spiralize" is selected. The topmost layers look weird when scrolling through layers up and down.

 

[bbg 0]

RC 7 fails to slice an STL file which worked fine in prior 14.01 releases. Shows 0 time and trashes the layer view. File loads and looks fine in all other views. It's a copyright graphic file which I'm developing so I don't want to upload it but can send it privately if that would help.

Thanks for all your hard work.

Bruce

 

[Daid 306]

RC 7 fails to slice an STL file which worked fine in prior 14.01 releases. Shows 0 time and trashes the layer view. File loads and looks fine in all other views. It's a copyright graphic file which I'm developing so I don't want to upload it but can send it privately if that would help.

Thanks for all your hard work.

Bruce

You can email it to d.braam@ultimaker.com I'll keep it confidential.

 

[Daid 306]

i used RC7 but still doesn't work :/

"bug in RC7, fixed already for next release"

 

[thomas-roager 0]

"bug in RC7, fixed already for next release"

Ahh okay super.

 

[Daid 306]

You can email it to d.braam@ultimaker.com I'll keep it confidential.

 

It slices fine, but due to changes in the layer view it looks a bit messy for such a small object.

 

[Dim3nsioneer 557]

No, for some reason it's seeing COM3 as an USB serial port, which I'm not sure if it should in your case.

Cura reads the registry keys from "HARDWARE\\DEVICEMAP\\SERIALCOMM", and checks if there is an USBSER in there. It has done so for quite a while already, so I'm confused why it would show up COM3 all of a sudden if it did not before.

I've just overwritten machineCom.py with the present git version and now it works as it should... let's see for how long...

 

[maartenw 6]

I see that 14.03 is released on 17 march. So it is not a RC anymore.

It was not clear whether for XP a separate version was available, and the 14.03 version and the 14.03-for-XP had the same size. Anyway, the version indicated as 'for XP' was downloaded and installed.

Still the layer view sounds 'pling' and the program does not respond anymore.

No message is shown, so this is all I can report.

 

[maartenw 6]

Former 'pling' results for 14.02 were from a 'real' machine.

Installed 14.03 on a fresh VM with XPSP3, same 'pling' result. Here, OpenGL 1.1.0 was found.

Installed 14.03 on a fresh VM with W7, and layer view was OK. Here, OpenGL 2.1 was found.

The stl object was put 'swinging' to the platform, The layer view was 'building' up from the top, and I could watch the layers at all heights.

So is the problem caused by different OpenGL or by Windows version?

 

[Daid 306]

So is the problem caused by different OpenGL or by Windows version?

 

Most likely the OpenGL or VM combination.

 

[maartenw 6]

Problem solved in 14.05RC02 (same XP machine...) ! Thanks!