Long Shot

[Anonymous]

Was wondering why my identical windows were not appearing as a single entry and then it hit me.
Since the zone reading is inconsistent and the zone number is part of the window number - I've entered the zone number manually into old user parameter number 5. This of course makes the windows non-identical.

So the question is - Is there a way of omitting a field from the 'identical' comparison?

[Karl Ottenstein]

Only by not showing (scheduling) the field(s) that make them different. Items in a schedule are only considered identical (for grouping) if all scheduled values are identical.

[Anonymous]

...other than the object ID!

It seriously limits the scheduling capacity.

I'm having to manually add a list of 'idenitcal' window numbers to one of the set and weed out the others from the schedule (via using the IFC type classification in the criteria - good thing I don't need to use it right now).

Not super user friendly.

Also noticed that even if the windows are different in elevation (say one has an awning on the left of a fixed panel and the other is the mirror image - so the 3d views are different) so long as the other displayed parameters match, the schedule will treat it as 'identical'.

I'd call that dangerous.

[Barry Kelly]

Angry wrote:
Also noticed that even if the windows are different in elevation (say one has an awning on the left of a fixed panel and the other is the mirror image - so the 3d views are different) so long as the other displayed parameters match, the schedule will treat it as 'identical'.

I'd call that dangerous.

That's when you need to add in a field for the window handing - I think GS call it "Orientation".
Then because the fields show different information they will list separately.
Barry.