AssetIndexer Error: 2018.3.0f + UMA 2.8RC3 Win10 about uma

[kenamis]

"Not sure if this is "serious" - the DCS Demo scene appears to work", did you mean "appears not to work"?

Are you by any chance, upgrading from a previous version of UMA?

[dza6549]

lol @kenamis I'm a coder - so I always say "appears" - without any real testing and especially if I am just starting out - I may have missed a button.

I've just gone through the examples and they all work fine. (Female expressions don't work - I'll let you know when I play some more)

No this is a clean install of RC3 on an empty 2018.3 project.

Do let me know if I can help out tracking this down. Cheers

Edit: Female expression work fine I was mistaking the controls

[jwvanderbeck]

Getting the same errors. Unity 2018.3.4f1, UMA 2.8 RCS from Github, clean install into new Unity project. Downloaded the .unitypackage and imported.

Only other assets in the project are Cinemachine and the new NavMesh Components

Unable to load the AssetIndexer. This item is used to index non-asset bundle resources and is required.
UnityEngine.Debug:LogError(Object)
UMA.UMAAssetIndexer:get_Instance() (at Assets/UMA/Core/Extensions/DynamicCharacterSystem/Scripts/UMAAssetIndexer.cs:109)
UMA.CharacterSystem.UMAAssetPostProcessor:OnPostprocessAllAssets(String[], String[], String[], String[]) (at Assets/UMA/Core/Extensions/DynamicCharacterSystem/Scripts/UMAAssetModificationProcessor.cs:14)
UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets(String[], String[], String[], String[], String[])

[kenamis]

Sometimes I can get the error to appear too when upgraded from a previous version of Unity, but it doesn't prevent compile and everything still works. The error goes away after the first run. @jwvanderbeck are you not able to run the scenes at all?

I think the issue is with Unity not loading the Resources in time which is odd.

[kenamis]

@Jaimi
http://www.createdbyx.com/post/2013/02/17/Unity-Tip-101-55-%E2%80%93-InitializeOnLoad-ResourcesLoad-gotcha%E2%80%99s.aspx

Maybe a simple solution would be to use "AssetDatabase.LoadAssetAtPath" instead?

[Jaimi]

AssetDatabase is not available outside of the editor. I will put in a change to delay load the AssetIndex in the editor utilities, and then remove the warning when it is null. We only put it in because one person deleted the file, causing it not to be found. Being not found in the post processor is not a problem, so it shouldn't warn anyway. Fixed in Release-28-prep