Difference between revisions of "Folder and File Structure"

From Sirikata Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
Most likely, you will be creating content for Sirikata with a group of artists.  While Sirikata is a great environment for solo work, it is important for organizational reasons to keep your content structured; if you are in a group project, it is imperative.  Because of this, it is highly suggested that you keep these folders at the top directory of your hard drive (C:).  An example path would be C:\sirikatacontent\.  This is so that if you transfer your files to another person in your group you will not run into any file path issues within 3ds Max or your other programs.  It also makes it easier for you to find files, as there is always a designated place for that file.  This system can potentially save you, or your group members, hours of work.
 +
 +
 +
== Sample Folder and File Structure ==
 +
 +
----
 +
 
/sirikata/
 
/sirikata/
 
* The system, platform, engine and everything once it is imported.
 
* The system, platform, engine and everything once it is imported.
Line 16: Line 23:
  
 
/sirikatacontent/ogreexports/
 
/sirikatacontent/ogreexports/
* where all exported scenes go, the folder of the export and its accompanying files (/ash_01/ash_01.scene ash_01/materials etc) These folders within are ready to be dragged directly into Sirikata.
+
* Where all exported scenes go, the folder of the export and its accompanying files (/ash_01/ash_01.scene ash_01/materials etc) These folders within are ready to be dragged directly into Sirikata.
  
  

Revision as of 02:19, 3 August 2009

Most likely, you will be creating content for Sirikata with a group of artists. While Sirikata is a great environment for solo work, it is important for organizational reasons to keep your content structured; if you are in a group project, it is imperative. Because of this, it is highly suggested that you keep these folders at the top directory of your hard drive (C:). An example path would be C:\sirikatacontent\. This is so that if you transfer your files to another person in your group you will not run into any file path issues within 3ds Max or your other programs. It also makes it easier for you to find files, as there is always a designated place for that file. This system can potentially save you, or your group members, hours of work.


Sample Folder and File Structure


/sirikata/

  • The system, platform, engine and everything once it is imported.


/sirikatacontent/documentation/

  • Where all documentation exists for Sirikata, Pipeline, Tutorials, etc.


/sirikatacontent/

  • Primary asset storage area for use by content designers, this resides separately and is before final import to Sirikata.


/sirikatacontent/mesh

  • The top directory for models. Every model will have its own folder within the directory.


/sirikatacontent/ogreexports/

  • Where all exported scenes go, the folder of the export and its accompanying files (/ash_01/ash_01.scene ash_01/materials etc) These folders within are ready to be dragged directly into Sirikata.


/sirikatacontent/textures

  • Finalized Textures ready for import, and to be used during material creation within Max.


/sirikatacontent/textures/TYPE

  • Type deliniates the type of texture, this is purely for ease of storage use for artists as once the export is complete, the texture resides within its corresponding mesh folder, under materials.


/sirikatacontent/texture_ref/

  • The massive folder utilized for working on textures, texture references, photos and all collage references for each project.


/sirikatacontent/projects

  • Each new folder will be the storage location for import directly into Sirikata. (Ex. /Kunst/ for the Speed Limits Kunst museum project).


/sirikatacontent/scripts/

  • Future useage for scripting, maybe CVS files can reside here?


/sirikatacontent/toolbox/

  • Not to be confused by Utilities, this is where we drop photoshop brushes, config files, palet files, etc.


/sirikatacontent/utilities/

  • All utilities that we are permitted to redistribute that are required by content designers (ogre exporter, dds plugin, etc)