profiler-enable-module

To enable or disable Unity profiler modules, you can use a local bookkeeping approach to manage module names within a wrapper's enabled set. This method controls the enabled state for runtime performance monitoring without altering the Profiler window configuration.

Local bookkeeping for Unity profiler modules involves adding or removing specific module names from a tracked enabled set. It provides a localized state management solution because Unity's runtime API lacks direct control over built-in profiler module namespaces.

Managing profiler modules through local bookkeeping does not modify the Unity Profiler window configuration. It strictly operates as a local wrapper to track the enabled state of modules for runtime performance debugging.

You need to know the exact profiler module names to enable or disable them effectively. The local bookkeeping mechanism requires specific module names, like 'Memory', to add or remove them from the enabled set for performance monitoring.

Unity's runtime API does not expose direct control for built-in profiler module namespaces, necessitating a local bookkeeping skill. This approach bridges the gap by maintaining a local set of enabled modules for debugging and performance monitoring.

The primary limitation is that this local bookkeeping method only tracks the enabled state and does not control the actual Unity Profiler window modules. It requires prior knowledge of exact module names to manage runtime performance monitoring correctly.