anchor.diff:  = Optimizing Your Game Using Statistics
  -:author: 
  -:revnumber: 
  +:author:
  +:revnumber:
   :revdate: 2016/03/17 20:48
   :relfileprefix: ../../
   :imagesdir: ../..
   ifdef::env-github,env-browser[:outfilesuffix: .adoc]
   
   
  -When you create a SimpleApplication, you see the default StatsView and FpsView in the left corner. 
  +When you create a SimpleApplication, you see the default StatsView and FpsView in the left corner.
   The StatsView displays object statistics that are used during development, for example for debugging and optimization.
  -Below the StatsView is the FpsView that displays the frames that jMonkeyEngine can render per second. 
  +Below the StatsView is the FpsView that displays the frames that jMonkeyEngine can render per second.
   
   The main use case of these statistics is to find out why the application may be running slow and where to start fixing the performance.
   
  
positive.code: .  It's okay if Switches (S) are lower than Used in Current Frame (F).
  .  The FPS should be 30 or more on the slowest hardware that you target.
  .  10'000-50'000 vertices is a typical average value for a scene.
  '''
  
  See also:
  
negative.code: 
  Types of items counted:
  
  *  FrameBuffers: Total number of rendering surfaces used for off-screen rendering and render-to-texture functionality.
  *  Textures: Total number of distinct textures used in the scene.
  *  Shaders: Total number of shaders used for effects (shading, blur, lighting, glow, etc).
  *  Objects: Total number of objects in the OpenGL pipeline. That is, objects attached to the rootNode and guiNode, etc.
  