printer settings not persistent?
Posted: Sun Oct 26, 2014 6:27 pm
by Simon
Hi,
Could anyone tell me if it is normal that S3D keeps forgetting my printer settings? I have a Kossel, so I choose "other" when the program starts and manually set up the build area and so on. But I have to do this every time I start the program.
I think this should be stored somewhere, but it doesn't seem to be.
Running on Ubuntu.
BR Simon
Re: printer settings not persistent?
Posted: Sun Oct 26, 2014 6:53 pm
by TenKOhms
Sounds like a permission issue with some of the s3d setting files. try running the script in the last post of this thread:
http://forum.simplify3d.com/viewtopic.php?f=9&t=1258
Here's the actual post you should try:
New Link. Fingers Crossed
https://www.dropbox.com/s/btj05p9g9yyms ... hortcut.sh
If Not.
Make a file with this
#!/bin/bash
echo "Changing to Simplify3D Software Directory..."
cd /opt/Simplify3D-2.1.1
echo "Done."
echo "Allowing permissions..."
sudo chmod go+rwx Simplify3D
sudo chmod go+rwx libInterface.so
sudo chmod go+rwx LaunchScript.sh
echo "Done."
echo "Allowing user to access Serial Ports..."
sudo usermod -a -G dialout $USER
echo "Done."
echo "Checking for working directory..."
cd /home/$USER/.local/share
mkdir Simplify3D
mkdir Simplify3D/Creator
sudo chmod -R go+rwx Simplify3D
echo "mkdir complete."
echo "If you see mkdir fail, directory exists, this is normal."
echo "Script finished. Open the Simplify3D shortcut on the Desktop and... Happy printing! -Simplify3D Software Team."
Re: printer settings not persistent?
Posted: Mon Oct 27, 2014 1:35 am
by dhylands
I'm running Ubuntu 14.04 and at the end of the install, I said "yes" to launch Simlify3D now.
Unfortunately, that created ~/.config/Simplify3D/Creator.conf and the implify3D directory and the Creator.conf file were both owned by root.
It doesn't look like that script will fix that.
I posted the commands I used to fix things over here:
http://forum.simplify3d.com/viewtopic.p ... 1544#p5852
Re: printer settings not persistent?
Posted: Tue Oct 28, 2014 11:56 am
by Simon
It indeed was a problem with the permission of the configuration file. Solved. Thank you!