That's what it's doing. I like to put the autoback files into a sub-directory and not just the root of the project. Actually the autoback line should be this, in order to make it project relative: pathConfig.SetDir #autoback "./autoback" But it'll work either way. I'm not sure what you mean by "pick up a project, and hit…
Here is the script that I run. I have one script saved for each project I'm working on and just use MaxScript | Run Script... command to execute the script. (Or you can drag the text to a toolbar to make a toolbar button.) I actually use relative autoback folders so that each project has it's own autoback files. I also had…
So this sets the project folder to C:/myproject (which I can point anyplace I want), sets the Autoback to wherever I want, and points the rest of the folders to "/myproject"? What is it doing different for Autoback than the rest of them? Or is this making C:/myproject/autoback, and then everything else just lives in a pile…
So, I work on one workstation at the office, plus a home desktop and a home laptop. I'm trying to figure out a setup to make working on projects on multiple systems more efficient. Currently, I've got Relative Paths turns on, and some common textures live in a Content folder inside of my project folder on each machine;…