Slic3r at command line doesn't care about bed shape from configuration

I'm having a problem with my Rostock Slic3r configuration or with it's behaviour.
When I slice stl-files from Slic3r running in gui mode everything is working as it should.
When slicing the same file from commandline with the same configuration exported to a single config.ini and then loaded at execution time the coordinates won't be as I think they should.

My graphic setting for the printers bed is:

Bed shape:
Shape: Rectangular
Size: x:180 y:180
Origin: x:90 y:90

And when exported to the config.ini that is converted to the line:

bed_shape = -90x-90,90x-90,90x90,-90x90

If I add the parameter "--print-center 0,0" to the command it will correct the error but I don't think it's meant to be like that or..?
As I can see it is only the bed configuration that is handled wrong.
Please have a look in the gcode produced by each method and let me know if you can find out how to solve this problem.

Thank You!

I compared the gcode, and the "cli_..." file looks like it's not for a delta.
The GUI one does tho, you can see that it's going back and forth over the origin (0,0), from x-49 to x49 for example.

If you have a Rostock/Delta then the bed center is supposed to be 0,0, so "--print-center 0,0" sounds like a good option.
I don't know why it didn't get your 0,0 origin from the INI file tho. Perhaps it didn't use the INI file.

Perhaps you should post your command line, and attach the INI.

I've not used the command line, so I may not be able to help with that, but perhaps someone else will be able to...

---

My printer: Raptosaur - Large Format Delta - [www.paulwanamaker.wordpress.com]
Can you answer questions about Calibration, Printing issues, Mechanics? Write it up and improve the Wiki!

Thank you for your answer!

Quote
Paul Wanamaker
Perhaps you should post your command line, and attach the INI.

Yes, of course. That slipped my mind
The command line is:
~/proj/Slic3r/bin/slic3r --output ~/tmp/cli_cube_100x2x2.gcode ~/proj/3d/stl/cube_100x2x2.stl --load ~/.Slic3r/config.ini

If you have a look in both of the gcode files you can see in the end of them that they are using the same settings.

Thank you!

It depends on your OS, but are you sure that "/.Slic3r/config.ini" is the correct path (rather than e.g. "~/Slic3r/config.ini" or "./Slic3r/config.ini")?

Dave

"~/.Slic3r/config.ini" is the correct path for the file.