birkeh/o3de
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Removed AssetProcessor Settings from the bootstrap.cfg file as they are

Browse Source 
being shadowed by the <engine-root>/Engine/Registry/bootstrap.setreg
file.
Attempting to set those values in the bootstrap.cfg would only result in
them being overridden when the bootstrap.setreg is merged into the
settings registry
This commit is contained in:
mcgarrah
2021-04-15 15:02:35 -05:00
committed by mcgarrah
parent 250f8d8db0
commit ab11b234a8
1 changed files with 9 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bootstrap.cfg
+9 -81
View File
@@ -1,84 +1,12 @@
-- When you see an option that does not have a platform preceeding it, that is the default
-- value for anything not specificly set per platform. So if remote_filesystem=0 and you have
-- ios_remote_file_system=1 then remote filesystem will be off for all platforms except ios
-- Any of the settings in this file can be prefixed with a platform name:
-- android, ios, mac, linux, windows, etc...
-- or left unprefixed, to set all platforms not specified. The rules apply in the order they're declared
; This file is deprecated and is only use currently for setting the path when running O3DE in an engine-centric manner
; By engine-centric, what is meant is using CMake to configure from the <engine-root> directory and passing in the LY_PROJECTS value
project_path=AutomatedTesting
-- remote_filesystem - enable Virtual File System (VFS)
-- This feature allows a remote instance of the game to run off assets
-- on the asset processor computers cache instead of deploying them the remote device
-- By default it is off and can be overridden for any platform
remote_filesystem=0
provo_remote_filesystem=0
android_remote_filesystem=0
ios_remote_filesystem=0
mac_remote_filesystem=0
-- What type of assets are we going to load?
-- We need to know this before we establish VFS because different platform assets
-- are stored in different root folders in the cache. These correspond to the names
-- In the asset processor config file. This value also controls what config file is read
-- when you read system_xxxx_xxxx.cfg (for example, system_windows_pc.cfg or system_android_es3.cfg)
-- by default, pc assets (in the 'pc' folder) are used, with RC being fed 'pc' as the platform
-- by default on console we use the default assets=pc for better iteration times
-- we should turn on console specific assets only when in release and/or testing assets and/or loading performance
-- that way most people will not need to have 3 different caches taking up disk space
assets = pc
-- provo_assets = provo
-- salem_assets = salem
-- jasper_assets = jasper
android_assets = es3
ios_assets = ios
mac_assets = osx_gl
-- Add the IP address of your console to the allowed list that will connect to the asset processor here
-- You can list addresses or CIDR's. CIDR's are helpful if you are using DHCP. A CIDR looks like an ip address with
-- a /n on the end means how many bits are significant. 8bits.8bits.8bits.8bits = /32
-- Example: 192.168.1.3
-- Example: 192.168.1.3, 192.168.1.15
-- Example: 192.168.1.0/24 will allow any address starting with 192.168.1.
-- Example: 192.168.0.0/16 will allow any address starting with 192.168.
-- Example: 192.168.0.0/8 will allow any address starting with 192.
-- allowed_list =
-- IP address and optionally port of the asset processor.
-- Set your PC IP here: (and uncomment the next line)
-- If you are running your asset processor on a windows machine you
-- can find out your ip address by opening a cmd prompt and typing in ipconfig
-- remote_ip = 127.0.0.1
-- remote_port = 45643
-- Which way do you want to connect the asset processor to the game: 1=game connects to AP "connect", 0=AP connects to game "listen"
-- Note: android and IOS over USB port forwarding may need to listen instead of connect
connect_to_remote=0
windows_connect_to_remote=1
provo_connect_to_remote=1
salem_connect_to_remote=0
jasper_connect_to_remote=0
android_connect_to_remote=0
ios_connect_to_remote=0
mac_connect_to_remote=0
-- Should we tell the game to wait and not proceed unless we have a connection to the AP or
-- do we allow it to continue to try to connect in the background without waiting
-- Note: Certain options REQUIRE that we do not proceed unless we have a connection, and will override this option to 1 when set
-- Since remote_filesystem=1 requires a connection to proceed it will override our option to 1
wait_for_connect=0
provo_wait_for_connect=0
salem_wait_for_connect=0
jasper_wait_for_connect=0
windows_wait_for_connect=1
android_wait_for_connect=0
ios_wait_for_connect=0
mac_wait_for_connect=0
-- How long applications should wait while attempting to connect to an already launched AP(in seconds)
-- connect_ap_timeout=3
-- How long application should wait when launching the AP and wait for the AP to connect back to it(in seconds)
-- This time is dependent on Machine load as well as how long it takes for the new AP instance to initialize
-- A debug AP takes longer to start up than a profile AP
-- launch_ap_timeout=15
; The Asset Processor Specific settings are now the <engine-root>/Engine/Registry/bootstrap.setreg settings
; The Engine specific settings can be overridden in order of least precedence to most
; 1. Override the settings in a "<gem-root>/Registry/*.setreg(patch)" file (Shared per Gem Settings)
; 2. Override the settings in a "<project-root>/Registry/*.setreg(patch)" file (Shared per Project Settings)
; 3. Override the settings in a "<project-root>/Registry/*.setreg(patch)" file (User per Project Settings)
; 4. Override the settings in a "~/.o3de/Registry/*.setreg(patch)" file (User Global Settings)
; Where "~" is %USERPROFILE% on Windows and $HOME on Unix like platforms