-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Removed the loading of the legacy system_<platform>_<asset_platform>.cfg
files
#13721
Removed the loading of the legacy system_<platform>_<asset_platform>.cfg
files
#13721
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question, are all the settings being deleted already set up somewhere in .setreg
files? If not, do they need to be added?
78cd066
to
c966a9d
Compare
|
Question, do developers with an already created project have any additional work to do when this is merged? Should the developers switch these values on their previously created levels, or will the be updated automatically? |
I am adding settings registry files that invoke these console commands in the |
`system_<platform>_<asset_platform>.cfg` files The settings registry has replaced the loading of platform specific setreg files using the Platform Abstraction Layer to determine platform specific folders. This is detailed in the documentation [here](https://www.o3de.org/docs/user-guide/settings/developer-documentation/#specialization-system-in-depth) The settings registry can also issue console commands which is described on the [Issue Console Commands](https://www.o3de.org/docs/user-guide/settings/issue-az-console-commands/) page Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com>
… AZ CVars Adding Settings Registry files for setting console variable values that modify the windows layout to replicate the existing settings from the old `system_<platform>_<asset_platform>.cfg` files Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com>
c966a9d
to
55faa40
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Might save a little bit of startup time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simplifies LyTestTools, thanks!
aec52ae
to
3a57189
Compare
The test tools were setting the `log_RemoteConsoleAllowedAddresses` console variable, through those settings files and they have been updated to specify those values through the command line arguments. For Android test tools launcher, that console variable is set through the Settings Registry '/O3DE/Autoexec/ConsoleCommands/log_RemoteConsoleAllowedAddresses' mechanism. Also removed the validation of the `system_<platform>_<asset>.cfg` from the CMake layout tool `verify_layout` method as it is no longer needed. Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com>
3a57189
to
04ab7e6
Compare
The settings registry has replaced the loading of platform specific setreg files using the Platform Abstraction Layer to determine platform specific folders.
This is detailed in the documentation
here
The settings registry can also issue console commands which is described on the Issue Console
Commands page
Signed-off-by: lumberyard-employee-dm 56135373+lumberyard-employee-dm@users.noreply.github.com