Is your feature request related to a problem? Please describe.
Currently, the command line args used to start the server and client executables are hardcoded to one set of flags. This means that if a given O3DE project uses different configuration, e.g., differently named .cfg files or a non-null renderer, the user needs to make code changes before they can deploy with modified flags.
Describe the solution you'd like
An easy way for the operator to configure the flags. Perhaps they could be passed in as a file, or specific flags on deploy could be used to toggle commonly used flags like --rhi or --console-command-file
Is your feature request related to a problem? Please describe. Currently, the command line args used to start the server and client executables are hardcoded to one set of flags. This means that if a given O3DE project uses different configuration, e.g., differently named .cfg files or a non-null renderer, the user needs to make code changes before they can deploy with modified flags.
Describe the solution you'd like An easy way for the operator to configure the flags. Perhaps they could be passed in as a file, or specific flags on
deploy
could be used to toggle commonly used flags like--rhi
or--console-command-file