DaHai8

Did you see my reply on one of your other of many duplicate posts you made on this subject? Keep your question to a single post and it'll easier to keep track of...

Those may be 'reversed faces'. Green colors indicate an inside facing wall. Reverse faces in Sketchup show up in dark grey. In Meshmixer they show up as striped pink/red faces. Not sure how other 3d modeling problems show that. Most times it does not affect the print, Cura can compensate, but you might want to check/fix it anyway.

The only issue I have with auto-slicing is that it can occasionally hang if I don't let it finish before doing another scale,rotate,move, etc... And once it's hung (hanged?) the only way to fix it is to exit Cura and restart it. That can suck if I've just placed a lot of items on the build plate and have to do it all over again. That's where a 'Save Layout' would be nice... Just my 2c

Well, I don't know what command line you are using that results in your 'Config(part1.ini): Line 1:No key value pair found" error. I don't know what part1.ini file is from your set up. I also didn't know how to do any of this until just over a few hours ago when I saw your post and decided to see if I could figure it out for myself. So I'm no expert. But I did get it working to a degree. In addition, I'm using Cura 15.04.4 which is newer than yours and so yours may contain bugs that are hampering your progress. All that said, from following the -'help' switch output from CuraEngine, the most basic slicing command for .stl in and .gcode out would be: CuraEngine.exe -o c:\path\to\output.gcode c:\path\to\input.stl If you wish to supply an .ini file for your printer's setting, you need to: File / Save Profile in the Cura GUI and then use that .ini file on the command line in Cura: CuraEngine.exe -c c:\path\to\profile.ini -o c:\path\to\output.gcode c:\path\to\input.stl However, I have been unable to get the CuraEngine to read the .ini file. It always returns this error: Not sure if your older version of Cura will work on reading the .ini or not.

I don't know why you're doing: CuraEngine -s "C:\Path\to\file.stl" That's not what the -s switch does. Following the CuraEngine usage help works fine for me.

For Cura 15.04.4 (and probably 14.x.x.), Enter: CuraEngine.exe -help For Cura 2.1.2, Enter: CuraEngine.exe help Those will show you the command line parameters for both versions of the CuraEngine.exe program.

Ok, I think I got the answer to my primary question: I did not get auto-updated/upgraded. I just now restarted Cura to make sure all the settings where still there/correct/etc. (which they were) and got a little window says "A new version of Cura is available!". So clearly I was not upgraded....so what happened that caused it to forget everything and act like a fresh install? puzzling....

Strange behavior from Cura this evening: I started it up by double-clicking an .stl file, like I usually do, Comura Articulatum from Thingiverse, and Cura launched like it was a fresh install on my laptop! It gave me some quick hint windows, a little welcome to Cura and made me choose a printer. Thankfully, my Aurora A3 was still in the list - whew! But it came up in 'Simple" setup mode (I never use Simple mode). So I switched to 'Advanced' and all the settings I had made visible before were gone :( Then I noticed I had 2 Aurora A3 Printers in my 'Printers:' selection. The second was set for ABS (I never print in ABS). So I removed that one. Went in and re-enabled all the 'Setting Visibility' items and AFAICT none of my presets were lost: speed, infill, raft parms, etc. and even my custom print bed .stl still shows. Oddly, the version still says 2.1.2, so if I was auto-upgraded, the version number wasn't changed. No harm, no foul. Just odd and a little worrisome for a moment. Does Cura auto-upgrade now? Or did it just lose its marbles this time?

I'm thinking you're printing at .2mm Layer Height and .3mm Initial Layer Height. This tends to offset the layers by .1mm accounting for the runover from 1.6mm to 1.7mm. Two things to try: 1. Print at .1mm layer height (better quality prints, but twice the print time) 2. Set .2mm Initial Layer Height. You may have issues getting the prints to stick to the bed pending on your printer, filamant, bed adhesion type...

Here is a basic Cura Printer Profile maker: https://quillford.github.io/CuraProfileMaker/ These advanced instructions should help you set up a json file for your printer if the basic one is not suffient: https://ultimaker.com/en/resources/20511-change-machine-settings

That could work, but Cura continually extrudes the filament across layers, it does not reset the extruder position at the start of each layer (like some other nameless slicers). You would need to use G92 Exxx.xxxx gcode to set the extruder position to same value as the first G1/G0 E value used in the second gcode file. Otherwise you'll probably get meters of filament ejected as it tries to 'catch-up' to the second gcode silced at a higher infill rate.

