Home
About
FAQ
Force Editor
Force Scripting API
- Force
  AABB
  AABB2D
  Application
  Asset
  AssetManager
  AudioClip
  LoadAudioClip
  UnloadAudioClip
  AudioEngine
  AudioListener
  AudioSource
  AutoValidate
  BoxCollider2D
  Camera
  CameraOrthoBounds
  CameraPerspectiveBounds
  CircleCollider2D
  CircleRenderer
  Collider2D
  Color
  Color32
  Component
  ComponentException
  Debug
  DisableInInspector
  Font
  ForceException
  GameObject
  Input
  Key
  Mouse
  Intersection
  Language
  LanguageManager
  LineRenderer
  Logger
  LogType
  Math
  Matrix3f
  Matrix4f
  MeshRenderer
  MonoEmptyScript
  MonoScript
  Object
  Particle
  ParticleSystem
  Physics2DSettings
  PhysicsBehaviour
  PhysicsType
  PhysicsShape2D
  PhysicsShape2DType
  PrimitiveType
  Quaternion
  Ray
  RayCast2DInput
  RayCast2DOutput
  Rect
  Renderer2D
  RendererException
  Resources
  Rigidbody2D
  RigidbodyType2D
  Scene
  SceneManager
  SceneManagerException
  Shader
  ShaderBufferBlock
  ShowInInspector
  SpriteRenderer
  StructuredBuffer
  Text
  TextAsset
  TextScript
  Texture
  Texture2D
  TextureFlip
  TextureTileEffect
  TextureType
  Transform
  Transform2D
  Direction
  Utils
  Vector2f
  Vector2i
  Vector3f
  Vector3i
  Vector4f
  Window
- ForceEditor
  GUI
  GUIException
  GUIPanel
  GUIPanelFlags
  GUITable
For Engine Developers
- Force Core API
  Prepare Project
  Application
Other

Powered by GitBook

On this page

Profiler Settings

PreviousScene Settings NextProject Settings

Last updated 9 months ago

Editor Settings.

Profiling and Debug settings.

General

Property

Description

Profiling

Enable profiling in runtime (when game plays) in debug build, and saving the results in ForceDebug-editor.json file along with Force.exe.