JE - Asset Pipeline Research NotesGeneral structure:

3 Main sections.

Art (for us this would be the place where all blender or maya files would be)

Some thoughts about this:

“Art” and “Inter” are comparable to the “work” and “publish” directory of Shotgrid. Maybe we should stay with those terms for consistency reasons (at least on the BabyGiant site, as there probably won’t be a Shotgrid pipeline on the Dark Bay site).

Mike Erwin (speaker in the video) recommends putting all of those folders into one single repository. The advantage of this is that one can always go back “to the project as it was 2 weeks ago” without the need to make sure that different repositories must be consistent for a certain time in the past.
- The repository could get realy heavy in size overall.
- But to play the game one [node] only would need to check out the Game-part of the repo, as all other files are not needed.
- When working on the babygiany site, we should only add work files to the repository that have been loaded into the unreal project at some point. (see image below)
  Note that the .uasset is losing its version when imported so we don’t have several versions inside the ue project itself.

Folder structure + naming conventions

Example folder structure for discussion: The work directory heavily builds upon the babygiant structure.

Babygiant could keep their ART/(work) folder inside their standard pipeline. This would prevent data redundency and sync problems. The Art folder would then be only versioned by Shotgrid, and the Inter and Game folder would then be only versioned by Perforce

Should the art folder always be synced from BGH to DB? What happens if Dark Bay changes something on an asset and we can’t keep track on our end.

Maybe we could make an “Art files” package at the end of a project, instead of this being a part of the repo from the beginning. This could also safe space on the repo.

SL_Foreground

SL_Midground

SL_Background

SL_LGT

SL_Characters

SL_Effects

SL_nDisplay