Lumberyard
User Guide (Version 1.16)

Building Game Assets for iOS Games

This feature is in preview release and is subject to change.

When you build an iOS game in Lumberyard, you must first build the assets that are included with the application. All built assets are located in the cache folder of your Lumberyard installation. For example, when you build the Samples Project, the assets are saved to the lumberyard_version\dev\cache\SamplesProject\ios directory. The initial build of the Samples Project assets may take up to an hour to process, but incremental changes should process almost instantly.

Note

If you make changes to your game in Lumberyard Editor on a Windows system, you must copy the updated assets to a macOS system using your preferred method. For example, you can use source control. For information, see Using the Perforce Plugin with Lumberyard.

To build iOS game assets on a macOS system

  1. On your macOS system, close all instances of the Asset Processor.

  2. Edit the bootstrap.cfg file (located in the lumberyard_version/dev directory) to set sys_game_folder to SamplesProject (or the project you want to build). Save the file.

  3. Edit the AssetProcessorPlatformConfig.ini file (located in the lumberyard_version/dev directory) to uncomment ios=enabled (remove the preceding semicolon) and to comment out pc=enabled (add a preceding semicolon). Save the file.

  4. In a command line window, navigate to the lumberyard_version/dev/BinMac64 directory and run the Asset Processor (GUI or batch version) to process and build your game assets.

    Note

    Symbolic links are not supported when you use the Asset Processor on macOS. To ensure that the Asset Processor works properly on macOS, follow these guidelines:

    • Do not use a symbolic link for your cache directory when you store compiled assets in a central location.

    • Do not store your source project assets in a symbolic link directory.

    • Use a unique cache directory. Do not share the cache directory with a Windows system that is also running the Asset Processor.