Scribd
Upload
119 views3 pages

Console Commands for Tomb Raider

This configuration file defines various configuration options for an application in a specific order of precedence. Values can be overwritten by later definitions like environment variables overwriting defaults. Placeholders like %{variable} allow inheriting values from other variables. The file specifies options like enabling plugins, diagnostic logging, and disabling processor extensions.

Uploaded by

taiiq zhou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
119 views3 pages

Console Commands for Tomb Raider

This configuration file defines various configuration options for an application in a specific order of precedence. Values can be overwritten by later definitions like environment variables overwriting defaults. Placeholders like %{variable} allow inheriting values from other variables. The file specifies options like enabling plugins, diagnostic logging, and disabling processor extensions.

Uploaded by

taiiq zhou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

/*

CONFIGURATION FILE.

All values are evaluated in this order:

|| Application Code (Defaults)


|| Configuration File
|| Environment Variables
|| Command Line
\/

The same value defined e.g. as an environment variable will overwrite the default
of a configuration file.

You can use the following syntax to assign the content of one value to another:
NEWVALUE=%{OLDVALUE}

Example:
g_SkipUnitTests=g_debug
g_myPath=g_path1;g_path2

To inherit the content of the same variable use: VALUE=%{inherit}

Example:
g_SkipUnitTests=%{inherit} // if this was passed to the command line the value
will be inherited from the environment or configuration file
*/

g_runC4DPlugin=true
g_disableStringAccessCheck=true
g_moduleDiagnostic=true

// g_memoryBacktrace=true

g_disableOpenGLExtensions=GL_NV_command_list;GL_ARB_direct_state_access:amd;GL_ARB_
sampler_objects:amd

g_modulePath = %{g_startupPath}/corelibs;%{g_startupPath}/plugins;%
{g_prefsPath}/plugins

g_enableViewportTypeChooser=true
// g_viewportMode=1 // Note: Uncomment this line to force Cinema 4D to start with
the legacy viewport

// disable debug breaks


// g_enableDebugBreak = false

// disable parallel execution of all ParallelFor loops:


// g_enableParallelFor = false

// output diagnostic data for class registation, layout and initialization


// g_showRegistrationProcess = 0

// skip the units tests of the test modules


// g_skipUnitTests=true

// set the memory model, possible values are 'c', 'debug' and 'release'
// g_alloc=c

// log all output to a file


// if no path is specified the log file will be created in the temporary folder
// g_logFile=[string]

// enable/disable console (Windows only and only if no debugger is present)


g_console = false

// allow/disallow diagnostic messages in console


g_diagnostic=true

// allow/disallow debug messages in console


// g_debug = false

// allow/disallow warning messages in console


// g_warning = false

// allow/disallow critical messages in console


// g_critical = false

// don't group memory leaks, show long output


// g_displayShortLeakList = false

// select startup language


// g_startupLanguage = en-US

// output diagnostic data of cadexchange module and selected import settings


// g_cadexchangelog=true

// disable environment variables


// g_disableEnvironment=true

// disable command line arguments


// g_disableCommandLine=true

// show a complete list of the current configuration originating from configuration


file, environment and command line
// g_outputConfiguration=true

// override the default module path. it can contain multiple entries. use ';' as
delimiter.
// g_modulePath=[string] (default "%{g_startupPath}")

// override the default temporary path


// g_tempPath=[string] (default "%{g_tempPath}")

// override the default preference path


// g_prefsPath=[string] (default "%{g_prefsPath}")

// list of modules that will exclusively be loaded (do not include path or suffix).
use ';' as delimiter.
// g_modulePositives=[string]

// list of modules that will not be loaded (do not include path or suffix). use ';'
as delimiter.
// g_moduleNegatives=[string]

// debug tool to force allocations to fail; only works with alloc=debug


// any allocation bigger or equal than this will fail
// g_makeAllocationsFail = 1000000

// decrease or increase number of CPUs / threads used


