Unity Simple Editor Log Parser: QUICK GUIDE

08 Oct 2020 Posted by: Comments: 0 In: tutorial, Unity

Often when we have to import a lot of assets into our project, Editor processing time to import them could be a real pain. Being able to see which asset category takes the longest to import can help you in:

  • Know where to direct your optimization efforts
  • Speed up your import times
  • Speed up platform switch times
  • Improve the performance of your Continuous Integration Pipeline if you’re doing clean nightly builds

There are already Asset store plugins that help you to inspect your Editor import timing, but Unity recently released a free Editor parser. You can download it here: https://github.com/Unity-Javier/SimpleEditorLogParser

To use it, you should import a bunch of assets into your project (textures, audio, scripts, whatever you like) and then make a copy of your Editor.log file, that you can find in C:\Users\username\AppData\Local\Unity\Editor\Editor.log. Paste it in a folder (I’ll use C:\Projects\Game01\). Now let’s parse it with Unity’s SimpleEditorLogParser:

  1. Download the zip file from Github
  2. Open the .sln project with VS2019
  3. If you’re prompted with a warning saying that VS needs some extra module to be installed in order to open this project, do it (this will open VSInstaller automatically)
  4. Go to Debug command line settings:
  5. add these arguments:
    –path C:\Projects\Game01\Editor.log –output \CategorizedLog.csv (change the path with the folder where is the copy of your Editor.log)
  6.  Save and Run the project: in the same folder, a cvs file should appear:
  7. I suggest at this time to upload this cvs into your google drive and open it as Google sheet file
  8. Select both Category and Import columns, and then insert a Chart
  9. Click on the created graph, and inside ChartEditor options select Aggregate and PieChart type. And there we go! We have our ImportTime vs Category Pie chart, ready to give use at a glance what we can do to improve import asset times!


Leave a Comment!

Your email address will not be published. Required fields are marked *