Customizing Default Project File Structure

[Anonymous]

I wonder if is possible to customize the
sub-directories names that are being created
automatically right after a new project created from
inside of Flame.
The folling proejct’s file structure is created by default:

../Project/My_Project_Name/
/action
/audio
/paint/autopaint
.
.
.
/..
/timewarp
/wipe

I thought the configuration template files (such as
pal.cfg or ntsc.cfg) are responsible for it. But it
looks like the context of *.cfg file has no effect on
project’s sub-directories creature.
Are there any environment variables or any other
settings that tell what directories Flame creates
initiating a new project?
What would be a procedure to
add/replace/remove/customize project’s sub-directory?
Let’s say, I want a sub-directory ~/Reference_Images
in addition to the default sub-directories inside
every project being created. Or I would like to
customize the location of sub-directory /Brushes by
moving it to /usr/all_My_Brushes/ directory.
Thanks in advance!

[guillem ramisa]

Yeah, how do you guys do it? Do you keep projects locally on every machine and share that directory over the network or do you have a dedicated server for all projects for easier access and backup? If so it would be nice to be able to change the default pathway when creating projects. So you don’t have to do that manually everytime.

[Shane]

Hey all,

Best way I’ve seen this done is to be networked to a server. A system admin sets it up so that when a project and it’s folders are created on the server, empty directorys are createded that mirror a projects folder in discreet. We have the networked automounted at root in the discreet systems and book marked in all the menus like action and import / export image ect…

We at one time bypassed in the config’s the discreets projects and went directly to the server. This was a bit nasty because if more than one person were accessing say a batch file the autoback that gets saved was constantly overwriting each others. It also became very easy to destroy setups accidently. last note was that it caused the sytem to hang and you had to unmount the server to reboot if the server went down.

For all personal setups and custom brushes each artist either used the default project or created one localy to save those type of things. We were also assigned a folder on the server with our names.

Hope that helps.

[guillem ramisa]

pokeitwithastick wrote:

Hey all,

Best way I’ve seen this done is to be networked to a server. A system admin sets it up so that when a project and it’s folders are created on the server, empty directorys are createded that mirror a projects folder in discreet. We have the networked automounted at root in the discreet systems and book marked in all the menus like action and import / export image ect…

We at one time bypassed in the config’s the discreets projects and went directly to the server. This was a bit nasty because if more than one person were accessing say a batch file the autoback that gets saved was constantly overwriting each others. It also became very easy to destroy setups accidently. last note was that it caused the sytem to hang and you had to unmount the server to reboot if the server went down.

For all personal setups and custom brushes each artist either used the default project or created one localy to save those type of things. We were also assigned a folder on the server with our names.

Hope that helps.

Interresting. Anyone else using different solutions?

[Author]

Posts