// note that the number can be higher than the actual number of cores
// g_threadCount = 128

// disable loading of unicode table, a default table will be used instead


// g_loadUnicodeTable = false

// disable the real vtune module if not needed by choosing the null implementation
// [Link]=PerformanceMonitorInterfaceNull

// disable AVX processor extensions


// g_disableAVX=true

// disable AVX2 processor extensions


// g_disableAVX2=true

// disable FMA processor extensions


// g_disableFMA=true

// disable AES processor extensions


// g_disableAES=true

// disable PCLMULQDQ processor extensions


// g_disablePCLMULQDQ=true

// disable SSE2 processor extensions


// g_disableSSE2=true

// disable SSE3 processor extensions


// g_disableSSE3=true

// disable SSE4_1 processor extensions


// g_disableSSE4_1=true

// disable SSE4_2 processor extensions


// g_disableSSE4_2=true

// Choose the run loop:


// Default implementation (usually for UI).
// Command line (no UI used/initialized).
// Gtk (Linux-only).
[Link]=DefaultRunLoopImpl
//[Link]=CmdLineRunLoopImpl
//[Link]=GtkPlusRunLoopImpl

Common questions

Powered by AI

Setting 'g_threadCount = 128' can lead to significantly increased resource utilization, as more CPU threads are invoked to perform tasks concurrently. This could maximize performance on systems with ample resources but may overwhelm systems with fewer cores or limited processing power. It could potentially degrade performance on systems unable to efficiently handle the specified thread count, leading to resource contention and diminished overall system responsiveness .

Setting 'g_disableAVX=true' disables AVX processor extensions, likely to ensure compatibility with systems that do not support these extensions or to avoid potential stability issues caused by utilizing advanced CPU features not available on all hardware. This can help maintain application reliability across diverse environments .

Disabling the loading of unicode tables with 'g_loadUnicodeTable=false' might be chosen to reduce memory usage or initialization time on systems where full unicode support is not necessary. The fallback mechanism suggested is to use a default table, thereby ensuring some level of functionality without the full unicode data set .

Overriding default paths like 'g_tempPath' and 'g_prefsPath' allows administrators to customize directory locations for temporary and preference files. This is useful for aligning with organizational directory structures, managing space on specific drives, or redirecting these paths to secure or backup locations to ensure data integrity and accessibility .

Setting 'g_makeAllocationsFail = 1000000' in a debug context intentionally forces memory allocations of one million bytes or larger to fail. This facilitates testing how the application handles such failures, promoting the development of more robust error handling and resource management strategies by simulating out-of-memory scenarios without imposing actual limits on overall system resources .

Command line arguments take precedence over configuration file entries. This is part of the configuration order where command line settings evaluate last, allowing users to dynamically adjust the behavior of the application without modifying the configuration files permanently .

Setting 'g_outputConfiguration=true' results in the application outputting a complete list of the current configuration, sourced from configuration files, environment variables, and command line arguments. This feature is beneficial for auditing, ensuring that all configuration layers are correctly applied, and for troubleshooting complex configurations by providing a clear overview of active settings .

The application evaluates configuration values in the following order: Application Code (Defaults), Configuration File, Environment Variables, and finally Command Line. Therefore, if both environment variables and configuration files define the same variable, the value from the environment variable will overwrite the configuration file. This allows for flexibility in customizing settings for different environments without altering configuration files .

A system administrator might disable AVX2, FMA, and AES processor extensions to ensure software compatibility across older hardware that lacks support for these features. While this ensures broader accessibility, it might reduce application performance and functionality, especially in data processing or cryptographic tasks that leverage these instructions for efficiency gains .

Disabling diagnostic messages with 'g_diagnostic=false' can reduce console noise, prevent clutter in application logs, and potentially improve performance by not processing these debug outputs. However, it can also hinder troubleshooting efforts by obscuring crucial information that aids in diagnosing issues, thus increasing the complexity of pinpointing and resolving problems during system outages or performance bottlenecks .

You might also like