How do you handle shared property and instruments throughout a workforce and initiatives?

How do you handle shared property and instruments throughout a workforce and initiatives?

[ad_1]

As my workforce grows I am making an attempt to higher handle shared property in an organized method throughout the workforce. These property embrace:

  • Brushes and Alphas for Substance, Blender, Krita, and many others
  • Customized Plugins for Maya
  • Trim Sheets and tiling textures
  • Reference meshes and pictures
  • Helpful configs for content material creation softwares that keep consistency and adherence to our asset insurance policies
  • In-Home tooling that simplifies sure workflows
  • … and a lot extra…

The character of those property is that they don’t seem to be tied to any particular applications and all have their very own buildings. As such, it is not sufficient to only combine with an current engine’s market.

These are property which will generally be up to date, or expanded upon- they usually might have dependencies on different property, although in all probability not typically.

Our workforce composition contains round 20 people with a various set of abilities from the deeply technical to the aesthetic and visible (i.e. Software program devs, artists, and technical artists). For example of the place we’re at with our tooling- we have been capable of onboard everybody onto git for model management, together with our artists. Nevertheless, this was solely doable with using Github Desktop and Sourcetree git shoppers. We’re utilizing a self-hosted Gitea occasion to retailer all of our repositories. We use Notion for course of documentation, discord for workforce communication, and construct primarily for Unity. We now have a non-public npm bundle registry for Unity particular packages, and all different property we share both by attachments in Notion or simply by sending it immediately when requested.

It is that final half that’s woefully inadequate and I am hoping to get recommendation on. How do different gamedev groups of comparable measurement to ours deal with syncing property and instruments throughout their groups. What we’re doing now shouldn’t be scalable and the discoverability of those instruments and property is so dangerous that always individuals are redoing work once they do not must.

What workflows and processes are used to assist this want? Are there options on the market which can be simple to onboard for individuals of much less technical skillsets?

[ad_2]

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply