The HeroEngine Art Pipeline allows for the transfer of art from your artists, to a Repository database, from which the art is available to the HeroBlade client that your developers use to build worlds.
This page gives a very simple overview of how the Art Pipeline works.https://account.heroengine.com/downloads/
What the artist does
- Artist creates art in various different formats, such as:
- The in-process art is stored on the Art_Depot
- When ready, the artist uses the Current Exporter Package to export the art into the format used by HeroEngine.
- The artist uses the Repository Browser client, to copy the formatted art to the Repository
What the game designer does
Once the art is in the Repository in the proper format, it is accessible to the game designers in a variety of ways, such as:
- The game designer can import some art (such as models and SpeedTrees) into the Asset Library
- This opens the Repository File Selector (a different kind of Repository browser)
- The game designer can also access textures in the Repository, from things such as the Terrain Panel, or a Properties Panel of an asset such as a Billboard.
- The game designer uses the Create Menu and the Asset Library to create instantiations of art assets in the game world.
In the Engine infrastructure:
- The artist's Repository Browser client is used to transfer art to the Repository Dude Manager process, which stores the art in the Repository database.
- The game designer's Repository File Selector communicates with the HeroBlade client, which then communicates with the Repository Server dynamic process. The Repository Server process accesses the information in the Repository database, and passes it back to the Client. Note that the HeroBlade client does not always need to send a request to the Repository Server, as once it is downloaded, art will be available in the Local Repository Cache.
The process of requests being generated from HeroBlade can be observed via the Repository Requests panel, which will display all currently outstanding requests. To see the request process in action:
- Open the Repository Request Panel
- Go to an area that you have not yet visited
- Requests should flow through the panel. Once each request is filled, it is removed from the panel. Requests that appear and disappear rapidly, are probably being filled from the LRC (Local Repository Cache). Requests that "sit" for a few seconds are probably waiting for download from the Repository.
For a more extreme example, you could Purge your local repository cache. This will then force a re-download of everything (Note: this may take some time, several minutes to a couple hours, depending on the speed of your connection).
How it works for players
As a player moves through the world, art is rendered from what is stored in their Local Repository Cache. As they move into new areas, if any new art is not yet on the player's system, their Client sends a request to the Repository, and new art is downloaded as-needed.