Well, to paraphrase Barbie "Math is hard" , so I wrote a new plugin: Pause at Layer Ok, basically I just took Pause at Height and modified it to work off Cura GUI Layer numbers instead of Z mm values.... For anyone interested, I'm happy to share the code here or anywhere it is appropriate to do so. Just let me know. Example print: I didn't get all the Black out of the print head before printing with Golden, so there's a bit of a bleed-in between the two. My bad, not the plugin's.

Then add a raft and its another variable to factor in. Question is, why should we have to?

Riddle me this: Why do the Cura Screen Layers start at 1 while the gCode Layers start at 0 (zero)? Why does the "Pause at Height" Post Processing Extension use millimeters instead of Layer Numbers? Basically, the way it stands right now, if I want to pause the print at a particular height to change filament I must: 1. Enable Layer View in Cura and note the layer number I want to print with the new color on. 2. Subtract 1 from that because gcode layers numbers start at 0 while Cura layers start at 1 3. Save the gcode out to disk. 4. Search for that Layer # and write down the Z height it prints at 5. Delete the gcode save in step 3 6. Go back into Cura and edit the Pause at Height to insert the correct Z height in MM 7. Save the gCode again and print it. I'm thinking that if Cura starting number layers in the Layer view at 0 and the Pause at Height plugin used layer numbers, it would make swapping filament and the like a whole lot easier. Or am I missing something supidfyingly obvious?

Have you tried any of the Cura included json files? Because it sounds like the one you got from facebook is either corrupt or incomplete or not compatible.

OK. Grasping at straws here and gonna shotgun it (metaphor mashup): 1. Try uninstalling and then re-installing, but run install as Administrator. 2. Try uninstalling and then install 2.1.1 3. Try turning off windows firewall and then run it. Because...why not 4. Try turning off your antivirus and running it. Again... because... 5. Try running it in Win7 compatibility mode (assuming you've been forced to win10 by micro$oft) 6. If your on 64bit windows try installing the 32 bit version. These are all things I'd try if I were in your shoes.

Try Cura "Run as Administrator". That's the recommended solution to when internet explorer has that problem.

Sounds like there may be another window (probably an error alert) that got covered up and has the input focus, so no other window will accept input. Have you tried Alt+Tab or Windows+Tab to see if there is another hidden window? Can you move any of the windows around to see if anything got covered up? Then there's always the default: Try updating your Display Adapter drivers.

I have this issue too, but it doesn't seem to effect my prints because my cooler is 3mm up from the nozzle tip: The print head moves from home to the start position of the raft. Its at the proper Z height and travels around the perimeter of the raft but doesn't extrude any filament for at least 30mm or more. Its trying to extrude, but the nozzle is not pre-primed. Now I have an incomplete perimeter of the raft as it starts printing the surface lines. Because there is missing perimeter on part of the raft, those edges tend to curl up. A possible fix: In the Start gCode there is this: G1 F200 E3 ;extrude 3mm of feed stock Try increasing the E value. Maybe 5 or more until you get your nozzle properly primed for when it starts printing the raft perimeter. The Start gCode is on the Start/End-Gcode tab in Cura 15.x

Here's a link to a pretty detailed Calibration Guide: http://reprap.org/wiki/Triffid_Hunter%27s_Calibration_Guide After that, you can adjust layer heights, nozzle and bed temperatures, and print speeds to dial in the best settings for you printer and the filament material. P.S. Hereis a Print Troubleshooting guide for specific print issues. It may help as well: http://reprap.org/wiki/Print_Troubleshooting_Pictorial_Guide

Yipes! Looks like over extrusion. Do you have Retraction enabled? How about 'Enable Combing' under Travel? Or perhaps your print head is too hot and its oooooozing...

I tried it with my RepRap style Printer, and it omitted the M106 command from the gcode when I unchecked that box. So it could be machine/json file dependent. Also, look through that fan-off gcode for M106 to ensure its in there or not. Also, does the fan turn on immediately or after printing the first few layers? P.S. I just tested it with the Ultimaker Original printer profile and the M106 255 is on ;Layer:1 with the Fan enabled and nowhere in the gcode when I uncheck the 'Enable Cooling Fans' box. Let us know what you find.

Removing my reply. I didn't read nallath's comment correctly

The center-point of rotation is at the center of the object currently selected (or center of the Object Group currently selected). You may have to deselect and then re-select the object to enable this as it does not always seems to track if you transform the object. Then your object won't float out of frame when you rotate/zoom the build window.

I think the order of the points in the polygon are wrong. Plotting those out, in the order given in the json file produces a bow-tie like object. I think the points should be in this order: -75,35 -75,-18 18,-18 18,35