ScriptableObject Asset values Not Viewable in Inspector anymore

[ippdev]

I updated from 2020 to 2021.2.7f1 and used the radio button to select an Asset for the Inspector field. To my surprise it showed no assets of that type to select. Going to the assets themselves they no longer show their values in the Inspector when selected. Double clicking as Asset opens it in VS and shows this

%YAML 1.1
%TAG !u! tag:unity3d.com,2011:
--- !u!114 &11400000
MonoBehaviour:
  m_ObjectHideFlags: 0
  m_CorrespondingSourceObject: {fileID: 0}
  m_PrefabInstance: {fileID: 0}
  m_PrefabAsset: {fileID: 0}
  m_GameObject: {fileID: 0}
  m_Enabled: 1
  m_EditorHideFlags: 0
  m_Script: {fileID: 11500000, guid: ba9ba6c9517b6ac42941db92e4605611, type: 3}
  m_Name: DefaultRightHandPose
  m_EditorClassIdentifier:
  handPoseName: DefaultRightHandPose
  handPoseValues:
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0
  - 0

Furthermore if I Create a new asset from the menu I get a proper asset with values until I click off it and it reverts to one of the default assets that all my other ScriptableObject assets have woefully become. What the heck is going on here?

[ippdev]

OK. I moved them out of StreamingAssets folder and they reverted. I do not like this at all. Whose idea was this?

[MaskedMouse]

@ippdev

OK. I moved them out of StreamingAssets folder and they reverted. I do not like this at all. Whose idea was this?

StreamingAssets was meant for the normal filesystem. So ScriptableObjects inside StreamingAssets shouldn’t have worked in the first place.

https://docs.unity3d.com/2021.2/Documentation/Manual/StreamingAssets.html

However, it is sometimes useful to place files into the normal filesystem on the target machine to make them accessible via a pathname. An example of this is the deployment of a movie file on iOS
devices; the original movie file must be available from a location in the filesystem to be played by the PlayMovie function.

[Bunny83]

@MaskedMouse

StreamingAssets was meant for the normal filesystem. So ScriptableObjects inside StreamingAssets shouldn’t have worked in the first place.

Exactly. StreamingAssets (despite the term Assets) does not contain “assets” in the sense of imported assets in the AssetsDatabase. The StreamingAssets folder is a way to stream in raw data at runtime that is not interpreted by Unity at all.

@ippdev

OK. I moved them out of StreamingAssets folder and they reverted. I do not like this at all. Whose idea was this?

Have you actually read the documentation on StreamingAssets? Why did you move your assets into the streaming assets folder?

[ippdev]

I was using it for its purpose…to stream data from json to initialize ScriptableObject assets which supply runtime data to a procedural animation system and visemes for an NLP application, and had been working fine until I went to check the values and it was a default asset and could not be referenced or inspected/change values in the Inspector. Moving them back out turned them back into inspectable and referenceable assets.