Download

Best practices regarding handling of packages coming from the Marketplace

Hello

I have a few questions about best practices regarding handling of packages coming from the Marketplace.

Assume that your project is using a huge pack of assets from the Marketplace (say 10 GB of data).

  • Do you put the whole pack into source control?
  • Do you migrate only the assets you really use into your own project/subproject? (Even if there is a lot of them)
  • How do you handle modifications you do to the assets?
  • How do you handle updates of the package in the Marketplace? (Is that even a thing?)

Thank you for your advice

Since UE4 does not have a proper CMS we don’t have source control for art assets and instead assign each map to an owner who oversees the development of “that” map.

Internet based project.

Environments are built standalone and what ever package is required is added to that project.

As above yes

When the project is ready to be consolidated the “level” is migrated using the levels and it only migrates the assets used in the project

Using sublevels a level can be added to the mix and updated. When the persistent map is loaded the sublevel that was edited is included with out worrying that on -going changes will change as well.

Once consolidated the map owner can then decided what art assets have a common use and add it to the common asset pool. Since it is used in a given environment it ensures that what is added to the consolidated build is in use and not bloat the build with unused art.

Source control of art is done visually as the owner can see if something has gone wrong.