ATTENTION! The process of updating WiKi to version Eco 10.x has begun. Those wishing to participate can find out more Information on our ECO Contribution Wiki Discord.

Client Profiling

From Eco - English Wiki
Revision as of 12:41, 15 November 2022 by Dennis (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Development Build[edit | edit source]

In opposite to Server Profiling, the profiling options on this page are only available when playing on a development build.

You can check if you're running a development build by looking up if this message is present in the right bottom corner:

Snapshot[edit | edit source]

You can use the `F6` key to make a snapshot. Check the chat log for output file location details, navigate there with your explorer and attach the file to your report.

Transforms Profiling[edit | edit source]

  1. Open Diagnostic Pages UI (with F2).
  2. Go to Transforms page (navigate pages with F3/F4). Page itself significantly impacts performance so keep it closed when you don't need transform updates data.
  3. When you have FPS problems open the page, wait for few seconds and make a screenshot. Attach it to report.
  4. Then run /savetransformstats command in console, find in same directory as Player.log file named transform-stats.txt and also attach it to report.

Test which objects have the most performance impact[edit | edit source]

  1. Use /disableobjects {trees,animals,worldobjects,rubbles} (one of the options) to disable rendering of specific group of objects. Then you can check if it fixes your FPS or not. You can also test if with that group disabled you have performance degradation issues or not.
  2. Use /enableobjects all (or speicific group you previously disabled) to re-enable all objects. Though all objects which was previously disabled won't be recovered - you need to re-enter the world or reload these objects by leaving and returning to the area.