Error after import

Solved680 views
0
0 Comments

xDoc Error: xDoc can’t load its Asset Resources!
Most probably the script assignments of xDoc’s scriptable objects got lost. These objects are located in the ‘Assets\Editor Default Resources\xDoc-FreeReader\Config’ folder. Either reassign them, reimport a working backup or contact support.
If you need the support link or email addresses, please refer to the xDoc tab in the Unity Preferences: ‘Edit’ menu -> ‘Preferences…’ -> ‘xDoc’.
UnityEngine.Debug:LogError(Object)
xDocBase.AssetManagement.AssetManager:ForceInit()
xDocBase.AssetManagement.AssetManager:.cctor()
xDoc.XDocAssetManagerAssistant:.cctor() (at Assets/Editor/xDoc-FreeReader/Scripts/XDocAssetManagerAssistant.cs:18)
xDoc.XDocAssetManagerAssistant:.cctor() (at Assets/Editor/xDoc-FreeReader/Scripts/XDocAssetManagerAssistant.cs:16)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes()
Checked the assignments, everything looks fine. Unity 2018.3

Question is closed for new answers.
Selected answer as best
1

Version 2.0 is published in the Unity Asset Store.

I have run a quick test: created a new project, updated xDoc from within the editor asset store window, imported it and now it works.

A few comments though:

  1. After update in the asset store window the “import” button did not appear. So I restarted the editor and there it was.
  2. After importing xDoc, the xDoc window was complaining about missing resources. So I restarted the editor and the error was gone and xDoc is running.
  3. One last bug I recognized is showing up while setting the colors. It is not a show stopper. It is possible to set the colors, but the user experience is not good and the editor might need to be restarted: The color picker does not work – so please don’t use it. Instead click into the color field, select a new color in the popup window and close the popup window by clicking the “x” in the top right corner.

But all in all,.. It works now 🙂 so download/import it and enjoy.

And thanks a lot for reporting and the feedback!

Posted new comment

I have imported xDoc Ver2.0 into Unity 2018.3.5f1 (create new project).
I get 11 warnings and 1 error.
Since it is possible to add Annotation with “Add Component”, it seems that it operates.
However, I do not know whether all the functions are working properly.

————————
xDoc Error: xDoc can’t load its Asset Resources!
Most probably the script assignments of xDoc’s scriptable objects got lost. These objects are located in the ‘AssetsEditor Default ResourcesxDoc-FreeReaderConfig’ folder. Either reassign them, reimport a working backup or contact support.
If you need the support link or email addresses, please refer to the xDoc tab in the Unity Preferences: ‘Edit’ menu -> ‘Preferences…’ -> ‘xDoc’.
UnityEngine.Debug:LogError(Object)
xDocBase.AssetManagement.AssetManager:ForceInit() (at Assets/Editor Default Resources/xDoc-FreeReader/Scripts/Scripts-Base/AssetManager.cs:247)
xDocBase.AssetManagement.AssetManager:.cctor() (at Assets/Editor Default Resources/xDoc-FreeReader/Scripts/Scripts-Base/AssetManager.cs:168)
System.Object:__icall_wrapper_mono_generic_class_init()
xDoc.XDocAssetManagerAssistant:.cctor() (at Assets/Editor Default Resources/xDoc-FreeReader/Scripts/XDocAssetManagerAssistant.cs:16)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes()

Does the error persist after an editor restart?

Error is exactly the same after your update. Asset is unusable..

Please check out this video, which I hastily put together just now: https://youtu.be/xs9jLVxh18c

Please check, what we are doing and what you are doing. And report what is necessary.

There is an error right after the installation, but a restart of the Unity Editor fixes it and it does not appear again and xDoc is functional as it should.

The tests were conducted on a fully upgraded windows 10 machine.

Please also check the Unity Editor version. If you are using a different editor version, please feedback, so we can test against it as well.

I am not fully aware of Unity’s return policy. And just in case all this is too much of a hassle for you and you do not want to spend any more effort into this, please contact Unity to get your money back.

Or give me more input and feedback, so I can sort it out.

0

OK, I have uploaded a new version of xDoc to the asset store and we are now waiting for the approval. This is now version 2.0.

As a special bonus all source code is published as well.

The asset upload tool alerted a small error. But the community suggest to ignore it, as it is not relevant. We’ll see in a few days hopefully. Stay tuned 😉

Posted new comment

ok, thanks Selim. I´ll check as soon as its available

0

Thanks for your support Ben. I have found the “bug” and debugged. Now I have to put together a new package and publish it in the asset store. The asset store needs a couple of days until they approve a new release.

If you are interested about where this error came from: Unity expanded their namespace and so invaded my namespace. The error message was a bit misleading,.. yupp.

Answered question
0

Just tested, its the same on a blank project

Answered question
0

Hi,

it´s an existing Project. We use collab. It´s the first time i use it, will try on empty project later.
Plan is to use it as team via Collab

Posted new comment

Let me give a quick answer on this. I have to elaborate further, but this might already help.

Do not import xDoc, if you are working as a team. Rather let one team member import it, then every other has to get it via the versioning system. You need these two directories:
AssetsEditor Default ResourcesxDoc
AssetsEditor Default ResourcesxDoc-FreeReader

The reason are the serial objects, which store the xDoc config (different types of annotations, etc.). Each serial object is referred to by a hash number, which is created by Unity on the fly **locally** (means the local computer). So you need one leading system, creating these hash tags/ids and the others follow. If every team member is maintaining their own independent copy of xDoc, the serial objects of xDoc wont be in sync.

To be more specific. Let’s say you have a game object with an annotation of type “comment”. The annotation type is a serial object, with a hash id, which is created when imported. The annotation has this hash id as a reference and you want to make sure every team member has the exactly same hash id/number.

I hope I could somehow explain it. Please tell me, if I was not clear enough or it that was not the source of the problem.

Thats what i did. The error is instant after import. No one else touched it

0

I have a few questions please.

Do you try to import xDoc to a new and empty project? Or is it an existing project? Or is it an existing project in which xDoc is already being used?

Did you copy all or parts of the project via the unity editor, the OS or a versioning system? Do you use a versioning system?

Did you use xDoc before and everything was fine till now, but just now it is throwing the error?

Do you have backups or older versions? Do they work?

Are you using xDoc in a team or just by your own?

Meanwhile I’ll be installing Unity 2018.3 and have a closer look. We should try to fix this latest over the weekend. During the week I will have only limited time unfortunately.

Changed status to publish