Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Glue reloads all the models in a merged models every time anyone glues. Not only do you have to wait for the merged model to completely reload, you have to open each clash report and wait for all the models to reload. If only one model changes,why do they all reload? Also, if the merged model is refreshed, why do you also have to refresh every clash report. We are spending way too much time in our meetings waiting for refreshes.
Agreed. Is there a way to cache the models locally when there is a new version. Not sure if it would speed up the refresh, but it seems to be downloading a packet of information during the refresh process. This would probably require pings to the cloud every couple of minutes to check for updated versions which would then trigger a download in the background. Once downloaded, then Glue would say, "a new version is available", then once your click, it would just be loading into the render engine...
I don’t think caching the files would help that much. Each file downloads and refreshes pretty quickly for me. What takes the time is refreshing all the models that DIDN”T change. As many as twenty on some projects.
It just a matter of Autodesk refining the refresh process.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")