Skip to content

Game Jammer: Asset Bundling Instructions Won't Work using Installed Engine #2511

Open
@AMZN-Gene

Description

@AMZN-Gene

The Bundling Assets for Release docs doesn't apply for people that use pre-built installed O3DE.

Updates to Bundling Assets for Release

  1. Skip the step for building AssetBundler
    a. This already exists in the engine folder C:\O3DE\23.10.1\bin\Windows\profile\Default\AssetBundler.exe
  2. Opening AssetBundler.exe will fail.
    a. The error message is wrong in this case. Unable to locate the Project Cache path from Settings Registry at key /O3DE/Runtime/FilePaths/CacheProjectRootFolder. Please run the O3DE Asset Processor to generate a Cache and build assets. ![image](https://github.com/o3de/o3de.org/assets/32776221/622a84bc-cc5e-404b-86ce-9c131344d594) The problem is that AssetBundler.exe wasn't told which project to open. Solution: Run AssetBundler from command-line and provide the project-path argument. .\bin\Windows\profile\Default\AssetBundler.exe --project-path C:\Users\genewalt\O3DE\Projects\NewProject'
  3. Bundling Assets for Release only creates the PAK files. "Final notes" should point users to the next step of actually using the PAK files and creating a release game build. Project Export CLI Tool

Formatting Suggestion: Maybe the page should include a tab; 1 tab for installed o3de, 1 tab for built from source.

Updates to Creating a Project Game Release Layout for Windows

  1. Remove the warning about having to export when building the engine as source. Devs can export when using an installed engine now :)
    In order to create a game only release (monolithic), you must have O3DE set up from source, not just the installer.
  2. Are these steps even needed now that the export script exists? Provide a link to the Project Export CLI Tool

Updates to Project Export CLI Tool

  1. Ensure export-project script examples include --output-path, --seedlist, --platform
    Example: C:\O3DE\23.10.1\scripts\o3de.bat export-project --export-script C:\O3DE\23.10.1\scripts\o3de\ExportScripts\export_source_built_project.py --project-path C:\Users\genewalt\O3DE\Projects\NewProject --config release --should-build-assets --log-level INFO --seedlist C:\Users\genewalt\O3DE\Projects\NewProject\AssetBundling\SeedLists\GameSeedList.seed --output-path C:\GameJam --noserver --nounified --platform pc

BLOCKED: o3de/o3de#17192

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature/buildContent relating to CMake or the overall build system of O3DE.good-first-issueIssue ready for a new contributor according to the help wanted guidelines.kind/enhancementEnhancement to an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions