Skip to content

F3 stats bars are sorted not according to their place in the timeline

Consider this:

f3_stats

  1. -Sync represents the time interval between Sound and State but placed between Lua and WindowManager.
  2. Lua represents the time interval between Event and WindowManager but placed between Gui and -Sync.
  3. WindowManager represents the time interval between Update and Cull but placed between -Sync and Event.

Ideally each bar should start not before the previous one starts. The goal is to clearly show the impact of each profiled scope on the frame duration. For example what visibly shifts the start of some scopes because it takes significant amount of time.

-Sync likely has to be renamed to something like LuaSync to make sense in the different position.