A hatch library saved me from texture headaches

I was getting different hatch results every time I opened a file. Creating a shared library for my team means we all use the same patterns now, and it's cut down on revision time by a lot.

3 comments

3 Comments

patel.leo1mo ago

Forget the patterns, the real win is stopping the blame game. We had a project where a wrong hatch from an old library almost caused a site delay because everyone pointed fingers. A single, checked library means when something prints wrong, @the_abby, you fix the root cause once for everyone, not fifty personal sets. It turns arguments into quick fixes.

the_abby1mo ago

Seriously? I've found shared libraries cause more headaches than they fix. They lock everyone into the same broken patterns and nobody can adjust things for their own projects. We tried that and it just meant any weird file from outside our team would still explode. Now I just keep a personal set I know will work and accept the five minutes of resetting on shared sheets. It's less trouble in the long run.

charlie_hernandez521mo ago

What was the worst part of it for you guys? I mean, we had a shared set that sounded good in theory, but then you'd get a pattern that just wouldn't scale right on bigger drawings, or the colors would come out weird on certain printers. Felt like we spent more time fixing the 'standard' stuff than if we just did our own thing. Maybe it's just me but that locked-in feeling makes small changes take forever.