Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoexec.game.setreg not working correctly in release builds #17045

Open
yumigenack opened this issue Nov 11, 2023 · 2 comments
Open

Autoexec.game.setreg not working correctly in release builds #17045

yumigenack opened this issue Nov 11, 2023 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/core Categorizes an issue or PR as relevant to SIG Core triage/needs-information Indicates an issue needs more information in order to triage

Comments

@yumigenack
Copy link

I followed the instructions here:
https://www.docs.o3de.org/docs/user-guide/packaging/windows-release-builds/#set-the-starting-level

I think autoexec.game.setreg is either not included by asset bundler or doesn't work as intended in release builds because I get a grey screen (no initial level)
image

A workaround to load a level is to create a shortcut for the GameLauncher.exe and include it as a parameter:
"D:\O3DE Release Builds\HelloWorld\HelloWorld.GameLauncher.exe" -LoadLevel HelloWorld

@yumigenack yumigenack added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 11, 2023
@lemonade-dm lemonade-dm added sig/docs-community Categorizes an issue or PR as relevant to SIG Docs-Community. sig/core Categorizes an issue or PR as relevant to SIG Core triage/needs-information Indicates an issue needs more information in order to triage and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. sig/docs-community Categorizes an issue or PR as relevant to SIG Docs-Community. labels Nov 15, 2023
@lemonade-dm
Copy link
Contributor

If you are using the Asset Bundler should be creating an engine_pc.pak file that would contain a bootstrap.client.<config>.setreg file that contains the "/O3DE/Autoexec/ConsoleCommands/LoadLevel" key within it.

When the AssetProcessor run was there any errors triggered for the engine.json file when the Job Key was "Settings Registry"?
If the autoexec.game.setreg is ill-formed JSON it will not process. Ill-formed JSON could be caused by either missing double quotes around the value of the "LoadLevel" key or the setreg has a trailing comma.

You can validate whether the "/O3DE/Autoexec/ConsoleCommands/LoadLevel" key will be propagated to a bundled PAK file by examining your <project-root>/Cache/pc/bootstrap.client.release.setreg file.
That file is an merged JSON file that should contain the "LoadLevel" key within it.
image

I am assuming your autoexec.game.setreg file looks similar to as follows and is located underneath your <project-root>/Registry directory?

{
    "O3DE": {
        "Autoexec": {
            "ConsoleCommands": {
                "LoadLevel": "helloworld"
            }
        }
    }
}

@spham-amzn
Copy link
Contributor

Any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/core Categorizes an issue or PR as relevant to SIG Core triage/needs-information Indicates an issue needs more information in order to triage
Projects
None yet
Development

No branches or pull requests

3 participants