<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Template default pens and colours in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253290#M936</link>
    <description>2.5 weeks and still no defenders of the complex templates foisted on us.&lt;BR /&gt;
Surely someone out there likes them?</description>
    <pubDate>Wed, 25 Jan 2017 10:32:20 GMT</pubDate>
    <dc:creator>KeesW</dc:creator>
    <dc:date>2017-01-25T10:32:20Z</dc:date>
    <item>
      <title>Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253280#M926</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I must again complain about the complexity of default pens and colours in the Australian, and perhaps other, templates. What genius dreamt up so many combinations and how are users supposed to remember them? Do they even make sense?  &lt;BR /&gt;
&lt;BR /&gt;
Let’s look at text options. We have 'Annotation-general' and 'Annotation-text'. They have different line colours and thicknesses. 'Annotation text general' differs from 'Annotation -general'. In this section, text uses 0.35mm whilst headings are 0.25 mm lines. Sorry for being a bit thick for thinking that convention has thicker lines for headings as for standard text. Dimension lines are only 0.13mm. &lt;BR /&gt;
&lt;BR /&gt;
We have subtle differences between cut structural (0.20) and cut non-structural (0.18) elements. These are the same colour and I doubt if anyone can see the differences between them on a drawing or on a screen. So why do it?  Is the template the outcome of a PhD thesis or designed for practical use? &lt;BR /&gt;
&lt;BR /&gt;
So why don't I change it? Because pens and colour choice should be interrelated with materials, surfaces and object appearances. As Archicad becomes more complex, reconstructing these connections becomes more time-consuming and only academics, or those in large practices with enough spare time, can sustain this overhead expense.&lt;BR /&gt;
&lt;BR /&gt;
Subtle variations and academic distinctions do not make for sensible and memorable rules. The KISS principle has clearly by-passed the author of our templates. There is much more than can, and should, be said about our templates and I look forward to hearing views from other users.&lt;BR /&gt;
&lt;BR /&gt;
PS: Archicad-talk may have added an emoticon without my approval. Please ignore it.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 Dec 2016 04:47:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253280#M926</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2016-12-29T04:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253281#M927</link>
      <description>An emoticon has been added without my approval. It obscures (0.18) which is the point of this objection.</description>
      <pubDate>Thu, 29 Dec 2016 04:52:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253281#M927</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2016-12-29T04:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253282#M928</link>
      <description>Archicad-talk doesn't like (0.18 mm) without the 'mm' because it obscures it with an emoticon!</description>
      <pubDate>Thu, 29 Dec 2016 04:56:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253282#M928</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2016-12-29T04:56:08Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253283#M929</link>
      <description>ARCHICAD-Talk Forum considers an 8 followed by a ) as a laughing smilie.&lt;BR /&gt;
You can Edit your post, then check the "Disable Smilies in this post" checkbox to prevent that.&lt;BR /&gt;
I have done that with your original post, and so now it displays it normally.</description>
      <pubDate>Sat, 31 Dec 2016 15:46:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253283#M929</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2016-12-31T15:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253284#M930</link>
      <description>Thanks Lazio. My wife pointed this out to me after my vent.</description>
      <pubDate>Sat, 31 Dec 2016 20:31:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253284#M930</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2016-12-31T20:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253285#M931</link>
      <description>&lt;BLOCKQUOTE&gt;KeesW wrote:&lt;BR /&gt;I must again complain about the complexity of default pens and colours...&lt;/BLOCKQUOTE&gt;

