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’.
xDoc.XDocAssetManagerAssistant:.cctor() (at Assets/Editor/xDoc-FreeReader/Scripts/XDocAssetManagerAssistant.cs:18)
xDoc.XDocAssetManagerAssistant:.cctor() (at Assets/Editor/xDoc-FreeReader/Scripts/XDocAssetManagerAssistant.cs:16)
Checked the assignments, everything looks fine. Unity 2018.3
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:
- After update in the asset store window the “import” button did not appear. So I restarted the editor and there it was.
- 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.
- 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!
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 😉
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.
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
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.