Hello Enrico!

I do not fully understand your question. Attach a picture, so I can follow you. (Normally Itallians and Norwegians understand each other quite well - Uno bierra per favore is my standard Italian expression)
Talking about lists, my experience is that the three most importent issues here are:

• 1. System in the model
  2. Use IDs on all your elements/objects
  3. Use Composites in your Walls and Slabs to describe the content of the Wall or the Slab.

I haven't tried to define individual fills that make up a composite, and then see what happens when you recombine then... so I don't know, but I think it limits you. If you try that, duplicate the fill and rename it, so the same basic fill can be assigned to different wall or slab types. Maybe that would work better? Typically you create many property objects and assign them to your composites, or objects. I typically will have one wall type.. well I have many.. but one wall type might be linked to several different property objects. Say you have a core fill that is the insulation fill. That might be in one wall for 2x4 construction, and another wall for 2x6 construction. You need 2 different property objects to handle this.

To divide a list by stories... I have found in most cases to define limited list, and define as many as you need. I typically have one for foundation, framing, "main", electrical, plumbing, mech, windows/doors, and one combining everything. I export these individual list to a spreadsheet to form a take off. Trying to make one list do too much leads to screaming.

I'll attach a screen shot for reference, maybe it will provide a few examples.

The whole thing is a big mess, in my opinion. GS really needs to rework the whole system. It is entirely too difficult to manage in an intuitive way. We're not code handlers, but architects (etc). Maybe in AC14, but I've been saying that since AC4.5, and it has changed very little since then.


PS>>> I can't get the image to upload (and it is under 100kb jpg???

image try

ok.. I had made 4 of these into one, and it much be too tall

#3

last but not least