All OOTB support files should be consolidated into fewer directories and files.

[NateBrush]

All OOTB support files should be consolidated into fewer directories and files.

For example, filled regions patterns are stored in multiple files in multiple sub-directories

C:/Program Files/Autodesk/Revit <version>/Data contains two hatch pattern files that do not include all of the OOTB hatch patterns.

C:/Program Files/Autodesk/Revit <version>/ACADInterop contains several additional linetype and hatch patterns.

Nothing within Revit (at least nothing obvious while trying to modify hatch patterns) directs users to these support files. I had to search multiple forums to find the first directory, test the hatch files, fail, search more forums to find the second directory, and test the hatch files until I found the pattern I wanted.

Revit button/Options/File Locations should house the default directories for all user support files including linetypes, hatch patterns, families, etc. It should not take 45 minutes to find how to load and rescale a hatch pattern that is loaded by default.

[hugha]

Not intending to detract in any way from this idea by pointing out that the HatchKit Add-In for Revit allows the creation of rescaled and rotated versions of fills directly from fills already present in the project rather than by accessing external .PAT files.

[NateBrush]

Is that an Autodesk Add-in? I think I have all of the official extensions for versions 15 through 17. Maybe I missed one.

[dplumb_BWBR]

Yes, HatchKit is an add-in

However, Revit 2018.2 (which just came out this week) now allows you to scale an Pattern that's already loaded.

http://blogs.autodesk.com/revit/2017/10/11/revit-2018-2-update/

[Anonymous]

I really like this idea of consolidation! Let's take it one step further and say that all support files... hatches, material images, bump maps, etc. for EVERY APPLICATION be centrally located to one location. We have hatch patterns for AutoCAD, Revit, and who knows what else. We have material images for Revit, 3ds Max, and who knows what else. Just put them all together, and share them between the applications.