⚙️Editing Project Settings
Many project settings behave in an undefined way with World Builder. We remove these instances from the Project Settings UI inside the editor to help make this clear.
This is important as your deployed game will run in a different game environment from your editor, including its config settings.
Adding your own project settings overrides
You are able to do so using the standard Project Settings UI. If there is a setting you'd like to change that isn't visible, we recommend contacting your support engineer. We're working on making it clearer as to why some settings are disabled.
It is still possible to add settings to the project config file via the ini file directly but we do not encourage usage of this and should only be used when required.
How to override CVars per scalability group (recommended)
This process outlines how you can modify the existing scalability group settings. This allows users within your game to select an overall graphics settings from the game menu - where each setting represents a scalability group - but where the CVars set by that scalability group can deviate from our predefined base settings.
The base scalability group CVars can be found within <Editor Location>/Config/BaseScalability.ini for reference. Section headers are structured as [<section name>@<configuration variant>] where the configuration variants are the quality levels that the user is able to choose. For example, the [AntiAliasingQuality@0] section will define all the anti aliasing CVars to be applied when a user selects quality level 0
To override the CVars that will be applied when a user selects any quality level you can
Find or create the
<Project Location>/Config/DefaultScalability.iniconfig file for your project.Refer to the
<Editor Location>/Config/BaseScalability.iniconfig to locate the CVar you want to override.Copy the section header for the CVar you will be overriding and paste it into the
DefaultScalability.iniif it doesn't already exist.Copy the CVar(s) you want to override into
DefaultScalability.iniuner the appropriate section headers copied or located in step 3.Modify the values for those CVars.
After doing the above steps, you must re-upload your content and use the new content for the changes to take effect. Once that is done, the next time you launch a world with your new content, your users will be using the new quality settings with the custom CVars
Example usage
Assume I want my game to display cinematic quality shadows at the lower graphical settings. I can locate the BaseScalability.ini file and find the section header [ShadowQuality@Cine]. To ensure that the lowest quality setting show these same shadow settings I can copy and paste this section header and all CVars within it into <Project Location>/Config/DefaultScalability.ini for my project. Now after changing the quality level in the heaer to be 0, the lowest quality level will use these CVars and show cinematic shadows
DefaultScalability.ini
How to override CVars globally
CVars can be overridden by creating a DefaultConsoleVariables.ini file in the same folder as the project config files, i.e. <Project Location>/Config/DefaultConsoleVariables.ini and putting all the cvars under the section [WorldBuilder].
The contents should look like this with a list of the CVars to override:
Any scalability group CVar (starts with 'sg.') will only be overridden if the user has not made graphics settings changes, as those changes take priority. Any other CVar will apply if they are not marked read-only (CVar is marked with the ECVF_ReadOnly flag in the codebase).
When a CVar has no effect, a warning will be logged.
You can also add CVars specific to device profile platforms:
Last updated