- User Since
- Oct 13 2015, 9:16 AM (105 w, 1 d)
Tue, Oct 17
Mon, Oct 16
Sun, Oct 15
Fri, Oct 13
@victor_larchenko : Could you look at plugin and try to fix it, please?
Thu, Oct 12
Wed, Oct 11
Mon, Oct 9
@marcio, @karrad : The right firmware is already in Cura2, all @victor_larchenko needs to do is to add it here:
Fri, Oct 6
@tranter : Thanks for the log file, very useful. Please try the most recent build for MAC I think I have this sleep function crash fixed (but not the functionality of preventing the sleep)
As far as
@victor_larchenko: Correction it seems that only mouse scrollwheel action in LayerView is triggering this (at least when the model is not sliced yet).
@victor_larchenko : On my gento box (with Qt5.9 also) the same action just completely hangs GPU btw. So it's really a bug in shaders or QML most probably.
@victor_larchenko : After looking at it a bit more, the problem there is not resolved with the cache clearing
Thu, Oct 5
hb_font_funcs_set_font_h_extents_func is a part of
You'll need to install
@Yahuba : Could you re-check if 2.6.38 MAC build has PyObjc in it now?
Also make sure you followed this: https://www.lulzbot.com/learn/tutorials/cura-lulzbot-edition-installation-debian , https://www.lulzbot.com/learn/tutorials/cura-lulzbot-edition-installation-ubuntu and https://www.lulzbot.com/learn/tutorials/cura-lulzbot-edition-installation-windows
@Yahuba , make sure that you directly connecting printer and computer via USB cable. No USB switches should be used.
ICU was disabled for Qt build in 2.6.37 on MAC and LIN, please try it out.
Wed, Oct 4
Tue, Oct 3
Mon, Oct 2
@victor_larchenko : Th scroll-wheel works now, but we've lost the ability to change active sliders with mouse click and also clicking on checkboxes doesn't work now.
Fri, Sep 29
@victor_larchenko : I think we should scroll the "active" slider (the one that is pointed by layer number indicator box (it can be top, bottom and middle).
Thu, Sep 28
This is probably a wrong place for repo creation requests, so closing this ticket.
@victor_larchenko : I can confirm this bug, described above. Most probably the bug is in CuraEngine.
@victor_larchenko : I think the best way to handle this problem so far is to move all of the materials from this repo into Cura2 repo (like we are doing right now with our material) and then I will remove this repo from build script.
@victor_larchenko , attached is the build for stretch:
@victor_larchenko : This bug is most probably a race condition, for some reason material_part_removal_temperature='material_part_removal_temperature' initially and this is what got passed as the float value,
then later on the float value got written and by the time GUI appears it works as normal. The easiest fix is to test if v is actually float (and not a string) before trying to round it in rU6435d7487ca0.
@victor_larchenko: I think I heard @Yahuba mentioning that serial drivers are not working for Win7 only, but it works for Win10. In any case one would need corresponding cura log output to figure out what is wrong.
@victor_larchenko: I see that cura is actually creating
Tue, Sep 26
Fri, Sep 22
Wed, Sep 20
Tue, Sep 19
@victor_larchenko: I'm using Haswell (i5-4570S) So I still think the problem is in how Cura2 handles 'material_part_removal_temperature' value...
Sep 18 2017
@victor_larchenko : The above didn't help, the error that appearing after adding float(v):
@victor_larchenko: So the numbers should be converted to float before rounding:
@karrad: The above procedure correctly setting buildplate temperature for me on 2.6.29.