Search Issue Tracker

Fixed in Unity 2018.2

Votes

1

Found in

2017.2.0f3

Issue ID

963958

Regression

Yes

When a class inherits from StateMachineBehaviour into a DLL, Unity does not reference it

Scripting

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 3Secondary functionality broken

Steps to reproduce:
1. Extract the attached archive into a folder
2. Open the Visual Studio solution located at DLLTest/DLLTest.sln
3. Look at the file DLLTest/TestMonoBehaviour.cs. It inherits from MonoBehaviour
4. Look at the file DLLTest/TestStateMachineBehaviour.cs. It inherits from StateMachineBehaviour
5. Add the references to the splitted dlls(UnityEngine.AnimationModule.dll, UnityEngine.CoreModule.dll, UnityEngine.dll) located inside a Unity folder(e.g. D:\Program Files\Unity\2017.2.0p3\Editor\Data\Managed\UnityEngine) and set Copy Local to False
6. Build the solution (The VS project is configured to put the generated dll into the Assets folder of the Unity project)
7. Open the Unity project located at the root of the archive
8. In the Project view, expand the dll DLLTest
9. The class TestMonoBehaviour is found but not the class TestStateMachineBehaviour

Actual results: The class TestStateMachineBehaviour is found
Expected results: The class TestStateMachineBehaviour should be found

Note:
It reproduces with the full dll(UnityEngine.dll) as well located inside a Unity folder(e.g. D:\Program Files\Unity\2017.2.0p3\Editor\Data\Managed)

Reproduced with: 2017.2.0p3, 2017.3.0b11, 2018.1.0a6
Not reproduced with: 2017.1.2p3

Fixed in: 2018.2.0a1
Backported to: 2017.3.1p2, 2018.1.0b7

Comments (3)

  1. 29aefb02435fd63f9fb4f4e09548f5d8?d=mm

    Nakano37

    Mar 20, 2018 21:39

    We are still seeing this occur in 2018.1.0b7

    when you search in your project for a class that extends StateMachineBehaviour it doesn't show up. When you search in your project for a class that extends MonoBehaviour it does show up.

  2. 3e38b5dbf851479c2cb44405ca902fae?d=mm

    talgeer

    Jan 28, 2018 04:43

    The issue is marked as resvoled. Can we know when the fix will be available ? This issue is still here in 2018.1.0b4

  3. 426a7aaddbd58244afea144e4eaff50a?d=mm

    fxanimation

    Dec 20, 2017 15:09

    Also reproduced with 2017.3.0f2 and 2017.3.0f3.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.