โš™๏ธ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

CVars can be overridden by creating a ConsoleVariables.ini file in the same folder as the above config files, i.e. <Project Location>/Plugins/<Plugin Name>/Config/ConsoleVariables.ini and putting all the cvars under the section [WorldBuilder].

The contents should look like this with a list of the CVars to override:

[WorldBuilder]
r.ScreenPercentage=150
t.MaxFPS=120

Many CVars are read-only, and so adding them here will have no effect. If this is the case, a warning will be logged (you can also check for yourself by searching the codebase for the name of the CVar, and seeing if it has the ECVF_ReadOnly flag set).

You can also add CVars specific to device profile platforms:

; Disables GI globally unless using a G6 Full (GFN) device 
[WorldBuilder]
sg.GlobalIlluminationQuality=0

[Windows_G6Full WorldBuilder]
sg.GlobalIlluminationQuality=3

.sg scalability group configs are respected as defaults - once a user has changed their settings, their client cache values will be used instead.

Last updated