Nerv

Yeah I got that. The gcode file is created fine if I don't try to load an ini file. Maybe I misunderstood you. From the post before: I took that to mean that the shipped version of CuraEngine is able to parse ini files directly. If I misunderstood you: - Is there a way to do translate the ini files to CuraEngine config files easily? - Or are there plans to re-implement the missing command line functionality in Cura >2.1.2? --------------------------------- BTW: My use case is that I first use and iterate in cura with the gui. But once I lock down the printer settings for a certain part I use a small script to render it in the future (even if there are slight changes in the stl), as I have various parts I print again and again, but many with somewhat different printer settings. No Idea how common this scenario is, but it works great with version control. Using Ultimaker 2; recently upgraded to 2+

I am trying to better automate the build of various parts using CuraEngine directly. At the moment I do this by using cura: cura \-i part1.ini \-o part1.gcode \-s part1.stl I want to switch to using CuraEngine directly for automated builds since the needed command line options seem to be missing on the new Cura rewrite (Cura-2.1.2). So how exactly can I use the shipped version of CuraEngine with the ini files? I can't seem to get it to work (cura 15.04.06; ubuntu 16.04). /usr/share/cura/CuraEngine -c part1.ini -o part1.gcode part1.stl gives the following error: Default config 'default.cfg' not usedConfig(part1.ini): Line 1: No key value pair foundFailed to read config 'part1.ini'Failed to open part1.gcode for output.