Transform Changes Debugger API

This tool will enable you to view and debug changes to position/rotation/scale on any transform done by any method/setter on a frame by frame basis.

It'll will work with code that executes changes via property setters (eg Transform.position = newValue) but also more complex methods (eg Transform.Rotate(1f, 230f, 15f, Space.Self)).

Changes can be originating from any assembly - not only your code but also 3rd party libraries or Unity assemblies.

There are 4 core features that this documentation goes into more detail:

1. View changes to position/rotation/scale of any transform in easy to use GUI on a frame-by-frame basis (more details)
2. Identify and view specific TransformModifiers (specific game object instance and script/method combination that initiated change (eg. Mover-1-GO via TestMove.cs script, method MoveTransform()) (more details)
3. Enable you to easily skip changes originating from specific TransformModifiers (at runtime, without need to recompile) - this means you can identify offending code by isolating specific changes (more details)

The best place to start are demo scenes, 1st one 'HardToPinpointIntermittentJitter' will show you all that's needed to start tracking

API and Full GUI Tool

Code in this repository is core API used in full tool that has an easy to use and intuitive GUI built on top.

You can see tool in action on this quick 1 minute video - it'll show you what's possible with the API.

I've put a lot of time to make the end tool fast and easy to use. If API is of use to you - full GUI tool will save you a lot of time.

Please consider purchasing the full GUI enabled version direcly on site or via Unity Store if you'd like to support development!

Transfor Changes Debugger GUI - Website

Scrennshots are from GUI version althought they are still relevant as they show what API can do.

Setup / Quickstart

Have a look at HardToPinpointJitter scene HardToPinpointJitterDebugger.cs script - those will give you basic idea how API can be used.

1. Add TrackTransformChanges script to objects you want to tracked
2. Initialize tracking:

    TransformChangesDebuggerManager.IsTrackingEnabled = true;
    TransformChangesDebuggerManager.Initialize(allAvailableAssembliesToPatch, userChosenAssembliesToPatch);

Viewing Change Details

All changes done in any frame can be retrieved via TransformChangesTracker.GetFrameChangesForTrackedObject and will provide:

• Originator - script instance that the change originated in. [click to see it in Hierarchy View]
• MethodName - actual method in the script where the change originated. [right click on the node title and choose 'goto code' to view the method in your code editor]
• Rotation \ Position \ Scale - (changes depending on node type) - value after the change has been made
  • ValueBeforeChange can be retrieved from code (see API details)
• Original Method Call - actual method call that caused transform change
  • Name - the name for method, in case of setters this will be set_xxx
  • Method Arguments - arguments passed to method

Relevant API

TransformChangesTracker.GetFrameChangesForTrackedObject

Modifiers Details

Changes visible on screen are grouped by TransformModifier - that is a specific change to object that originated from specific game object instance via script using specific method. This panel breaks them down to better illustrate which objects are changing tracked transform.

For example one of TransformModifiers on the screenshot is Mover01 game object that's modifying tracked object via TestMover script, in RotateObject method.

Relevant API

TransformChangesTracker.GetModifiers

Temporarily Skipping Specific Changes at Runtime

The tool will allow you to quickly isolate TransformModifiers that could be causing issues - this can be done by temporarily disabling changes made by them.

Simply tick the 'disable changes' checkbox next to the modifier and resume the game. Any change made by modifier will now be skipped. The actual change node will still be registered by the tool and the title will indicate that it was 'SKIPPED'

Relevant API

TransformChangesDebuggerManager.SkipTransformChangesFor

Capturing Changes - Configuring Sources / Assemblies Bar

The tool will find all calls to any transform modifying methods (eg setters [set_position, set_rotation] but also more complex methods like Transform.Rotate(1f, 230f, 15f, Space.Self)). This happens directly in memory so no assembly files are actually modified. This process can add some time to entering play mode.

By default only changes originating from your own User Code - Assembly-CSharp.dll will be captured. Of course, this can not be enough if change originates from say 3rd party library.

You can use the bottom Assemblies bar to configure which assemblies should be included. Simply use the tick box next to the name.

Relevant API

You configure assemblies that are patched with initial TransformChangesDebuggerManager.Initialize call. Later you can also patch assembly at runtime via TransformChangesDebugger.API.TransformChangesDebuggerManager.EnableChangeTracking

Performance

When you're processing assembly for the first time - tool needs to find all the methods that should be patched. That's most time-expensive part of the process but it only happens once (as long as assembly is not recompiled) - that means 3rd party / Unity libraries need to execute 'find' step just once to build cache. After that, search step is not executed and instead only patching happens - which is much quicker. If patched assembly is recompiled tool will also re-run search step and update cache.

You can see performance statistics around patching times to help you decide if specific library is needed.

This greatly improves workflow and helps keep entering play-mode time well under 0.5s.

Assemblies will be only processed if there's at least 1 TrackTransformChanges script in the scene, you can have the tool imported into the project ready to be used without any performance cost if you're not using it.

Quickly Disable Tool to Save Time

You can very easily turn whole patching process off by turning the tool off with 'record' button in top bar.

Relevant API

TransformChangesDebugger.API.TransformChangesDebuggerManager.IsTrackingEnabled

API Usage - Advanced

The tool exposes easy to use and documented API that you can use directly. Following section will document what's possible.

Adding Custom Code to Handle Changes

You can execute custom code in response to any tracked change. The easiest way to do that is to use UnityEvents on TrackTransformChanges, PositionChanged, RotationChanged and ScaleChanged. They give you access to TransformChange which has change data (API Reference)

You can also use TransformChangesDebuggerManager.RegisterCallbackFor[Position/Rotation/Scale]Changes to register your custom callback. Eg. have a look at ApiUsageExamples.cs

TransformChangesDebuggerManager.RegisterCallbackForPositionChanges(InterceptFor,
    (ilWeavedValues, newValue) =>
    {
        Debug.Log($"Intercepted scale change: {newValue} " +
                    $"{ilWeavedValues.CallingFromMethodName} {ilWeavedValues.CallingObject?.name ?? "StaticCall"} " +
                    $"{ilWeavedValues.ChangeType}");
    }
);

Will produce following result on changes:

Intercepted scale change: (0.0, 0.0, 0.0) TestMover.SetTransformValues() Mover02 Scale
Intercepted scale change: (1.0, 1.0, 1.0) TestMover.SetTransformValues() Mover02 Scale
Intercepted scale change: (2.0, 2.0, 2.0) TestMover.SetTransformValues() Mover02 Scale

Skipping Specific Changes

You can have more control over which changes are skipped (at runtime) by calling TransformChangesDebuggerManager.SkipTransformChangesFor and passing ShouldSkipTransformChangeExecutionPredicate.

For eaxample following setup would skip any changes made to object named DoNotChangeIfCallingFromSpecificMethod when change is coming from method name TestMover.SetPosition.

TransformChangesDebuggerManager.SkipTransformChangesFor((ilWeavedValuesArray, changingComponent) =>
{
    if (changingComponent.name == "DoNotChangeIfCallingFromSpecificMethod" && ilWeavedValuesArray.CallingFromMethodName == "TestMover.SetPosition")
    {
        return true; //true will indicate that change should be skipped
    }
    return false;
});

To unregister you simply call TransformChangesDebuggerManager.RemoveSkipTransformChangesFor passing in the same predicate.

Enable/Disable Tool

Change TransformChangesDebuggerManager.IsTrackingEnabled

Drawbacks / Limitations

Physics

Currently physics (eg changes done via Rigidbody or gravity) will be treated as mismatch. If you're debugging transform that's misbehaving then it's best to temporarily turn gravity off. If physics is indeed the cause of the issue then this tool will not be able to help you at this point.

Please let me know if that's important to you, while it's not officialy supported I'll look into improving that part if there's enough interest.

Debugging Original Code

When tool is enabled, calling code will be adjusted in memory that means yo