#Project Info Summary
3 messages in this thread
John:
The way we do it in production is to keep each project and it's files in a
separate directory on the network. That way, I know that for client X, all
his maps, projects, meshes, etc. are in one place and can be easily backed
up.
It also makes it easier to remember what is where!
Greg Pyros
Greg,
I do the same idea with my directory structure to ensure I know what pieces
are used together, when and to keep clients files seperate from other clients.
But, that is not my point. When a client looks at a fli file and wants to know
what 'settings' i used, I want an integrated way to tell them:
What rendering method was used
What anti-aliasing option was used
….all the info on the "render" dialog box.
Plus
Scene info about the materials
Plus
use your imagination…..
It stinks to have to keep a diary of renderings/materials/projetcs either on
paper or in a seperate file. This feature would allow people to be more
productive within the enviornment.
-John
John:
>> I want an integrated way to tell them:
>>
>> What rendering method was used
>> What anti-aliasing option was used
>> ….all the info on the "render" dialog box.
>> Plus Scene info about the materials
I agree, this would be good to have easy access to, but, as of today, just
remember that all this information is stored in the *.PRJ file, if you save
it just before you start rendering!
Greg Pyros