sasapositive.blogg.se - Textures not showing up in sl cache viewer

#TEXTURES NOT SHOWING UP IN SL CACHE VIEWER HOW TO#

Here, you’ll see the Projects/Folders you have access to on BIM360, emulated on your local storage. If you have Desktop Connector installed (get it here), a folder path called BIM 360 exists in your User Profile, when you are logged in to your Autodesk Account. But first, why we went the way we did: Strategy 01- Path ARAP to Desktop Connector We went through a few processes, for getting it to work, but the final version takes about 5 minutes to set up.

You can force-sync DC folder by querying the images using something like Read Image File in Dyn Sandbox, or a simple Desktop App.

You can Drive Letter it (using LH workaround, like for Deployments), but you have to force sync the images in DC.

You can Symbolic Link it (works for all users), but you have to force sync the images in DC, and needs admin rights to set up.

You can Straight Path (full DC path), but it forces users to play tug of war, resetting material image paths.

But i want to explain why we ended up where we ended up.

Here is how we accomplished that, using some old (and basic) workflow tricks: This has been possible using the Autodesk Desktop Connector, for some time (we will show you below), but we wanted to strategize a way to accomplish it without every user having a unique path in the Additional Render Appearance Path (ARAP) dialogue, so it could be easily deployable.

#TEXTURES NOT SHOWING UP IN SL CACHE VIEWER HOW TO#

With a number of clients working in a more distributed fashion in 2020/2021, we have seen an uptick in requests and questions about how to host Materials (and Render Assets (images) for Revit Materials) in a Cloud/distributable way, so they work correctly for all Project parties/participants.