Rejutka

Heh, yeah, but it's more like "If I enable this rendering, half the fonts look ugly. If I disable it, the other half looks ugly." My problem is I don't like it when the characters are fuzzy at the edges, which ClearType mostly produces - except in a few cases where it improves the edges... It's a better result than I would have hoped, so I'm quite satisfied. To know what the issue is helps even if it doesn't solve anything. (Weird how the mind works.)

Yep, that's the issue. Unfortunatly enabling ClearType would change all the other text in a way I don't like :-/ Still, thanks for clearing the issue.

Minor issue: font in menu looks weird. The screenshot somehow looks better than the actual program, but I think it's still noticeable - especially compared to old Cura: I'm using Windows 7 64Bit, ClearType is disabled. I've tried to see if someone else had this already, but apparently there is no search in thread function? Or I simply missed it... (Also, I realize this is a very minor issue compared to things like retraction problems or having to maintain dozens of profiles. But it's what jumped into my eye when I started Cura 2.1 and it's something I find highly annoying, to the point of actually not using a program if it's too much. It's not too bad in Cura, though. Or rather, Cura is important enough to endure it. I know I've seen this before in other programs, so I blame Windows.)

(Using 15.4.3 on Windows 7) Not sure if this should be an idea or a question. If there is a way to disable this, it's a question (where?). If there is no way to disable it, it's a suggestion (add it). With more words: Currently the Cura Splash screen stays in the foreground even if one changes the focus to another program. This is, at least for me, highly annoying. Cura takes some time to start (no idea why) and I'd like to not just sit and stare at the screen while it does so. The program that has focus works fine and everything - but I don't see much of it...

I have a similar issue. Maybe it's the same, I believe I have found the reason for it. My issue: I'm printing a very small object, each layer takes not even a second (so claims Cura). For some reason, Cura is adding code that moves the head to the side, extrudes a bit, then moves back extruding some more. When viewing the GCode with Repetier Host, I can see the extranous head movements. They make no sense model-wise, as they're about 2 CM from the model. I have looked at the GCode and noticed weird G0 codes - immediately before a new layer. When I set the minimal layer time to 0, the resulting GCode contains no extra movements. But when I set it back to 5 seconds, the extra movements/extrusions appear. Not sure if this is intended, but it almost looks like Cura is expecting there to be a wipe tower? I can't upload GCode files apparently, so here's snippets of the file, containing one layer each (same STL, same settings, apart from delay):

I'm using Cura - should have mentioned that... What I mean by resetting is the code that moves the printhead to the 0/0/0 position, moves Z up a bit, extrudes some filament, then moves to the start point of the print. How does the program decide wether it is a single or dual extrusion? Number of materials used? Or machine settings? If I have a machine set up as dual extruder, and only use one material - which coding is used?

As I understand it - please correct me if wrong - there is a start.gcode for every extruder, which is called in sequence, for every extruder used in the print. Which means that if I have a dual extruder, and the code to center/reset the printhead is in the start2.gcode, it is only called if the second nozzle/extruder is actually used! Which caused the printhead to almost slam into the right wall since it wasn't centered on 0 (I never bother to do this, as the gcode should contain that information). I'm assuming there is an easy workaround for this already, like putting the reset code in start.gcode instead of start2.gcode (although I suppose then it wouldn't be called if one only used the other extruder?). Moving it to another section would make most sense, though (IMO), since in my case, I used a predefined configuration, never even thinking about the details until I tried to print a single color model.

Great as cura is, it's bothersome that whenever I change the size of a model, it immediately starts to recalculate the printing time - I haven't even finished deleting the previous numbers, and it already starts, almost freezing my computer. Couldn't it wait until I leave the input field? Sorry to start posting with a complaint - but you know how it is - most people don't bother complaining about things that don't really interest them :-)