2005-02-22 11:56 AM
2005-02-24 12:58 AM
2005-02-24 01:04 AM
2005-02-24 04:33 AM
ashok_hj wrote:Sorry that I was on vacation and couldn't reply sooner.
Now iam working on quantity analysis in archicad,In my project i have used composite section like a strut wall,since strut wall is made of gypsum board on either side and empty gap in the centre,Iam able to get the component list and also know to customise the component list,but when i use to get the volume of this composite section,it considers the complete thickness of composite wall which i dont want,i want it to consider only the gypsum part only,is there is any way to get it.
2005-03-13 09:59 PM
2005-03-14 01:36 AM
MarinRacic wrote:Hi Marin,
Does this mean I need to make property scripts for every type of composite I have defined? Calculation Guide manual wasn't very helpful as all the examples noted there I can do also through Interactive Schedule.
What I need is to calculate, for example, volume of structural concrete in an external composite wall as easy as possible. How can I do it?
2005-04-19 10:46 PM
Karl wrote:When is this "passion" going to become a comprehensive, coherent book? I'll send you my $10 now!
...I get very passionate about the Calculation possibilities...
2005-04-20 12:13 AM
Karl wrote:This is definitely the direction Graphisoft should take with the calculations. It doesn't make sense that I could have the graphic representation of a brick veneer wall but could have a composite script that actually calculates a wood siding wall. Very non-intuitive.
... Each MATERIAL has take-off information associated with it, and so when you build a composite wall there, you are building skins made of Materials (with self-knowledge, if you will), not "dumb" drafting fills as we do in ArchiCAD.
The net result, is that if you script how a brick wall take-off is computed, then if you use that brick wall as the outer skin of a brick, air, CMU or brick, concrete, or brick, air, frame wall (etc) ... you don't have to write a script for the composite as we do and figure out what each skin is ... thus computing bricks in every composite associated script, but rather just one time when you define bricks. Chief does not have the computation flexibility of ArchiCAD, but this concept has a lot to offer.
If you agree, add your vote to this wishlist item:
http://archicad-talk.graphisoft.com/viewtopic.php?p=34077#34077
Karl