Search Issue Tracker

Won't Fix

In Progress in 6000.4.X

Under Consideration for 6000.2.X, 6000.3.X

Votes

19

Found in

6000.0.59f1

6000.1.16f1

6000.2.7f1

6000.3.0b4

6000.4.0a1

Issue ID

UUM-120716

Regression

No

Error Message "Broken text PPtr in file" is not informative enough to locate the problematic asset

-

Reproduction steps:
1. Create a new project
2. Import the user’s attached “REPROFILE“ to the project
3. Observe the Console

Expected result: The error message should include critical contextual information to help developers quickly locate and fix the problem
Actual result: “Broken text PPtr in file(Assets/{REPROFILE}.controller). Local file identifier (-6474349677314147615) doesn't exist!”

Reproducible with: 6000.0.59f1, 6000.1.16f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1

Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested

  1. Resolution Note:

    When we get these kinds of errors, we do not have the required information to provide context, as the file is corrupted and relationships between objects in the file are broken.

    These errors generally happen when assets are merged, which is not recommended for AnimatorControllers, as they are a complex web of dependent sub-assets.

    In order to fix the file, you need to search for the missing PPtr in the text file, and follow the chain of asset dependencies to find what refers to it. Then you can either look at previous versions of the file to identify what was removed, or delete the invalid asset from the text file if it's unused.

    In this specific case, there are multiple dangling transitions which do not seem to be used by any states, and which point to inexistent states.

    So they should be able to be safely removed.

    For reference, here is an example of transition to remove from the file:
    --- !u!1101 &5954314337809685864
    AnimatorStateTransition:
    m_ObjectHideFlags: 1
    m_CorrespondingSourceObject: {fileID: 0}
    m_PrefabInstance: {fileID: 0}
    m_PrefabAsset: {fileID: 0}
    m_Name:
    m_Conditions:
    - m_ConditionMode: 2
    m_ConditionEvent: <REDACTED>
    m_EventTreshold: 0
    m_DstStateMachine: {fileID: 0}
    m_DstState: {fileID: -6474349677314147615}
    m_Solo: 0
    m_Mute: 0
    m_IsExit: 0
    serializedVersion: 3
    m_TransitionDuration: 0.25
    m_TransitionOffset: 0
    m_ExitTime: 0.75
    m_HasExitTime: 1
    m_HasFixedDuration: 1
    m_InterruptionSource: 0
    m_OrderedInterruption: 1
    m_CanTransitionToSelf: 1

Comments (3)

  1. Roman-Ilyin

    Oct 09, 2025 10:52

    Request to backport the solution to versions 6.2 and 6.3 upon its completion. Given that the 6.4 release is not imminent, we would appreciate having this issue resolved in the current LTS versions.

  2. Snigros

    Oct 07, 2025 08:12

    I have noticed these errors appearing in the last few releases of Unity - e.g. 6.2.4f1, 6.2.5f1, 6.2.6f1 and 6.2.6f2).

    For me it seems to appear in the console after I open an animator component and then close it (even without making any changes).

    Agree the error message is particularly unhelpful. Using Windows 11.

  3. kirillgalov

    Oct 02, 2025 08:37

    Gamarjoba! It is veri important

Add comment

Log in to post comment