So don't use them.  Make a simple pen set that is rational and easy to manage.&lt;BR /&gt;
&lt;BR /&gt;
Give the first 10 columns a pen weight/size based on the pen number.&lt;BR /&gt;
&lt;BR /&gt;
Column 1 = .1mm&lt;BR /&gt;
Column 2 = .2mm&lt;BR /&gt;
Column 3 = .3mm ....&lt;BR /&gt;
Make column 10 = .01 so you will have hairlines in every color too.&lt;BR /&gt;
&lt;BR /&gt;
Make the first Row black, the the other colors for rows don't matter.&lt;BR /&gt;
&lt;BR /&gt;
It would look something like this depending on the colors for rows you want to use.  &lt;BR /&gt;
&lt;A href="https://imageshack.com/i/pmwALI9Op" target="_blank"&gt;&lt;IMG src="http://imagizer.imageshack.us/v2/xq90/922/wALI9O.png" /&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
The point is to match the pen numbers to with the pen size so you always know what size the pen is by looking at the pen number.&lt;BR /&gt;
&lt;BR /&gt;
Pen 1 = .1mm&lt;BR /&gt;
Pen 2= .2mm&lt;BR /&gt;
Pen 3= .3mm  so on and so on.&lt;BR /&gt;
&lt;BR /&gt;
Pen 104 = .4mm&lt;BR /&gt;
Pen 228 = .8mm&lt;BR /&gt;
Pen 181 = .1mm&lt;BR /&gt;
Pen 85 = .5mm     you get the idea I am sure. &lt;BR /&gt;
&lt;BR /&gt;
This makes it very easy to keep a what-you-see-is-what-you-get relationship between your screen and your final prints.&lt;BR /&gt;
&lt;BR /&gt;
It's not that I do not understand what you can do with pen sets, it is just that I can do all of that in other ways.  I have been using this one and only pen set for about 25 years and I have never wished I had a better one.</description>
      <pubDate>Tue, 03 Jan 2017 22:39:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253285#M931</guid>
      <dc:creator>Steve Jepson</dc:creator>
      <dc:date>2017-01-03T22:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253286#M932</link>
      <description>It's worth mentioning that now with graphic overrides, you don't really need multiple pen sets. If you get GOs set up correctly once, you only need a penset with a couple of rows. (or columns) Or if your drawings are black/white/grey, you could probably get away with a single row of pens.</description>
      <pubDate>Wed, 04 Jan 2017 00:03:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253286#M932</guid>
      <dc:creator>Richard Morrison</dc:creator>
      <dc:date>2017-01-04T00:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253287#M933</link>
      <description>&lt;BLOCKQUOTE&gt;KeesW wrote:&lt;BR /&gt; There is much more than can, and should, be said about our templates and I look forward to hearing views from other users. &lt;/BLOCKQUOTE&gt;

Here is a perspective not many share with me.&lt;BR /&gt;
&lt;BR /&gt;
The only kind of Template I think is useful is the exact opposite of a what most people would consider a Template.&lt;BR /&gt;
&lt;A href="http://www.masterscript.nl/Clean-Template" target="_blank"&gt;http://www.masterscript.nl/Clean-Template&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
I much prefer to let the Template(if you want to call it that) evolve on it's own by importing only what I want, when I want it into the new project.&lt;BR /&gt;
&lt;BR /&gt;
With hundreds of completed projects, what would I use a Template for?  My past projects are all Templates aren't they?&lt;BR /&gt;
&lt;BR /&gt;
I paste or import &lt;FONT size="150"&gt;assemblies of elements&lt;/FONT&gt; into the new project and adjust them for the new conditions. I may not even import any Favorites. I don't need to load any libraries either.  Everything I need is automatically imported into the new project when it comes in. &lt;BR /&gt;
&lt;BR /&gt;
I typically work with 3 instances of ArchiCAD open. The new project that starts with the Clean-Template, and perhaps a couple of similar completed projects to assemble the new project with.&lt;BR /&gt;
&lt;BR /&gt;
I don't need to model very much from scratch anymore.&lt;BR /&gt;
Templates are for people who need to outsource the work but want it to look like they did the work inhouse.  Or for people who don't have any completed projects they did the way they would like to have done it.  That is perhaps the best argument I have seen for why a person would want to use a Template.  The project always starts out well organized and with the little extras that take some extra time but are intended to pay off in the end.  But then the time runs out and everything is in a panic to just get it out the door.  It gets real easy to tell yourself "it doesn't have to be perfect. Nobody will care anyway if the CAD file is a mess.  All that counts is the .pdf."  And so you never do have a completed project that is how it should have been done.  Whereas if you hand a Template that already is set up to keep you from needing to take so many shortcuts you would actually end up with the project done the way it should be.  That is a powerful argument for Templates.  I don't care who you are or how you work.  &lt;BR /&gt;
&lt;BR /&gt;
That being said, I still don't use them &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;</description>
      <pubDate>Wed, 04 Jan 2017 00:52:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253287#M933</guid>
      <dc:creator>Steve Jepson</dc:creator>
      <dc:date>2017-01-04T00:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253288#M934</link>
      <description>Thank you for your thoughts and comments. I have been using my list pen weight related to pen numbers for years. But...... new templates created by our vendors (e.g. Graphisoft) appear to provide advantages of integrations with objects and elements that might be worth considering. I find them too complex and almost incomprehensible. &lt;BR /&gt;
