Unity PKG Assets randomly showing up

Please help, Unity 2017 seems to be very strange, in some project some of my pkg assets are working in some project they don't appear. Assets like alembicimporter, substance link etc. I'm starting to be afraid to work seriously with Unity, I've spend 3 months to make a pipeline R&D and it's almost finish , Unity is very good but i cannot afford those kind of issues during real production.I need to install several packages as start up projects... I'm focusing in cinematic and filmmaking and i have some difficulty to work on it. Thanks guys

 

You're going to have to provide more details than just they are randomly showing up. Anything in the editor log? Are the assets still in the Assets folder when you look through Windows Explorer (or the mac equivalent)? What type of assets are these? Do you have compile errors?

 

Yes the assets are still in the folder , i'm using assets like alembic importer, deep sky haze, substance painter link...kind of basic assets to complete unity's features for filmmaking as error i get this

Assets/UTJ/Alembic/Editor/Importer/AlembicImporter.cs(31,17): error CS1061: Type `UnityEditor.Experimental.AssetImporters.AssetImportContext' does not contain a definition for `AddSubAsset' and no extension method `AddSubAsset' of type `UnityEditor.Experimental.AssetImporters.AssetImportContext' could be found. Are you missing an assembly reference?

As an artist it's a chinese language for me . Here is my first rendering test

and i'm about to get deeper and add complex character animations and FX but now i have this assets issues

@JeffDUnity3D no i'm not using source control

Thanks guys

 

AlembicImporter.cs is apparently using the experimental AssetImportContext class. Experimental features are prone to frequent changes before they are completed and ready for general use, and as such their implementation can differ drastically between different versions of Unity. Think of them like alpha or beta tests of unfinished features. You should see if the author has updated versions of these 3rd party assets which are using experimental features of Unity, for the version of Unity you are using.

For example, in your first error the problem is AssetImportContext.AddSubAsset does not exist in your version of Unity. That is because that experimental API changed between 2017.2 and 2017.3 as that feature has further developed.

2017.2 docs:
https://docs.unity3d.com/2017.2/Doc...mental.AssetImporters.AssetImportContext.html
Latest docs (currently 2017.3):
https://docs.unity3d.com/ScriptReference/Experimental.AssetImporters.AssetImportContext.html

So when using experimental features of Unity, your choices are to use the version of Unity your 3rd party scripts were written for, get updated versions of 3rd party scripts that reimplement usage of updated experimental features of Unity as they change, or rewrite the scripts yourself to reflect changes to experimental API's.

If you continue to have trouble with this experimental feature, the correct forum to talk about it is over here:
https://forum.unity.com/forums/experimental-scripting-previews.107/

 

This is getting very complicated for an artist like me. Is this a good idea? i'm going to use Unity 5 from now, it seems more stable and most of the old assets are working. Cinemachine and Timeline will be replaced by something like cinema director assets etc. So instead of the Adam era, i will stay inside the Blacksmith era.

 

SOLVED for those who will face this issue Here is the link to get the updated alembic importer https://github.com/unity3d-jp/AlembicImporter/releases

also
Alembic Importer is now integrated so you can go Asset>Import New Asset and point to a .abc file. You will see the abc file asset in your Asset folder You can then drag drop the abc into your scene. To playback the alembic:
1. Hit Play, and the alembic stream will kick in.
2. In Timeline, add Alembic track, add Alembic clip, then link the abc scene obj in the ‘Stream