Contains global variables accessible from everywhere. Contains global variables accessible from everywhere. Use [method get_setting], [method set_setting] or [method has_setting] to access them. Variables stored in [code]project.godot[/code] are also loaded into ProjectSettings, making this object very useful for reading custom game configuration options. When naming a Project Settings property, use the full path to the setting including the category. For example, [code]"application/config/name"[/code] for the project name. Category and property names can be viewed in the Project Settings dialog. [b]Feature tags:[/b] Project settings can be overridden for specific platforms and configurations (debug, release, ...) using [url=$DOCS_URL/tutorials/export/feature_tags.html]feature tags[/url]. [b]Overriding:[/b] Any project setting can be overridden by creating a file named [code]override.cfg[/code] in the project's root directory. This can also be used in exported projects by placing this file in the same directory as the project binary. Overriding will still take the base project settings' [url=$DOCS_URL/tutorials/export/feature_tags.html]feature tags[/url] in account. Therefore, make sure to [i]also[/i] override the setting with the desired feature tags if you want them to override base project settings on all platforms and configurations. https://godotengine.org/asset-library/asset/675 https://godotengine.org/asset-library/asset/125 https://godotengine.org/asset-library/asset/677 Adds a custom property info to a property. The dictionary must contain: - [code]name[/code]: [String] (the property's name) - [code]type[/code]: [int] (see [enum Variant.Type]) - optionally [code]hint[/code]: [int] (see [enum PropertyHint]) and [code]hint_string[/code]: [String] [b]Example:[/b] [codeblocks] [gdscript] ProjectSettings.set("category/property_name", 0) var property_info = { "name": "category/property_name", "type": TYPE_INT, "hint": PROPERTY_HINT_ENUM, "hint_string": "one,two,three" } ProjectSettings.add_property_info(property_info) [/gdscript] [csharp] ProjectSettings.Singleton.Set("category/property_name", 0); var propertyInfo = new Godot.Collections.Dictionary { {"name", "category/propertyName"}, {"type", Variant.Type.Int}, {"hint", PropertyHint.Enum}, {"hint_string", "one,two,three"}, }; ProjectSettings.AddPropertyInfo(propertyInfo); [/csharp] [/codeblocks] Clears the whole configuration (not recommended, may break things). Returns the order of a configuration value (influences when saved to the config file). Returns the value of a setting. [b]Example:[/b] [codeblocks] [gdscript] print(ProjectSettings.get_setting("application/config/name")) [/gdscript] [csharp] GD.Print(ProjectSettings.GetSetting("application/config/name")); [/csharp] [/codeblocks] Returns the absolute, native OS path corresponding to the localized [code]path[/code] (starting with [code]res://[/code] or [code]user://[/code]). The returned path will vary depending on the operating system and user preferences. See [url=$DOCS_URL/tutorials/io/data_paths.html]File paths in Godot projects[/url] to see what those paths convert to. See also [method localize_path]. [b]Note:[/b] [method globalize_path] with [code]res://[/code] will not work in an exported project. Instead, prepend the executable's base directory to the path when running from an exported project: [codeblock] var path = "" if OS.has_feature("editor"): # Running from an editor binary. # `path` will contain the absolute path to `hello.txt` located in the project root. path = ProjectSettings.globalize_path("res://hello.txt") else: # Running from an exported project. # `path` will contain the absolute path to `hello.txt` next to the executable. # This is *not* identical to using `ProjectSettings.globalize_path()` with a `res://` path, # but is close enough in spirit. path = OS.get_executable_path().get_base_dir().plus_file("hello.txt") [/codeblock] Returns [code]true[/code] if a configuration value is present. Loads the contents of the .pck or .zip file specified by [code]pack[/code] into the resource filesystem ([code]res://[/code]). Returns [code]true[/code] on success. [b]Note:[/b] If a file from [code]pack[/code] shares the same path as a file already in the resource filesystem, any attempts to load that file will use the file from [code]pack[/code] unless [code]replace_files[/code] is set to [code]false[/code]. [b]Note:[/b] The optional [code]offset[/code] parameter can be used to specify the offset in bytes to the start of the resource pack. This is only supported for .pck files. Returns the localized path (starting with [code]res://[/code]) corresponding to the absolute, native OS [code]path[/code]. See also [method globalize_path]. Returns [code]true[/code] if the specified property exists and its initial value differs from the current value. Returns the specified property's initial value. Returns [code]null[/code] if the property does not exist. Saves the configuration to the [code]project.godot[/code] file. [b]Note:[/b] This method is intended to be used by editor plugins, as modified [ProjectSettings] can't be loaded back in the running app. If you want to change project settings in exported projects, use [method save_custom] to save [code]override.cfg[/code] file. Saves the configuration to a custom file. The file extension must be [code].godot[/code] (to save in text-based [ConfigFile] format) or [code].binary[/code] (to save in binary format). You can also save [code]override.cfg[/code] file, which is also text, but can be used in exported projects unlike other formats. Sets the specified property's initial value. This is the value the property reverts to. Sets the order of a configuration value (influences when saved to the config file). Sets the value of a setting. [b]Example:[/b] [codeblocks] [gdscript] ProjectSettings.set_setting("application/config/name", "Example") [/gdscript] [csharp] ProjectSettings.SetSetting("application/config/name", "Example"); [/csharp] [/codeblocks] This can also be used to erase custom project settings. To do this change the setting value to [code]null[/code]. Background color for the boot splash. If [code]true[/code], scale the boot splash image to the full window size (preserving the aspect ratio) when the engine starts. If [code]false[/code], the engine will leave it at the default pixel size. Path to an image used as the boot splash. If left empty, the default Godot Engine splash will be displayed instead. [b]Note:[/b] Only effective if [member application/boot_splash/show_image] is [code]true[/code]. If [code]true[/code], displays the image specified in [member application/boot_splash/image] when the engine starts. If [code]false[/code], only displays the plain color specified in [member application/boot_splash/bg_color]. If [code]true[/code], applies linear filtering when scaling the image (recommended for high-resolution artwork). If [code]false[/code], uses nearest-neighbor interpolation (recommended for pixel art). This user directory is used for storing persistent data ([code]user://[/code] filesystem). If left empty, [code]user://[/code] resolves to a project-specific folder in Godot's own configuration folder (see [method OS.get_user_data_dir]). If a custom directory name is defined, this name will be used instead and appended to the system-specific user data directory (same parent folder as the Godot configuration folder documented in [method OS.get_user_data_dir]). The [member application/config/use_custom_user_dir] setting must be enabled for this to take effect. The project's description, displayed as a tooltip in the Project Manager when hovering the project. Icon used for the project, set when project loads. Exporters will also use this icon when possible. Icon set in [code].icns[/code] format used on macOS to set the game's icon. This is done automatically on start by calling [method DisplayServer.set_native_icon]. The project's name. It is used both by the Project Manager and by exporters. The project name can be translated by translating its value in localization files. The window title will be set to match the project name automatically on startup. [b]Note:[/b] Changing this value will also change the user data folder's path if [member application/config/use_custom_user_dir] is [code]false[/code]. After renaming the project, you will no longer be able to access existing data in [code]user://[/code] unless you rename the old folder to match the new project name. See [url=$DOCS_URL/tutorials/io/data_paths.html]Data paths[/url] in the documentation for more information. Specifies a file to override project settings. For example: [code]user://custom_settings.cfg[/code]. See "Overriding" in the [ProjectSettings] class description at the top for more information. [b]Note:[/b] Regardless of this setting's value, [code]res://override.cfg[/code] will still be read to override the project settings. If [code]true[/code], the project will save user data to its own user directory (see [member application/config/custom_user_dir_name]). This setting is only effective on desktop platforms. A name must be set in the [member application/config/custom_user_dir_name] setting for this to take effect. If [code]false[/code], the project will save user data to [code](OS user data directory)/Godot/app_userdata/(project name)[/code]. If [code]true[/code], the project will use a hidden directory ([code].godot[/code]) for storing project-specific data (metadata, shader cache, etc.). If [code]false[/code], a non-hidden directory ([code]godot[/code]) will be used instead. [b]Note:[/b] Restart the application after changing this setting. [b]Note:[/b] Changing this value can help on platforms or with third-party tools where hidden directory patterns are disallowed. Only modify this setting if you know that your environment requires it, as changing the default can impact compatibility with some external tools or plugins which expect the default [code].godot[/code] folder. Icon set in [code].ico[/code] format used on Windows to set the game's icon. This is done automatically on start by calling [method DisplayServer.set_native_icon]. If [code]true[/code], disables printing to standard error. If [code]true[/code], this also hides error and warning messages printed by [method @GlobalScope.push_error] and [method @GlobalScope.push_warning]. See also [member application/run/disable_stdout]. Changes to this setting will only be applied upon restarting the application. If [code]true[/code], disables printing to standard output. This is equivalent to starting the editor or project with the [code]--quiet[/code] command line argument. See also [member application/run/disable_stderr]. Changes to this setting will only be applied upon restarting the application. If [code]true[/code], flushes the standard output stream every time a line is printed. This affects both terminal logging and file logging. When running a project, this setting must be enabled if you want logs to be collected by service managers such as systemd/journalctl. This setting is disabled by default on release builds, since flushing on every printed line will negatively affect performance if lots of lines are printed in a rapid succession. Also, if this setting is enabled, logged files will still be written successfully if the application crashes or is otherwise killed by the user (without being closed "normally"). [b]Note:[/b] Regardless of this setting, the standard error stream ([code]stderr[/code]) is always flushed when a line is printed to it. Changes to this setting will only be applied upon restarting the application. Debug build override for [member application/run/flush_stdout_on_print], as performance is less important during debugging. Changes to this setting will only be applied upon restarting the application. Forces a delay between frames in the main loop (in milliseconds). This may be useful if you plan to disable vertical synchronization. If [code]true[/code], enables low-processor usage mode. This setting only works on desktop platforms. The screen is not redrawn if nothing changes visually. This is meant for writing applications and editors, but is pretty useless (and can hurt performance) in most games. Amount of sleeping between frames when the low-processor usage mode is enabled (in microseconds). Higher values will result in lower CPU usage. Path to the main scene file that will be loaded when the project runs. Audio buses will disable automatically when sound goes below a given dB threshold for a given time. This saves CPU as effects assigned to that bus will no longer do any processing. Audio buses will disable automatically when sound goes below a given dB threshold for a given time. This saves CPU as effects assigned to that bus will no longer do any processing. Default [AudioBusLayout] resource file to use in the project, unless overridden by the scene. Specifies the audio driver to use. This setting is platform-dependent as each platform supports different audio drivers. If left empty, the default audio driver will be used. If [code]true[/code], microphone input will be allowed. This requires appropriate permissions to be set when exporting to Android or iOS. The mixing rate used for audio (in Hz). In general, it's better to not touch this and leave it to the host operating system. Safer override for [member audio/driver/mix_rate] in the Web platform. Here [code]0[/code] means "let the browser choose" (since some browsers do not like forcing the mix rate). Specifies the preferred output latency in milliseconds for audio. Lower values will result in lower audio latency at the cost of increased CPU usage. Low values may result in audible cracking on slower hardware. Audio output latency may be constrained by the host operating system and audio hardware drivers. If the host can not provide the specified audio output latency then Godot will attempt to use the nearest latency allowed by the host. As such you should always use [method AudioServer.get_output_latency] to determine the actual audio output latency. [b]Note:[/b] This setting is ignored on all versions of Windows prior to Windows 10. Safer override for [member audio/driver/output_latency] in the Web platform, to avoid audio issues especially on mobile devices. Setting to hardcode audio delay when playing video. Best to leave this untouched unless you know what you are doing. The default compression level for gzip. Affects compressed scenes and resources. Higher levels result in smaller files at the cost of compression speed. Decompression speed is mostly unaffected by the compression level. [code]-1[/code] uses the default gzip compression level, which is identical to [code]6[/code] but could change in the future due to underlying zlib updates. The default compression level for Zlib. Affects compressed scenes and resources. Higher levels result in smaller files at the cost of compression speed. Decompression speed is mostly unaffected by the compression level. [code]-1[/code] uses the default gzip compression level, which is identical to [code]6[/code] but could change in the future due to underlying zlib updates. The default compression level for Zstandard. Affects compressed scenes and resources. Higher levels result in smaller files at the cost of compression speed. Decompression speed is mostly unaffected by the compression level. Enables [url=https://github.com/facebook/zstd/releases/tag/v1.3.2]long-distance matching[/url] in Zstandard. Largest size limit (in power of 2) allowed when compressing using long-distance matching with Zstandard. Higher values can result in better compression, but will require more memory when compressing and decompressing. If [code]true[/code], logs all output to files. Desktop override for [member debug/file_logging/enable_file_logging], as log files are not readily accessible on mobile/Web platforms. Path to logs within the project. Using an [code]user://[/code] path is recommended. Specifies the maximum amount of log files allowed (used for rotation). If [code]true[/code], enables warnings when a constant is used as a function. If [code]true[/code], enables warnings when deprecated keywords are used. If [code]true[/code], enables warnings when an empty file is parsed. If [code]true[/code], enables specific GDScript warnings (see [code]debug/gdscript/warnings/*[/code] settings). If [code]false[/code], disables all GDScript warnings. If [code]true[/code], scripts in the [code]res://addons[/code] folder will not generate warnings. If [code]true[/code], enables warnings when using a function as if it was a property. If [code]true[/code], enables warnings when a ternary operator may emit values with incompatible types. If [code]true[/code], enables warnings when dividing an integer by another integer (the decimal part will be discarded). If [code]true[/code], enables warnings when passing a floating-point value to a function that expects an integer (it will be converted and lose precision). If [code]true[/code], enables warnings when using a property as if it was a function. If [code]true[/code], enables warnings when calling a function without using its return value (by assigning it to a variable or using it as a function argument). Such return values are sometimes used to denote possible errors using the [enum Error] enum. If [code]true[/code], enables warnings when defining a local or subclass member variable, signal, or enum that would have the same name as a built-in function or global class name, which possibly shadow it. If [code]true[/code], enables warnings when defining a local or subclass member variable that would shadow a variable at an upper level (such as a member variable). If [code]true[/code], enables warnings when calling an expression that has no effect on the surrounding code, such as writing [code]2 + 2[/code] as a statement. If [code]true[/code], enables warnings when calling a ternary expression that has no effect on the surrounding code, such as writing [code]42 if active else 0[/code] as a statement. If [code]true[/code], all warnings will be reported as if they were errors. If [code]true[/code], enables warnings when using a variable that wasn't previously assigned. If [code]true[/code], enables warnings when assigning a variable using an assignment operator like [code]+=[/code] if the variable wasn't previously assigned. If [code]true[/code], enables warnings when unreachable code is detected (such as after a [code]return[/code] statement that will always be executed). If [code]true[/code], enables warnings when using an expression whose type may not be compatible with the function parameter expected. If [code]true[/code], enables warnings when performing an unsafe cast. If [code]true[/code], enables warnings when calling a method whose presence is not guaranteed at compile-time in the class. If [code]true[/code], enables warnings when accessing a property whose presence is not guaranteed at compile-time in the class. If [code]true[/code], enables warnings when a signal is unused. If [code]true[/code], enables warnings when a local variable is unused. If [code]true[/code], enables warnings when assigning the result of a function that returns [code]void[/code] to a variable. Message to be displayed before the backtrace when the engine crashes. Maximum number of frames per second allowed. The actual number of frames per second may still be below this value if the game is lagging. If [member display/window/vsync/vsync_mode] is set to [code]Enabled[/code] or [code]Adaptive[/code], it takes precedence and the forced FPS number cannot exceed the monitor's refresh rate. See also [member physics/common/physics_ticks_per_second]. This setting is therefore mostly relevant for lowering the maximum FPS below VSync, e.g. to perform non-real-time rendering of static frames, or test the project under lag conditions. [b]Note:[/b] This property is only read when the project starts. To change the rendering FPS cap at runtime, set [member Engine.target_fps] instead. Maximum call stack allowed for debugging GDScript. Maximum amount of functions per frame allowed when profiling. Print frames per second to standard output every second. Print more information to standard output when running. It displays information such as memory leaks, which scenes and resources are being loaded, etc. This can also be enabled using the [code]--verbose[/code] or [code]-v[/code] command line argument, even on an exported project. See also [method OS.is_stdout_verbose] and [method @GlobalScope.print_verbose]. Maximum call stack in visual scripting, to avoid infinite recursion. Color of the contact points between collision shapes, visible when "Visible Collision Shapes" is enabled in the Debug menu. Sets whether 2D physics will display collision outlines in game when "Visible Collision Shapes" is enabled in the Debug menu. Maximum number of contact points between collision shapes to display when "Visible Collision Shapes" is enabled in the Debug menu. Color of the collision shapes, visible when "Visible Collision Shapes" is enabled in the Debug menu. Color of the disabled navigation geometry, visible when "Visible Navigation" is enabled in the Debug menu. Color of the navigation geometry, visible when "Visible Navigation" is enabled in the Debug menu. Custom image for the mouse cursor (limited to 256×256). Hotspot for the custom mouse cursor image. Position offset for tooltips, relative to the mouse cursor's hotspot. If [code]true[/code], allows HiDPI display on Windows, macOS, Android, iOS and HTML5. If [code]false[/code], the platform's low-DPI fallback will be used on HiDPI displays, which causes the window to be displayed in a blurry or pixelated manner (and can cause various window management bugs). Therefore, it is recommended to make your project scale to [url=$DOCS_URL/tutorials/viewports/multiple_resolutions.html]multiple resolutions[/url] instead of disabling this setting. [b]Note:[/b] This setting has no effect on Linux as DPI-awareness fallbacks are not supported there. If [code]true[/code], keeps the screen on (even in case of inactivity), so the screensaver does not take over. Works on desktop and mobile platforms. The default screen orientation to use on mobile devices. See [enum DisplayServer.ScreenOrientation] for possible values. [b]Note:[/b] When set to a portrait orientation, this project setting does not flip the project resolution's width and height automatically. Instead, you have to set [member display/window/size/viewport_width] and [member display/window/size/viewport_height] accordingly. If [code]true[/code], the home indicator is hidden automatically. This only affects iOS devices without a physical home button. Forces the main window to be always on top. [b]Note:[/b] This setting is ignored on iOS, Android, and HTML5. Forces the main window to be borderless. [b]Note:[/b] This setting is ignored on iOS, Android, and HTML5. Sets the main window to full screen when the project starts. Note that this is not [i]exclusive[/i] fullscreen. On Windows and Linux, a borderless window is used to emulate fullscreen. On macOS, a new desktop is used to display the running project. Regardless of the platform, enabling fullscreen will change the window size to match the monitor's size. Therefore, make sure your project supports [url=$DOCS_URL/tutorials/rendering/multiple_resolutions.html]multiple resolutions[/url] when enabling fullscreen mode. [b]Note:[/b] This setting is ignored on iOS, Android, and HTML5. Allows the window to be resizable by default. [b]Note:[/b] This setting is ignored on iOS and Android. Sets the game's main viewport height. On desktop platforms, this is also the initial window height. Sets the game's main viewport width. On desktop platforms, this is also the initial window width. On desktop platforms, sets the game's initial window height. [b]Note:[/b] By default, or when set to 0, the initial window height is the [member display/window/size/viewport_height]. This setting is ignored on iOS, Android, and HTML5. On desktop platforms, sets the game's initial window width. [b]Note:[/b] By default, or when set to 0, the initial window width is the viewport [member display/window/size/viewport_width]. This setting is ignored on iOS, Android, and HTML5. Sets the VSync mode for the main game window. See [enum DisplayServer.VSyncMode] for possible values and how they affect the behavior of your application. Depending on the platform and used renderer, the engine will fall back to [code]Enabled[/code], if the desired mode is not supported. When creating node names automatically, set the type of casing in this project. This is mostly an editor setting. What to use to separate node name from number. This is mostly an editor setting. The command-line arguments to append to Godot's own command line when running the project. This doesn't affect the editor itself. It is possible to make another executable run Godot by using the [code]%command%[/code] placeholder. The placeholder will be replaced with Godot's own command line. Program-specific arguments should be placed [i]before[/i] the placeholder, whereas Godot-specific arguments should be placed [i]after[/i] the placeholder. For example, this can be used to force the project to run on the dedicated GPU in a NVIDIA Optimus system on Linux: [codeblock] prime-run %command% [/codeblock] Text-based file extensions to include in the script editor's "Find in Files" feature. You can add e.g. [code]tscn[/code] if you wish to also parse your scene files, especially if you use built-in scripts which are serialized in the scene files. Search path for project-specific script templates. Godot will search for script templates both in the editor-specific path and in this project-specific path. Default value for [member ScrollContainer.scroll_deadzone], which will be used for all [ScrollContainer]s unless overridden. If [code]true[/code], swaps Cancel and OK buttons in dialogs on Windows and UWP to follow interface conventions. Path to a custom [Theme] resource file to use for the project ([code]theme[/code] or generic [code]tres[/code]/[code]res[/code] extension). Path to a custom [Font] resource to use as default for all GUI elements of the project. If set to [code]true[/code], default font uses 8-bit anitialiased glyph rendering. See [member FontData.antialiased]. Default font hinting mode. See [member FontData.hinting]. Default font glyph sub-pixel positioning mode. See [member FontData.subpixel_positioning]. Timer setting for incremental search in [Tree], [ItemList], etc. controls (in milliseconds). Timer for detecting idle in [TextEdit] (in seconds). Default delay for tooltips (in seconds). Default [InputEventAction] to confirm a focused button, menu or list item, or validate input. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to discard a modal or pending input. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to move down in the UI. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to go to the end position of a [Control] (e.g. last item in an [ItemList] or a [Tree]), matching the behavior of [constant KEY_END] on typical desktop UI systems. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to focus the next [Control] in the scene. The focus behavior can be configured via [member Control.focus_next]. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to focus the previous [Control] in the scene. The focus behavior can be configured via [member Control.focus_previous]. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to go to the start position of a [Control] (e.g. first item in an [ItemList] or a [Tree]), matching the behavior of [constant KEY_HOME] on typical desktop UI systems. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to move left in the UI. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to go down a page in a [Control] (e.g. in an [ItemList] or a [Tree]), matching the behavior of [constant KEY_PAGEDOWN] on typical desktop UI systems. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to go up a page in a [Control] (e.g. in an [ItemList] or a [Tree]), matching the behavior of [constant KEY_PAGEUP] on typical desktop UI systems. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to move right in the UI. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. Default [InputEventAction] to select an item in a [Control] (e.g. in an [ItemList] or a [Tree]). [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. If no selection is currently active, selects the word currently under the caret in text fields. If a selection is currently active, deselects the current selection. [b]Note:[/b] Currently, this is only implemented in [TextEdit], not [LineEdit]. Default [InputEventAction] to move up in the UI. [b]Note:[/b] Default [code]ui_*[/code] actions cannot be removed as they are necessary for the internal logic of several [Control]s. The events assigned to the action can however be modified. If [code]true[/code], key/touch/joystick events will be flushed just before every idle and physics frame. If [code]false[/code], such events will be flushed only once per process frame, between iterations of the engine. Enabling this can greatly improve the responsiveness to input, specially in devices that need to run multiple physics frames per visible (process) frame, because they can't run at the target frame rate. [b]Note:[/b] Currently implemented only on Android. Specifies the tablet driver to use. If left empty, the default driver will be used. Override for [member input_devices/pen_tablet/driver] on Windows. If [code]true[/code], sends mouse input events when tapping or swiping on the touchscreen. If [code]true[/code], sends touch input events when clicking or dragging the mouse. Default delay for touch events. This only affects iOS devices. The locale to fall back to if a translation isn't available in a given language. If left empty, [code]en[/code] (English) will be used. If [code]true[/code], text server break iteration rule sets, dictionaries and other optional data are included in the exported project. [b]Note:[/b] "ICU / HarfBuzz / Graphite" text server data includes dictionaries for Burmese, Chinese, Japanese, Khmer, Lao and Thai as well as Unicode Standard Annex #29 and Unicode Standard Annex #14 word and line breaking rules. Data is about 4 MB large. [b]Note:[/b] "Fallback" text server does not use additional data. If non-empty, this locale will be used when running the project from the editor. Double vowels in strings during pseudolocalization to simulate the lengthening of text due to localization. The expansion ratio to use during pseudolocalization. A value of [code]0.3[/code] is sufficient for most practical purposes, and will increase the length of each string by 30%. If [code]true[/code], emulate bidirectional (right-to-left) text when pseudolocalization is enabled. This can be used to spot issues with RTL layout and UI mirroring that will crop up if the project is localized to RTL languages such as Arabic or Hebrew. Replace all characters in the string with [code]*[/code]. Useful for finding non-localizable strings. Prefix that will be prepended to the pseudolocalized string. Replace all characters with their accented variants during pseudolocalization. Skip placeholders for string formatting like [code]%s[/code] or [code]%f[/code] during pseudolocalization. Useful to identify strings which need additional control characters to display correctly. Suffix that will be appended to the pseudolocalized string. If [code]true[/code], enables pseudolocalization for the project. This can be used to spot untranslatable strings or layout issues that may occur once the project is localized to languages that have longer strings than the source language. [b]Note:[/b] This property is only read when the project starts. To toggle pseudolocalization at run-time, use [member TranslationServer.pseudolocalization_enabled] instead. Force layout direction and text writing direction to RTL for all locales. Specifies the [TextServer] to use. If left empty, the default will be used. Optional name for the 2D navigation layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 2D navigation layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 2D navigation layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 2D navigation layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 2D navigation layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 2D navigation layer 14. If left empty, the layer will display as "Layer 14". Optional name for the 2D navigation layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 2D navigation layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 2D navigation layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 2D navigation layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 2D navigation layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 2D navigation layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 2D navigation layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 2D navigation layer 21. If left empty, the layer will display as "Layer 21". Optional name for the 2D navigation layer 22. If left empty, the layer will display as "Layer 22". Optional name for the 2D navigation layer 23. If left empty, the layer will display as "Layer 23". Optional name for the 2D navigation layer 24. If left empty, the layer will display as "Layer 24". Optional name for the 2D navigation layer 25. If left empty, the layer will display as "Layer 25". Optional name for the 2D navigation layer 26. If left empty, the layer will display as "Layer 26". Optional name for the 2D navigation layer 27. If left empty, the layer will display as "Layer 27". Optional name for the 2D navigation layer 28. If left empty, the layer will display as "Layer 28". Optional name for the 2D navigation layer 29. If left empty, the layer will display as "Layer 29". Optional name for the 2D navigation layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 2D navigation layer 30. If left empty, the layer will display as "Layer 30". Optional name for the 2D navigation layer 31. If left empty, the layer will display as "Layer 31". Optional name for the 2D navigation layer 32. If left empty, the layer will display as "Layer 32". Optional name for the 2D navigation layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 2D navigation layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 2D navigation layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 2D navigation layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 2D navigation layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 2D navigation layer 9. If left empty, the layer will display as "Layer 9". Optional name for the 2D physics layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 2D physics layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 2D physics layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 2D physics layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 2D physics layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 2D physics layer 14. If left empty, the layer will display as "Layer 14". Optional name for the 2D physics layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 2D physics layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 2D physics layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 2D physics layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 2D physics layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 2D physics layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 2D physics layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 2D physics layer 21. If left empty, the layer will display as "Layer 21". Optional name for the 2D physics layer 22. If left empty, the layer will display as "Layer 22". Optional name for the 2D physics layer 23. If left empty, the layer will display as "Layer 23". Optional name for the 2D physics layer 24. If left empty, the layer will display as "Layer 24". Optional name for the 2D physics layer 25. If left empty, the layer will display as "Layer 25". Optional name for the 2D physics layer 26. If left empty, the layer will display as "Layer 26". Optional name for the 2D physics layer 27. If left empty, the layer will display as "Layer 27". Optional name for the 2D physics layer 28. If left empty, the layer will display as "Layer 28". Optional name for the 2D physics layer 29. If left empty, the layer will display as "Layer 29". Optional name for the 2D physics layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 2D physics layer 30. If left empty, the layer will display as "Layer 30". Optional name for the 2D physics layer 31. If left empty, the layer will display as "Layer 31". Optional name for the 2D physics layer 32. If left empty, the layer will display as "Layer 32". Optional name for the 2D physics layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 2D physics layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 2D physics layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 2D physics layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 2D physics layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 2D physics layer 9. If left empty, the layer will display as "Layer 9". Optional name for the 2D render layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 2D render layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 2D render layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 2D render layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 2D render layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 2D render layer 14. If left empty, the layer will display as "Layer 14". Optional name for the 2D render layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 2D render layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 2D render layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 2D render layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 2D render layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 2D render layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 2D render layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 2D render layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 2D render layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 2D render layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 2D render layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 2D render layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 2D render layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 2D render layer 9. If left empty, the layer will display as "Layer 9". Optional name for the 3D navigation layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 3D navigation layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 3D navigation layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 3D navigation layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 3D navigation layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 3D navigation layer 14. If left empty, the layer will display as "Layer 14". Optional name for the 3D navigation layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 3D navigation layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 3D navigation layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 3D navigation layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 3D navigation layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 3D navigation layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 3D navigation layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 3D navigation layer 21. If left empty, the layer will display as "Layer 21". Optional name for the 3D navigation layer 22. If left empty, the layer will display as "Layer 22". Optional name for the 3D navigation layer 23. If left empty, the layer will display as "Layer 23". Optional name for the 3D navigation layer 24. If left empty, the layer will display as "Layer 24". Optional name for the 3D navigation layer 25. If left empty, the layer will display as "Layer 25". Optional name for the 3D navigation layer 26. If left empty, the layer will display as "Layer 26". Optional name for the 3D navigation layer 27. If left empty, the layer will display as "Layer 27". Optional name for the 3D navigation layer 28. If left empty, the layer will display as "Layer 28". Optional name for the 3D navigation layer 29. If left empty, the layer will display as "Layer 29". Optional name for the 3D navigation layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 3D navigation layer 30. If left empty, the layer will display as "Layer 30". Optional name for the 3D navigation layer 31. If left empty, the layer will display as "Layer 31". Optional name for the 3D navigation layer 32. If left empty, the layer will display as "Layer 32". Optional name for the 3D navigation layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 3D navigation layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 3D navigation layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 3D navigation layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 3D navigation layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 3D navigation layer 9. If left empty, the layer will display as "Layer 9". Optional name for the 3D physics layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 3D physics layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 3D physics layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 3D physics layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 3D physics layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 3D physics layer 14. If left empty, the layer will display as "Layer 14". Optional name for the 3D physics layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 3D physics layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 3D physics layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 3D physics layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 3D physics layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 3D physics layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 3D physics layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 3D physics layer 21. If left empty, the layer will display as "Layer 21". Optional name for the 3D physics layer 22. If left empty, the layer will display as "Layer 22". Optional name for the 3D physics layer 23. If left empty, the layer will display as "Layer 23". Optional name for the 3D physics layer 24. If left empty, the layer will display as "Layer 24". Optional name for the 3D physics layer 25. If left empty, the layer will display as "Layer 25". Optional name for the 3D physics layer 26. If left empty, the layer will display as "Layer 26". Optional name for the 3D physics layer 27. If left empty, the layer will display as "Layer 27". Optional name for the 3D physics layer 28. If left empty, the layer will display as "Layer 28". Optional name for the 3D physics layer 29. If left empty, the layer will display as "Layer 29". Optional name for the 3D physics layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 3D physics layer 30. If left empty, the layer will display as "Layer 30". Optional name for the 3D physics layer 31. If left empty, the layer will display as "Layer 31". Optional name for the 3D physics layer 32. If left empty, the layer will display as "Layer 32". Optional name for the 3D physics layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 3D physics layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 3D physics layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 3D physics layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 3D physics layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 3D physics layer 9. If left empty, the layer will display as "Layer 9". Optional name for the 3D render layer 1. If left empty, the layer will display as "Layer 1". Optional name for the 3D render layer 10. If left empty, the layer will display as "Layer 10". Optional name for the 3D render layer 11. If left empty, the layer will display as "Layer 11". Optional name for the 3D render layer 12. If left empty, the layer will display as "Layer 12". Optional name for the 3D render layer 13. If left empty, the layer will display as "Layer 13". Optional name for the 3D render layer 14. If left empty, the layer will display as "Layer 14" Optional name for the 3D render layer 15. If left empty, the layer will display as "Layer 15". Optional name for the 3D render layer 16. If left empty, the layer will display as "Layer 16". Optional name for the 3D render layer 17. If left empty, the layer will display as "Layer 17". Optional name for the 3D render layer 18. If left empty, the layer will display as "Layer 18". Optional name for the 3D render layer 19. If left empty, the layer will display as "Layer 19". Optional name for the 3D render layer 2. If left empty, the layer will display as "Layer 2". Optional name for the 3D render layer 20. If left empty, the layer will display as "Layer 20". Optional name for the 3D render layer 3. If left empty, the layer will display as "Layer 3". Optional name for the 3D render layer 4. If left empty, the layer will display as "Layer 4". Optional name for the 3D render layer 5. If left empty, the layer will display as "Layer 5". Optional name for the 3D render layer 6. If left empty, the layer will display as "Layer 6". Optional name for the 3D render layer 7. If left empty, the layer will display as "Layer 7". Optional name for the 3D render layer 8. If left empty, the layer will display as "Layer 8". Optional name for the 3D render layer 9. If left empty, the layer will display as "Layer 9". Godot uses a message queue to defer some function calls. If you run out of space on it (you will see an error), you can increase the size here. This is used by servers when used in multi-threading mode (servers and visual). RIDs are preallocated to avoid stalling the server requesting them on threads. If servers get stalled too often when loading resources in a thread, increase this number. The policy to use for unhandled Mono (C#) exceptions. The default "Terminate Application" exits the project as soon as an unhandled exception is thrown. "Log Error" logs an error message to the console instead, and will not interrupt the project execution when an unhandled exception is thrown. [b]Note:[/b] The unhandled exception policy is always set to "Log Error" in the editor, which also includes C# [code]tool[/code] scripts running within the editor as well as editor plugin code. Default cell size for 2D navigation maps. See [method NavigationServer2D.map_set_cell_size]. Default edge connection margin for 2D navigation maps. See [method NavigationServer2D.map_set_edge_connection_margin]. Default cell size for 3D navigation maps. See [method NavigationServer3D.map_set_cell_size]. Default edge connection margin for 3D navigation maps. See [method NavigationServer3D.map_set_edge_connection_margin]. Maximum amount of characters allowed to send as output from the debugger. Over this value, content is dropped. This helps not to stall the debugger connection. Maximum number of errors allowed to be sent from the debugger. Over this value, content is dropped. This helps not to stall the debugger connection. Maximum amount of messages in the debugger queue. Over this value, content is dropped. This helps to limit the debugger memory usage. Maximum number of warnings allowed to be sent from the debugger. Over this value, content is dropped. This helps not to stall the debugger connection. Default size of packet peer stream for deserializing Godot data (in bytes, specified as a power of two). The default value [code]16[/code] is equal to 65,536 bytes. Over this size, data is dropped. Timeout (in seconds) for connection attempts using TCP. Maximum size (in kiB) for the [WebRTCDataChannel] input buffer. Amount of read ahead used by remote filesystem. Higher values decrease the effects of latency at the cost of higher bandwidth usage. Page size used by remote filesystem (in bytes). The CA certificates bundle to use for SSL connections. If this is set to a non-empty value, this will [i]override[/i] Godot's default [url=https://github.com/godotengine/godot/blob/master/thirdparty/certs/ca-certificates.crt]Mozilla certificate bundle[/url]. If left empty, the default certificate bundle will be used. If in doubt, leave this setting empty. The default angular damp in 2D. [b]Note:[/b] Good values are in the range [code]0[/code] to [code]1[/code]. At value [code]0[/code] objects will keep moving with the same velocity. Values greater than [code]1[/code] will aim to reduce the velocity to [code]0[/code] in less than a second e.g. a value of [code]2[/code] will aim to reduce the velocity to [code]0[/code] in half a second. A value equal to or greater than the physics frame rate ([member ProjectSettings.physics/common/physics_ticks_per_second], [code]60[/code] by default) will bring the object to a stop in one iteration. The default gravity strength in 2D (in pixels per second squared). [b]Note:[/b] This property is only read when the project starts. To change the default gravity at runtime, use the following code sample: [codeblocks] [gdscript] # Set the default gravity strength to 980. PhysicsServer2D.area_set_param(get_viewport().find_world_2d().space, PhysicsServer2D.AREA_PARAM_GRAVITY, 980) [/gdscript] [csharp] // Set the default gravity strength to 980. PhysicsServer2D.AreaSetParam(GetViewport().FindWorld2d().Space, PhysicsServer2D.AreaParameter.Gravity, 980); [/csharp] [/codeblocks] The default gravity direction in 2D. [b]Note:[/b] This property is only read when the project starts. To change the default gravity vector at runtime, use the following code sample: [codeblocks] [gdscript] # Set the default gravity direction to `Vector2(0, 1)`. PhysicsServer2D.area_set_param(get_viewport().find_world_2d().space, PhysicsServer2D.AREA_PARAM_GRAVITY_VECTOR, Vector2.DOWN) [/gdscript] [csharp] // Set the default gravity direction to `Vector2(0, 1)`. PhysicsServer2D.AreaSetParam(GetViewport().FindWorld2d().Space, PhysicsServer2D.AreaParameter.GravityVector, Vector2.Down) [/csharp] [/codeblocks] The default linear damp in 2D. [b]Note:[/b] Good values are in the range [code]0[/code] to [code]1[/code]. At value [code]0[/code] objects will keep moving with the same velocity. Values greater than [code]1[/code] will aim to reduce the velocity to [code]0[/code] in less than a second e.g. a value of [code]2[/code] will aim to reduce the velocity to [code]0[/code] in half a second. A value equal to or greater than the physics frame rate ([member ProjectSettings.physics/common/physics_ticks_per_second], [code]60[/code] by default) will bring the object to a stop in one iteration. Sets which physics engine to use for 2D physics. "DEFAULT" and "GodotPhysics2D" are the same, as there is currently no alternative 2D physics server implemented. If [code]true[/code], the 2D physics server runs on a separate thread, making better use of multi-core CPUs. If [code]false[/code], the 2D physics server runs on the main thread. Running the physics server on a separate thread can increase performance, but restricts API access to only physics process. Threshold angular velocity under which a 2D physics body will be considered inactive. See [constant PhysicsServer2D.SPACE_PARAM_BODY_ANGULAR_VELOCITY_SLEEP_THRESHOLD]. Threshold linear velocity under which a 2D physics body will be considered inactive. See [constant PhysicsServer2D.SPACE_PARAM_BODY_LINEAR_VELOCITY_SLEEP_THRESHOLD]. Maximum distance a shape can penetrate another shape before it is considered a collision. See [constant PhysicsServer2D.SPACE_PARAM_CONTACT_MAX_ALLOWED_PENETRATION]. Maximum distance a shape can be from another before they are considered separated and the contact is discarded. See [constant PhysicsServer2D.SPACE_PARAM_CONTACT_MAX_SEPARATION]. Maximum distance a pair of bodies has to move before their collision status has to be recalculated. See [constant PhysicsServer2D.SPACE_PARAM_CONTACT_RECYCLE_RADIUS]. Default solver bias for all physics constraints. Defines how much bodies react to enforce constraints. See [constant PhysicsServer2D.SPACE_PARAM_CONSTRAINT_DEFAULT_BIAS]. Individual constraints can have a specific bias value (see [member Joint2D.bias]). Default solver bias for all physics contacts. Defines how much bodies react to enforce contact separation. See [constant PhysicsServer2D.SPACE_PARAM_CONTACT_DEFAULT_BIAS]. Individual shapes can have a specific bias value (see [member Shape2D.custom_solver_bias]). Number of solver iterations for all contacts and constraints. The greater the amount of iterations, the more accurate the collisions will be. However, a greater amount of iterations requires more CPU power, which can decrease performance. See [constant PhysicsServer2D.SPACE_PARAM_SOLVER_ITERATIONS]. Time (in seconds) of inactivity before which a 2D physics body will put to sleep. See [constant PhysicsServer2D.SPACE_PARAM_BODY_TIME_TO_SLEEP]. The default angular damp in 3D. [b]Note:[/b] Good values are in the range [code]0[/code] to [code]1[/code]. At value [code]0[/code] objects will keep moving with the same velocity. Values greater than [code]1[/code] will aim to reduce the velocity to [code]0[/code] in less than a second e.g. a value of [code]2[/code] will aim to reduce the velocity to [code]0[/code] in half a second. A value equal to or greater than the physics frame rate ([member ProjectSettings.physics/common/physics_ticks_per_second], [code]60[/code] by default) will bring the object to a stop in one iteration. The default gravity strength in 3D (in meters per second squared). [b]Note:[/b] This property is only read when the project starts. To change the default gravity at runtime, use the following code sample: [codeblocks] [gdscript] # Set the default gravity strength to 9.8. PhysicsServer3D.area_set_param(get_viewport().find_world().space, PhysicsServer3D.AREA_PARAM_GRAVITY, 9.8) [/gdscript] [csharp] // Set the default gravity strength to 9.8. PhysicsServer3D.AreaSetParam(GetViewport().FindWorld().Space, PhysicsServer3D.AreaParameter.Gravity, 9.8); [/csharp] [/codeblocks] The default gravity direction in 3D. [b]Note:[/b] This property is only read when the project starts. To change the default gravity vector at runtime, use the following code sample: [codeblocks] [gdscript] # Set the default gravity direction to `Vector3(0, -1, 0)`. PhysicsServer3D.area_set_param(get_viewport().find_world().get_space(), PhysicsServer3D.AREA_PARAM_GRAVITY_VECTOR, Vector3.DOWN) [/gdscript] [csharp] // Set the default gravity direction to `Vector3(0, -1, 0)`. PhysicsServer3D.AreaSetParam(GetViewport().FindWorld().Space, PhysicsServer3D.AreaParameter.GravityVector, Vector3.Down) [/csharp] [/codeblocks] The default linear damp in 3D. [b]Note:[/b] Good values are in the range [code]0[/code] to [code]1[/code]. At value [code]0[/code] objects will keep moving with the same velocity. Values greater than [code]1[/code] will aim to reduce the velocity to [code]0[/code] in less than a second e.g. a value of [code]2[/code] will aim to reduce the velocity to [code]0[/code] in half a second. A value equal to or greater than the physics frame rate ([member ProjectSettings.physics/common/physics_ticks_per_second], [code]60[/code] by default) will bring the object to a stop in one iteration. Sets which physics engine to use for 3D physics. "DEFAULT" and "GodotPhysics3D" are the same, as there is currently no alternative 3D physics server implemented. If [code]true[/code], the 3D physics server runs on a separate thread, making better use of multi-core CPUs. If [code]false[/code], the 3D physics server runs on the main thread. Running the physics server on a separate thread can increase performance, but restricts API access to only physics process. Threshold angular velocity under which a 3D physics body will be considered inactive. See [constant PhysicsServer3D.SPACE_PARAM_BODY_ANGULAR_VELOCITY_SLEEP_THRESHOLD]. Threshold linear velocity under which a 3D physics body will be considered inactive. See [constant PhysicsServer3D.SPACE_PARAM_BODY_LINEAR_VELOCITY_SLEEP_THRESHOLD]. Maximum distance a shape can penetrate another shape before it is considered a collision. See [constant PhysicsServer3D.SPACE_PARAM_CONTACT_MAX_ALLOWED_PENETRATION]. Maximum distance a shape can be from another before they are considered separated and the contact is discarded. See [constant PhysicsServer3D.SPACE_PARAM_CONTACT_MAX_SEPARATION]. Maximum distance a pair of bodies has to move before their collision status has to be recalculated. See [constant PhysicsServer3D.SPACE_PARAM_CONTACT_RECYCLE_RADIUS]. Default solver bias for all physics contacts. Defines how much bodies react to enforce contact separation. See [constant PhysicsServer3D.SPACE_PARAM_CONTACT_DEFAULT_BIAS]. Individual shapes can have a specific bias value (see [member Shape3D.custom_solver_bias]). Number of solver iterations for all contacts and constraints. The greater the amount of iterations, the more accurate the collisions will be. However, a greater amount of iterations requires more CPU power, which can decrease performance. See [constant PhysicsServer3D.SPACE_PARAM_SOLVER_ITERATIONS]. Time (in seconds) of inactivity before which a 3D physics body will put to sleep. See [constant PhysicsServer3D.SPACE_PARAM_BODY_TIME_TO_SLEEP]. Enables [member Viewport.physics_object_picking] on the root viewport. Controls how much physics ticks are synchronized with real time. For 0 or less, the ticks are synchronized. Such values are recommended for network games, where clock synchronization matters. Higher values cause higher deviation of in-game clock and real clock, but allows smoothing out framerate jitters. The default value of 0.5 should be fine for most; values above 2 could cause the game to react to dropped frames with a noticeable delay and are not recommended. [b]Note:[/b] For best results, when using a custom physics interpolation solution, the physics jitter fix should be disabled by setting [member physics/common/physics_jitter_fix] to [code]0[/code]. [b]Note:[/b] This property is only read when the project starts. To change the physics FPS at runtime, set [member Engine.physics_jitter_fix] instead. The number of fixed iterations per second. This controls how often physics simulation and [method Node._physics_process] methods are run. See also [member debug/settings/fps/force_fps]. [b]Note:[/b] This property is only read when the project starts. To change the physics FPS at runtime, set [member Engine.physics_ticks_per_second] instead. [b]Note:[/b] Only 8 physics ticks may be simulated per rendered frame at most. If more than 8 physics ticks have to be simulated per rendered frame to keep up with rendering, the game will appear to slow down (even if [code]delta[/code] is used consistently in physics calculations). Therefore, it is recommended not to increase [member physics/common/physics_ticks_per_second] above 240. Otherwise, the game will slow down when the rendering framerate goes below 30 FPS. Sets the number of MSAA samples to use (as a power of two). MSAA is used to reduce aliasing around the edges of polygons. A higher MSAA value results in smoother edges but can be significantly slower on some hardware. See also bilinear scaling 3d [member rendering/scaling_3d/mode] for supersampling, which provides higher quality but is much more expensive. Sets the screen-space antialiasing mode for the default screen [Viewport]. Screen-space antialiasing works by selectively blurring edges in a post-process shader. It differs from MSAA which takes multiple coverage samples while rendering objects. Screen-space AA methods are typically faster than MSAA and will smooth out specular aliasing, but tend to make scenes appear blurry. Another way to combat specular aliasing is to enable [member rendering/anti_aliasing/screen_space_roughness_limiter/enabled]. Sets the quality of the depth of field effect. Higher quality takes more samples, which is slower but looks smoother. Sets the depth of field shape. Can be Box, Hexagon, or Circle. Box is the fastest. Circle is the most realistic, but also the most expensive to compute. If [code]true[/code], jitters DOF samples to make effect slightly blurrier and hide lines created from low sample rates. This can result in a slightly grainy appearance when used with a low number of samples. If [code]true[/code], performs a previous depth pass before rendering 3D materials. This increases performance significantly in scenes with high overdraw, when complex materials and lighting are used. However, in scenes with few occluded surfaces, the depth prepass may reduce performance. If your game is viewed from a fixed angle that makes it easy to avoid overdraw (such as top-down or side-scrolling perspective), consider disabling the depth prepass to improve performance. This setting can be changed at run-time to optimize performance depending on the scene currently being viewed. [b]Note:[/b] Only supported when using the Vulkan Clustered backend (not Vulkan Mobile or OpenGL). When using Vulkan Mobile or OpenGL, there is no depth prepass performed. The video driver to use. [b]Note:[/b] OpenGL support is currently incomplete. Only basic 2D rendering is supported, and single-window mode is required for correct operation. [b]Note:[/b] The backend in use can be overridden at runtime via the [code]--rendering-driver[/code] command line argument. [b]FIXME:[/b] No longer valid after DisplayServer split: In such cases, this property is not updated, so use [code]OS.get_current_video_driver[/code] to query it at run-time. Thread model for rendering. Rendering on a thread can vastly improve performance, but synchronizing to the main thread can cause a bit more jitter. Default background clear color. Overridable per [Viewport] using its [Environment]. See [member Environment.background_mode] and [member Environment.background_color] in particular. To change this default color programmatically, use [method RenderingServer.set_default_clear_color]. [Environment] that will be used as a fallback environment in case a scene does not specify its own environment. The default environment is loaded in at scene load time regardless of whether you have set an environment or not. If you do not rely on the fallback environment, you do not need to set this property. Sets how the glow effect is upscaled before being copied onto the screen. Linear is faster, but looks blocky. Bicubic is slower but looks smooth. Lower-end override for [member rendering/environment/glow/upscale_mode] on mobile devices, due to performance concerns or driver support. Takes more samples during downsample pass of glow. This ensures that single pixels are captured by glow which makes the glow look smoother and more stable during movement. However, it is very expensive and makes the glow post process take twice as long. Sets the quality for rough screen-space reflections. Turning off will make all screen space reflections sharp, while higher values make rough reflections look better. Quality target to use when [member rendering/environment/ssao/quality] is set to [code]ULTRA[/code]. A value of [code]0.0[/code] provides a quality and speed similar to [code]MEDIUM[/code] while a value of [code]1.0[/code] provides much higher quality than any of the other settings at the cost of performance. Number of blur passes to use when computing screen-space ambient occlusion. A higher number will result in a smoother look, but will be slower to compute and will have less high-frequency detail. Distance at which the screen-space ambient occlusion effect starts to fade out. Use this hide ambient occlusion at great distances. Distance at which the screen-space ambient occlusion is fully faded out. Use this hide ambient occlusion at great distances. If [code]true[/code], screen-space ambient occlusion will be rendered at half size and then upscaled before being added to the scene. This is significantly faster but may miss small details. Lower-end override for [member rendering/environment/ssao/half_size] on mobile devices, due to performance concerns. Sets the quality of the screen-space ambient occlusion effect. Higher values take more samples and so will result in better quality, at the cost of performance. Setting to [code]ULTRA[/code] will use the [member rendering/environment/ssao/adaptive_target] setting. Quality target to use when [member rendering/environment/ssil/quality] is set to [code]ULTRA[/code]. A value of [code]0.0[/code] provides a quality and speed similar to [code]MEDIUM[/code] while a value of [code]1.0[/code] provides much higher quality than any of the other settings at the cost of performance. When using the adaptive target, the performance cost scales with the complexity of the scene. Number of blur passes to use when computing screen-space indirect lighting. A higher number will result in a smoother look, but will be slower to compute and will have less high-frequency detail. Distance at which the screen-space indirect lighting effect starts to fade out. Use this hide screen-space indirect lighting at great distances. Distance at which the screen-space indirect lighting is fully faded out. Use this hide screen-space indirect lighting at great distances. If [code]true[/code], screen-space indirect lighting will be rendered at half size and then upscaled before being added to the scene. This is significantly faster but may miss small details and may result in some objects appearing to glow at their edges. Sets the quality of the screen-space indirect lighting effect. Higher values take more samples and so will result in better quality, at the cost of performance. Setting to [code]ULTRA[/code] will use the [member rendering/environment/ssil/adaptive_target] setting. Scales the depth over which the subsurface scattering effect is applied. A high value may allow light to scatter into a part of the mesh or another mesh that is close in screen space but far in depth. Sets the quality of the subsurface scattering effect. Higher values are slower but look nicer. Scales the distance over which samples are taken for subsurface scattering effect. Changing this does not impact performance, but higher values will result in significant artifacts as the samples will become obviously spread out. A lower value results in a smaller spread of scattered light. Enables filtering of the volumetric fog effect prior to integration. This substantially blurs the fog which reduces fine details but also smooths out harsh edges and aliasing artifacts. Disable when more detail is required. Number of slices to use along the depth of the froxel buffer for volumetric fog. A lower number will be more efficient but may result in artifacts appearing during camera movement. Base size used to determine size of froxel buffer in the camera X-axis and Y-axis. The final size is scaled by the aspect ratio of the screen, so actual values may differ from what is set. Set a larger size for more detailed fog, set a smaller size for better performance. If [code]true[/code], renders [VoxelGI] and SDFGI ([member Environment.sdfgi_enabled]) buffers at halved resolution (e.g. 960×540 when the viewport size is 1920×1080). This improves performance significantly when VoxelGI or SDFGI is enabled, at the cost of artifacts that may be visible on polygon edges. The loss in quality becomes less noticeable as the viewport resolution increases. [LightmapGI] rendering is not affected by this setting. [b]Note:[/b] This property is only read when the project starts. To set half-resolution GI at run-time, call [method RenderingServer.gi_set_use_half_resolution] instead. The automatic LOD bias to use for meshes rendered within the [ReflectionProbe]. Higher values will use less detailed versions of meshes that have LOD variations generated. If set to [code]0.0[/code], automatic LOD is disabled. Increase [member rendering/mesh_lod/lod_change/threshold_pixels] to improve performance at the cost of geometry detail. [b]Note:[/b] [member rendering/mesh_lod/lod_change/threshold_pixels] does not affect [GeometryInstance3D] visibility ranges (also known as "manual" LOD or hierarchical LOD). [b]Note:[/b] This property is only read when the project starts. To adjust the automatic LOD threshold at runtime, set [member Viewport.mesh_lod_threshold] on the root [Viewport]. The [url=https://en.wikipedia.org/wiki/Bounding_volume_hierarchy]BVH[/url] quality to use when rendering the occlusion culling buffer. Higher values will result in more accurate occlusion culling, at the cost of higher CPU usage. Higher values will result in more accurate occlusion culling, at the cost of higher CPU usage. The occlusion culling buffer's pixel count is roughly equal to [code]occlusion_rays_per_thread * number_of_logical_cpu_cores[/code], so it will depend on the system's CPU. Therefore, CPUs with fewer cores will use a lower resolution to attempt keeping performance costs even across devices. If [code]true[/code], [OccluderInstance3D] nodes will be usable for occlusion culling in 3D in the root viewport. In custom viewports, [member Viewport.use_occlusion_culling] must be set to [code]true[/code] instead. [b]Note:[/b] Enabling occlusion culling has a cost on the CPU. Only enable occlusion culling if you actually plan to use it. Large open scenes with few or no objects blocking the view will generally not benefit much from occlusion culling. Large open scenes generally benefit more from mesh LOD and visibility ranges ([member GeometryInstance3D.visibility_range_begin] and [member GeometryInstance3D.visibility_range_end]) compared to occlusion culling. Number of cubemaps to store in the reflection atlas. The number of [ReflectionProbe]s in a scene will be limited by this amount. A higher number requires more VRAM. Size of cubemap faces for [ReflectionProbe]s. A higher number requires more VRAM and may make reflection probe updating slower. Lower-end override for [member rendering/reflections/reflection_atlas/reflection_size] on mobile devices, due to performance concerns or driver support. Use a higher quality variant of the fast filtering algorithm. Significantly slower than using default quality, but results in smoother reflections. Should only be used when the scene is especially detailed. Sets the number of samples to take when using importance sampling for [Sky]s and [ReflectionProbe]s. A higher value will result in smoother, higher quality reflections, but increases time to calculate radiance maps. In general, fewer samples are needed for simpler, low dynamic range environments while more samples are needed for HDR environments and environments with a high level of detail. Lower-end override for [member rendering/reflections/sky_reflections/ggx_samples] on mobile devices, due to performance concerns or driver support. Limits the number of layers to use in radiance maps when using importance sampling. A lower number will be slightly faster and take up less VRAM. If [code]true[/code], uses texture arrays instead of mipmaps for reflection probes and panorama backgrounds (sky). This reduces jitter noise and upscaling artifacts on reflections, but is significantly slower to compute and uses [member rendering/reflections/sky_reflections/roughness_layers] times more memory. Lower-end override for [member rendering/reflections/sky_reflections/texture_array_reflections] on mobile devices, due to performance concerns or driver support. Affects the final texture sharpness by reading from a lower or higher mipmap. Negative values make textures sharper, while positive values make textures blurrier. When using FSR, this value is used to adjust the mipmap bias calculated internally which is based on the selected quality. The formula for this is [code]-log2(1.0 / scale) + mipmap_bias[/code] Determines how sharp the upscaled image will be when using the FSR upscaling mode. Sharpness halves with every whole number. Values go from 0.0 (sharpest) to 2.0. Values above 2.0 won't make a visible difference. Sets the scaling 3D mode. Bilinear scaling renders at different resolution to either undersample or supersample the viewport. FidelityFX Super Resolution 1.0, abbreviated to FSR, is an upscaling technology that produces high quality images at fast framerates by using a spatially aware upscaling algorithm. FSR is slightly more expensive than bilinear, but it produces significantly higher image quality. FSR should be used where possible. Scales the 3D render buffer based on the viewport size uses an image filter specified in [member rendering/scaling_3d/mode] to scale the output image to the full viewport size. Values lower than [code]1.0[/code] can be used to speed up 3D rendering at the cost of quality (undersampling). Values greater than [code]1.0[/code] are only valid for bilinear mode and can be used to improve 3D rendering quality at a high performance cost (supersampling). See also [member rendering/anti_aliasing/quality/msaa] for multi-sample antialiasing, which is significantly cheaper but only smoothens the edges of polygons. If [code]true[/code], uses faster but lower-quality Lambert material lighting model instead of Burley. Lower-end override for [member rendering/shading/overrides/force_lambert_over_burley] on mobile devices, due to performance concerns or driver support. If [code]true[/code], forces vertex shading for all rendering. This can increase performance a lot, but also reduces quality immensely. Can be used to optimize performance on low-end mobile devices. Lower-end override for [member rendering/shading/overrides/force_vertex_shading] on mobile devices, due to performance concerns or driver support. The directional shadow's size in pixels. Higher values will result in sharper shadows, at the cost of performance. The value will be rounded up to the nearest power of 2. Lower-end override for [member rendering/shadows/directional_shadow/size] on mobile devices, due to performance concerns or driver support. Quality setting for shadows cast by [DirectionalLight3D]s. Higher quality settings use more samples when reading from shadow maps and are thus slower. Low quality settings may result in shadows looking grainy. [b]Note:[/b] The Soft Very Low setting will automatically multiply [i]constant[/i] shadow blur by 0.75x to reduce the amount of noise visible. This automatic blur change only affects the constant blur factor defined in [member Light3D.shadow_blur], not the variable blur performed by [DirectionalLight3D]s' [member Light3D.light_angular_distance]. [b]Note:[/b] The Soft High and Soft Ultra settings will automatically multiply [i]constant[/i] shadow blur by 1.5× and 2× respectively to make better use of the increased sample count. This increased blur also improves stability of dynamic object shadows. Lower-end override for [member rendering/shadows/directional_shadow/soft_shadow_quality] on mobile devices, due to performance concerns or driver support. Subdivision quadrant size for shadow mapping. See shadow mapping documentation. Subdivision quadrant size for shadow mapping. See shadow mapping documentation. Subdivision quadrant size for shadow mapping. See shadow mapping documentation. Subdivision quadrant size for shadow mapping. See shadow mapping documentation. Size for shadow atlas (used for OmniLights and SpotLights). See documentation. Lower-end override for [member rendering/shadows/shadow_atlas/size] on mobile devices, due to performance concerns or driver support. Quality setting for shadows cast by [OmniLight3D]s and [SpotLight3D]s. Higher quality settings use more samples when reading from shadow maps and are thus slower. Low quality settings may result in shadows looking grainy. [b]Note:[/b] The Soft Very Low setting will automatically multiply [i]constant[/i] shadow blur by 0.75x to reduce the amount of noise visible. This automatic blur change only affects the constant blur factor defined in [member Light3D.shadow_blur], not the variable blur performed by [DirectionalLight3D]s' [member Light3D.light_angular_distance]. [b]Note:[/b] The Soft High and Soft Ultra settings will automatically multiply shadow blur by 1.5× and 2× respectively to make better use of the increased sample count. This increased blur also improves stability of dynamic object shadows. Lower-end override for [member rendering/shadows/shadows/soft_shadow_quality] on mobile devices, due to performance concerns or driver support. Sets the maximum number of samples to take when using anisotropic filtering on textures (as a power of two). A higher sample count will result in sharper textures at oblique angles, but is more expensive to compute. A value of [code]0[/code] forcibly disables anisotropic filtering, even on materials where it is enabled. [b]Note:[/b] This property is only read when the project starts. There is currently no way to change this setting at run-time. If [code]true[/code], uses nearest-neighbor mipmap filtering when using mipmaps (also called "bilinear filtering"), which will result in visible seams appearing between mipmap stages. This may increase performance in mobile as less memory bandwidth is used. If [code]false[/code], linear mipmap filtering (also called "trilinear filtering") is used. [b]Note:[/b] This property is only read when the project starts. There is currently no way to change this setting at run-time. If [code]true[/code], the texture importer will import lossless textures using the PNG format. Otherwise, it will default to using WebP. The default compression level for lossless WebP. Higher levels result in smaller files at the cost of compression speed. Decompression speed is mostly unaffected by the compression level. Supported values are 0 to 9. Note that compression levels above 6 are very slow and offer very little savings. If [code]true[/code], the texture importer will import VRAM-compressed textures using the BPTC algorithm. This texture compression algorithm is only supported on desktop platforms, and only when using the Vulkan renderer. [b]Note:[/b] Changing this setting does [i]not[/i] impact textures that were already imported before. To make this setting apply to textures that were already imported, exit the editor, remove the [code].godot/imported/[/code] folder located inside the project folder then restart the editor (see [member application/config/use_hidden_project_data_directory]). If [code]true[/code], the texture importer will import VRAM-compressed textures using the Ericsson Texture Compression algorithm. This algorithm doesn't support alpha channels in textures. [b]Note:[/b] Changing this setting does [i]not[/i] impact textures that were already imported before. To make this setting apply to textures that were already imported, exit the editor, remove the [code].godot/imported/[/code] folder located inside the project folder then restart the editor (see [member application/config/use_hidden_project_data_directory]). If [code]true[/code], the texture importer will import VRAM-compressed textures using the Ericsson Texture Compression 2 algorithm. This texture compression algorithm is only supported when using the Vulkan renderer. [b]Note:[/b] Changing this setting does [i]not[/i] impact textures that were already imported before. To make this setting apply to textures that were already imported, exit the editor, remove the [code].godot/imported/[/code] folder located inside the project folder then restart the editor (see [member application/config/use_hidden_project_data_directory]). If [code]true[/code], the texture importer will import VRAM-compressed textures using the S3 Texture Compression algorithm. This algorithm is only supported on desktop platforms and consoles. [b]Note:[/b] Changing this setting does [i]not[/i] impact textures that were already imported before. To make this setting apply to textures that were already imported, exit the editor, remove the [code].godot/imported/[/code] folder located inside the project folder then restart the editor (see [member application/config/use_hidden_project_data_directory]). Action map configuration to load by default. If [code]true[/code] Godot will setup and initialise OpenXR on startup. Specify whether OpenXR should be configured for an HMD or a hand held device. Specify the default reference space. Specify the view configuration with which to configure OpenXR settting up either Mono or Stereo rendering. If [code]true[/code], Godot will compile shaders required for XR.