&lt;BR /&gt;
I'd like to hear someone defend these complex templates for practical work applications instead of intellectual purity.</description>
      <pubDate>Wed, 04 Jan 2017 01:07:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253288#M934</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2017-01-04T01:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253289#M935</link>
      <description>In the UK there was a webinar on pen sets but I don't recall anything in it that convinced me they were a good solution. As mentioned above I think G.O.s are the future accompanied by a single pen set. I don't see a need to have a badly flawed arrangement of setting multiple pens per component and then manipulating the appearance of the components with different pen sets when a simple GO setting can achieve the same thing.</description>
      <pubDate>Wed, 04 Jan 2017 16:59:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253289#M935</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2017-01-04T16:59:43Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253290#M936</link>
      <description>2.5 weeks and still no defenders of the complex templates foisted on us.&lt;BR /&gt;
Surely someone out there likes them?</description>
      <pubDate>Wed, 25 Jan 2017 10:32:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253290#M936</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2017-01-25T10:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253291#M937</link>
      <description>I like the Dutch template, which as far as I can tell does not use the overly complex system of pens international template (and other local templates) have.&lt;BR /&gt;
&lt;BR /&gt;
Pen 1-10 are black pens when printed with your typical pen weights going from thin to thick. They have easy to distinguish CAD-colours in the set you'd typically use when drafting, so you know when you see a red line, it is the 0,18 mm etc.&lt;BR /&gt;
21-30 is the same pen weights, but at excactly 50% grey. Great for furniture outlines (not used by default for that sadly), subdued vectorial fills, distinguishing existing structure from to be built&lt;BR /&gt;
41-50 again same weights, but red. great for MEP / fire safety / etc&lt;BR /&gt;
61-70 same weights, green great for: see red&lt;BR /&gt;
81-90 same weights, blue great for: see red&lt;BR /&gt;
101-110, black pens for cut fills at different weights / uses (can be tweaked to quickly change if wanted). I don't really use a lot of these, mostly stick to what the template offers for the building materials. I like the hairline one for clear drawings when printed&lt;BR /&gt;
91-100 white to near black grey scale, 91 is the default backgroup pen for everything in the library, great for solid hatch fills in elevations (dark grey for glass, etc)&lt;BR /&gt;
&lt;BR /&gt;
Everything else is just assorted colours you can use for illustration purposes, the only exception being pen 19, which is probably popular in other library parts as background pen.&lt;BR /&gt;
&lt;BR /&gt;
I find it easy to use, like the 5 colour options with weights that are above eachother in the pick a pen dialogue and it is easy to remember pen '1' is 0,13 mm pen, so is '21', '41' etc&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/11487iB57CD31685E9823B/image-size/large?v=v2&amp;amp;px=999" border="0" alt="penset.jpg" title="penset.jpg" /&gt;</description>
      <pubDate>Wed, 25 Jan 2017 11:22:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253291#M937</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2017-01-25T11:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: Template default pens and colours</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253292#M938</link>
      <description>Having never really been taught traditional CAD drafting practices I've always struggled with the old pen weights/colours problem.&lt;BR /&gt;
&lt;BR /&gt;
But a few years ago I decided to group things by elements into columns and have types of pens in rows... then graphisoft bought out their idea of how it should be done, so I kind of hybrid-ed their formatting and mine together as it was surprisingly similar.&lt;BR /&gt;
&lt;BR /&gt;
Unfortunately this was prior to the GO options, but as we haven't upgraded to 20 yet so it still remains useful. However with my limited experience on 20 it seems that GO's are more of a blanket override, so wouldn't perhaps be as suited to objects or other elements that require some nuance between pens for correct display.&lt;BR /&gt;
&lt;BR /&gt;
In anywise I think I'll keep the pen table I've developed, also made a handy table object to display what each of the pens are (shown attached), unfortunately GDL can't give me a numeric readout of the thicknesses...</description>
      <pubDate>Thu, 06 Jul 2017 05:39:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Template-default-pens-and-colours/m-p/253292#M938</guid>
      <dc:creator>JaseBee</dc:creator>
      <dc:date>2017-07-06T05:39:48Z</dc:date>
    </item>
  </channel>
</rss>

