The asset library of resources can not be included in the software installation package in the first place, so that the volume of a software installation package can be saved.
Then we can download the resources of the asset library directly into the local computer after we install the software and start using it, instead of having to download again every time we open the asset library.
In fact, the user experience is really poor due to the loading problem 
Hi @tas_1985 ,
thank you for reporting this issue! The performance of the Asset Library was one of our major concerns during the development process and this type of behaviour should not occur.
Could you quickly confirm, that you’re using the new release version instead of one of the recent preview versions?
With the release version we actually deploy the information used by the asset library, so the only requests to our servers are the ones done when searching something on the Asset Library. This however shouldn’t require large transfers of data.
If you are already using the current release version, could you please try reinstalling it?
I just ran the 2.5 installer (instead of the ‘release candidate’) and it’s a big difference. The library runs much smoother.
I uninstalled the software and cleaned it up before reinstalling it
I did a detailed test, and sometimes it didn’t even start up, but other times it often did, as I mentioned on the second floor of this post, where a “server is running” window appeared while the asset was being placed and I couldn’t continue working
As I have suggested in the Preview thread, the asset library shall be placed somewhere in the network drive and shared across the office.
Then, allow the Asset Library to run as a standalone application EXE and give the users the possibility to download ALL available assets to that network drive.
This will solve the speed bottleneck issue.
There are a number of people who complained about slow loading time due to asset (re)downloading at each start up of Enscape.
Please look at how ArchVision dashboard is working (it has been working well for 10+ years and there are reasons behind it)
Anyway I know the team has been working very hard, it will only get better :thumbup:
@tas_1985 Thank you for attaching the video, this greatly improved my understanding of the issue you are experiencing!
Would you be so kind to send us a feedback, so that I can take a look at the created log files? (it would be best to mention my name, so that it reaches me directly)
The inconsistency in your experience surprises me… For each Asset used in your scene we first look on your local filesystem if that Asset already exists. Only if the data is not available, we download the Assets. This means, once you’ve downloaded an Asset, you will use the local version and don’t have to download that Asset again.
@joeykeys We’ve noted the request to specify a specific location to store the Asset data. We definitely want to implement this possibility - stay tuned
I sent a feedback and mentioned your name, hoping it would help improve the situation
