Search Issue Tracker

By Design

Votes

5

Found in

2022.2.5f1

2023.1.0b2

2023.2.0a3

Issue ID

UUM-27638

Regression

Yes

ScriptableObject's properties are not displayed in the Inspector Window when it's definition class is split in multiple files

-

Reproduction steps:
1. Open the “Duplicate Files Issue” Project
2. In the Project Window select “Assets/Foo” ScriptableObject
3. Observe the Inspector Window

Expected result: “Foo” ScritableObject’s properties are displayed in the Inspector Window
Actual result: “Foo” ScritableObject’s “Bar” and “Baz” properties are not displayed in the Inspector Window

Reproducible with: 2022.2.0a5, 2022.2.5f1, 2023.1.02b, 2023.2.0a3
Not reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.2.0a4

Reproduce on: Intel MacOS 13.1

Note: If you select “Assets/_First Definition/Foo.cs” Script and select “Debug” in the Inspector Window, you can observe that the “Namespace” property is empty. The same is applied to “Assets/_Second Definition/Foo.cs” Script

  1. Resolution Note:

    As stated in the log, partial MonBehaviours/ScriptableObjects needs to have 1 file thats named the same as the class.
    Files are our stable ID's for referencing, ie. GameObject attaching Script, or serialization, and because of that we need to be able to always find 1 and the same file every time.
    The error is an improvement to preemptively help fix issues related to this area

Add comment

Log in to post comment