I was in the same situation recently. I was working on 3 projects and needed to switch between them because of the relative textures. The best thing to do is to use maxScript to set the project folder and sub folders. When you set the project folder through the interface it creates all the extra folders you don't need. But…
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;…
Huh, alright. So Project Folders is the way to go, but using MS to automate-out the extraneous crap. That works. It may not be hard for YOU to figure out the MaxScript, but I don't have the maxscript tools to create a sphere, let alone path setups, lol. Eager for your example!
Yeah, that makes sense. It's always the same 3 computers, so I can just use the correct MS on each machine, that way when I pick up a project, they're all relinked to the correct folders. Looks sweet, I'll test it out when I'm at the office. Thanks!
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…
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…