Treat scale as project information
The first decision is the real-world size of the repeat. A brick texture might be measured by unit width and height, while boards, tiles and panels have their own module and joint logic. If the bitmap looks correct but the repeat dimensions are wrong, every elevation, render and material take-off derived from it becomes misleading.
Record the module, bond or layout, joint width and orientation before export. In the receiving application, verify the result against a known model dimension rather than judging it by eye.
Coordinate appearance and linework
The rendered appearance and the drawing hatch serve different purposes. The texture carries color and surface variation. A bump or normal map suggests small relief. Roughness controls how broadly the surface reflects light. The hatch provides scale-independent or model-scaled linework for drawings.
These outputs should describe the same material geometry, but they are not interchangeable. A hatch does not need photographic material data, and a raster texture cannot replace legible drawing conventions.
- Use the same unit dimensions for texture and model-pattern exports.
- Keep drafting hatches simple enough to print clearly.
- Check map strength in more than one lighting condition.
- Retain the source recipe so the material can be regenerated.
Validate inside Revit
Host applications interpret scale, map channels and pattern files differently. Import into a test project first, apply the material to a known object, and inspect both a rendered view and a printed drawing. Check rotation, repeat seams, unit conversion, pattern density and whether linked files remain available to the team.
The Architect Assets plugin is intended to reduce setup work, but the website and exported package remain the fallback. A plugin is a convenience layer; project validation still belongs in the target Revit version and template.