[RELEASED] DebugTools - Runtime debugging tools for Unity3D *Free*

DebugTools is a runtime and editor extension gives developers a suite of tools that they can you to visualise, analyse and debug their games and applications. The suite provides a range of in-game overlays, console and logs allowing better analysis both in the editor and while deployed to the full range of platforms compatible with the Unity3D engine.

DebugTools is free for a limited time while in early development. This is hopefully in return for feedback, bug reporting and feature requests. If you have any feedback or feature requests feel free to believe them below.

Asset Store Link: https://www.assetstore.unity3d.com/en/#!/content/83230

On-screen Console

The on-screen console allows you to output everything that you would normally log to the Unity platform except now you can do it on while your application is deployed to any platform you like!!!

Variable Tracking

The variable tracking functionality allows you to watch and track the value of a varible in realtime so you can see exactly what it’s value is every single frame.

Static Graphs

Static graphs allow you to plot a range of data points on a graph and visualise them in a intuitive manner.

Realtime Graphs

The realtime graph functionality allows you to create a graph that tracks and plots the value of a variable per frame. For example you can use it to track the framerate of your game in realtime or the volume of the current audio.

Other Features

  • Persistent log created for access after game in case of crash.
  • Text based config file allowing you to make chages without using unity.
  • Avaliable on all of Unity3D’s platofrms.

Upcoming/Planned Features

  • Custom console commands.
  • Post/Upload/Email analytics once game complete.
  • Automatic game performance tracking.
  • Bug reporting API.

If you would like to promote your game by having footage it included in a showreel of the extension please get in contact.

2 Likes

Custom outputs are coming soon in the next update. Perfect for creating a output log in VR.

Hi there,

This looks pretty nice. I was looking for a way to create commands in a console system with history and tab to autocomplete commands. So I’m looking forward to that. SmartConsole has those features and is pretty nice but seems outdated. I like the way commands are created with CMD+ but it doesn’t have tab to autocomplete and I’m not sure what would happen if the console got too large. One of the assets I was testing had a report that after 65k characters or something it would give an error which they worked around by removing lines I think.

Anyway, I tested this in Unity 2017.1.0p2 but was unable to get it to work. I guess this explains why none of the boxes in the readme file for 2017 have an X. I’m on Windows 10.

First there is no default settings.xml file that it could find and it gave an error that it couldn’t find it. I even typed it out but it still won’t work. Saving the settings from the Tools > Debug Tools > Settings didn’t seem to create the file and so I created it myself but it didn’t seem to update it for me for some reason when saving.

Once I typed out the settings file as shown in one of the images on the asset store it still wouldn’t work. I would still get this error:
Error

ArgumentOutOfRangeException: Argument is out of range.
Parameter name: index
System.Collections.Generic.List`1[UnityEngine.Vector2].get_Item (Int32 index) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:633)
DebugTools.GraphCanvas.UpdateTexture () (at Assets/DebugTools/Scripts/Grapher.cs:229)
DebugTools.GraphCanvas.Update () (at Assets/DebugTools/Scripts/Grapher.cs:210)
DebugTools.Grapher.UpdateAllGraphs () (at Assets/DebugTools/Scripts/Grapher.cs:46)

Then I started working on fixing the issues myself. I found that the issue with the settings.xml not being created was caused line 70 in DebugToolsSettingsEditor.cs had to be changed to this:

            string filePath = Application.dataPath + "/DebugTools/";

It would then save the settings.xml file ok for me.

Editing the console key proved to be a difficult task. I could not get it to change. It only seemed to click the underlying options on the settings panel. Trying to use the keyboard to scroll through the options resulted in my computer crashing, giving me a BSOD.

At this point I gave up and luckily this website saves forum posts so here you go =)

Hey, thanks for trying out the package and I’m really sorry you ran into so many issues. I’m working on those as we speak and will hopefully be pushing an update in the next few days correcting the issues.

No worries, I kind of expected bugs in an alpha release. I just thought I’d give some feedback and report the issues so you can fix them. I’m now thinking that the BSOD crash was possibly something else to do with my computer though, as I don’t know why scrolling in the menu would have caused that.

This is what the new settings panel is currently looking like at the moment, currently there are only a few options per tab though this will grow as features are added and requests are made for more options. I’m hoping to submit this update on Monday and have it live by Wednesday next week.


I’ll also try get around to doing some testing on Unity 2017 and try fix any compatibility issues that might have been occurring. I have yet to install 2017 yet as I’m not upgrading my other projects so have been working on just 5.6