Project Folder Basics

[Geoffc]

I've never learned how to setup a max project correctly. I keep all my maps, 3d models (plants, cars) and material libraries in my Max directory. I have a separate Projects folder on my HD where I keep my cad and .max files. I've just gotten by by adding most of the maps and model directories to the 'external paths' in the path setup.

 

Now I believe that I'm supposed to use the File->Set Project Folder command to setup project specific subdirectories in each of my Project folders.

 

I guess then I copy over just the maps and 3d blocks that I'm using for an individual project to it's own subdirectories and save the .mxp file for it only? Or by having the "File I/O" set all to "relative" each project should always find it's own maps in its own sub-folders?

 

I realize that this is most basic, but is there a tutorial somewhere for understanding these paths and setup?

 

 

Here's my goal: I was thinking of either getting a network external drive to keep and host all my projects and their corresponding maps, blocks, files, etc. I want an easy way to setup DR in vray where any other computer in my small office can simply open up the same max file on this server, and it would use the "relative" links to find the maps and xrefs in the individual project sub-folders.

 

 

 

If anyone could help walk me through these basics, I'd really appreciate it!

[Tommy L]

I guess the biggest decision you have to make is how militant youre going to be about maps and materials. If i create a new material I like, I store it on the server in the central material library. The bitmaps in that material go into the material library map directory. Both the material library and the map library are sub-divided into relevent folders (concrete, wood etc).

Project specific maps, such as Irradience maps, site maps, one off textures, these are all contained in the job folder. Its on the server as well (nothing is local) but in a drive that can be archived without disturbing network tasks when the job is completed. Its maintaining the division between archivable and repeatedly usable that is the key. For my system anyway.

[Nils Norgren]

I think Thomas makes a good point, at our shop we have taken a different tact, we put all related files with the project, even if they are duplicated around the servers.

 

We use a series of .MXP files (that match our hierarchy), I have an updated list of Projects in a .txt file on the server, along with a Maxscript utility that looks at the text file, makes a pull down list of the projects, and then you hit a button and it loads the .MXP file for that project (loading the specific paths per project). You then can open and save from the "Scenes" file and when you hit render you will be dumped into the "Renders" folder, we attempt to keep all the associated files, Proxys, Maps, photometrics in the project.

 

Within asset tracker we can change the paths to "relative" and the whole project can be archived and restored to a new place without reliance on a heirarchy outside of the project.

 

This all is part of the pipeline that keeps things easy to move between offices, backups and archives.

 

-Nils

[Geoffc]

Thanks, those are both great responses.

 

I have a couple more follow ups:

 

Nils: If you keep your project specific materials/maps in the project folder, how do you get them there as you build the project? Does the manager or individual modeler pull them from a main directory and just physically copy them over using win explorer or something similar?

 

And for both of you, regarding keeping the projects and materials on a server, does this have any performance disadvantage as long as your are locally networked?

 

I guess my other main concern is using DR. Please tell me if this scenario would work: If I kept all my scenes on a net server under a project folder, and all my maps/materials on the server in a main storage area (sim to Tommy), and all projects used a generic mxp file that kept these maps folders listed in the external I/O and the rest set to relative, then I would start up max on the slaves, load the same mxp, and close, then start the vraydummy. Shouldn't the slaves find the correct maps for each project?

 

I'd experiment with this before asking, but don't yet have an external network drive to test.

[Nils Norgren]

If you keep your project specific materials/maps in the project folder, how do you get them there as you build the project? Does the manager or individual modeler pull them from a main directory and just physically copy them over using win explorer or something similar?

 

It is the artist's responsibility to move the items into the directory, we have a few of our own utilites to help, but it can be a problem, especially when people know about things from another project, they will merge models in from different directories (leaving any linked maps or proxies in the old directory). For the most part people are smart about it and keep it clean as they work. The main tool is the asset tracker.

 

And for both of you, regarding keeping the projects and materials on a server, does this have any performance disadvantage as long as your are locally networked?

 

There is a definite performance loss when working off servers, we are running aggegratted gig from the server to the switches and all gig networking to the workstations. People HAVE to work off the servers as they are backed up nightly to tapes, the workstations can be reformatted at a moment's notice if there is a problem (usually we have to save people's e-mail and that is it). If they work locally there are many risks, for-most among them is versioning.

 

More info than you asked for, but hope it helps when thinking about the pipeline (think about projects from inception to archive and back again).

 

-Nils

[Geoffc]

It is the artist's responsibility to move the items into the directory, we have a few of our own utilites to help, but it can be a problem, especially when people know about things from another project, they will merge models in from different directories (leaving any linked maps or proxies in the old directory).

 

-Nils

 

I know that feeling well, in architecture. One of the largest advantages of cad is to be able to use previous work in future projects. But more often than not people quickly copy details, notes and other drawings into a new project without verifying their applicability or correcting the file paths.