
And considering that some standard Autodesk materials are deemed propriety and therefore don’t transfer to Lumion, it might just be a good idea to create an entire library of custom materials and assets. In this video blog, I show how you should share your custom materials with others. These textures are then applied to assets, with which in turn are applied to the material.

It is, therefore, useful to consider a folder in which textures are placed. Immediately I thought of e-transmit for Revit, but while trawling blogs it became apparent that custom textures were not in included in the transmittal. When I asked the client for these missing textures they, in turn, indicated that the file was in turn shared with them by an Architect and that the textures were not available to them either.

This question presented itself to me when a client asked me to render a Revit file they shared with me. Sharing Custom Revit Materials What is the correct way to share custom Revit materials with others?
