Script filtering and Folded beams

[Masibanda-CE]

I have script filters that look for all the different DSTV codes for use in Drawing processes and Dimension requests. They tend to work rather well with the exception of "Folded beams". Folded beams seem to return "True" for all DSTV code scripting. Does anyone experience this or understand why this would be?

The most recent example is a Dimension request that is filtering for points of a T section, but is picking up the points of a Folded beam.

[Masibanda-CE]

@gabriel.costin 

When using AttachedBeams the points then remove from the plates AND the angles (which indicates the T/8 filter is working in a limited capacity), BUT the FoldedBeams are still being included.

I also tried your "profile angle" suggestion and received points of Angles AND FoldedBeams.

I'd say that there is a problem in that FoldedBeams are not correctly being processed and will return TRUE when checking for any DSTV type.

[gabriel.costin]

I see your point. I'm going to think more if we can get rid off the folded beams somehow ....I admit that I'm less optimist now.

[Sebastian_Eiche]

I used the proftype "18" for folded beams in the past for a script, but this was used in the process manager, and there the other scripts are working.

I think this is because the script is running before the modelobject "for example" beam is used. In the detail style model object, the filter is running after selecting the model object "beam".

in my testing I used an overview detail style to show a specific object. In this case I have only one line just for the modelobject "T", but I could use a script like I want, the folded beam is always set the filter to true:

My model has different objects, like C, T , W shapes, folded beams and plates. I could filter all object very clear to show or not to show with script and object properties, but not the folded beam.

My last idea was to use the "IsUnwind" property, but this is not working in the modeloject filter too. 

[gabriel.costin]

@Masibanda-CE

I ran more tests on my side. The bottom line is that the Folded Beam objects are not even reaching out to filtering. Thus, they aren't responsive to filtering conditions. It's not easy to say why this is happening without having in depth investigations.

You may focus on finding a solution in a different way (e.g. different model roles).

[Masibanda-CE]

  Thanks for your help on this Gabriel. Using roles is no longer an option as it’s the ONLY feature that seems to work consistently and because of that we already have added hundreds. It’s become unmanageable.

i suppose the only way to fix this defect, yes defect, is to add it to the development wish list and wait for a decade, what do you think @Gernot.Jeromin ?

[Sebastian_Eiche]

I have another idea.is it maybe an option not use the center of the T as dim point? If it is an option to use the start and / or the end point, you could maybe think about the following:

The presentation of the T shape could be set up as shown with sytemline and the folded beam without system line. So you could add in the dimension the Systemline of attachedbeam (filter for T). The result is, that Advance Steel try to use the Systemline for dimension but should not recognize the folded beam, because the Systemline of this object is not shown.

Not the result you want, but maybe as option

[Emanuel.Nestor · Accepted solution]

Hi @Masibanda-CE, and Hi All,

Thank you for reporting this behavior, and thank you for all the investigations you have done so far.

Here are some findings from my side:

• It seems that the function "Obj.getProfType.getDSTVValues.DSTVType" ends (exits) the script with "True" when interrogate the folded beam object.
• It seems that it does not even go to the next line after it (I put a check point right after it, and it does not reach it). 
• Even more, it seems that the same behavior occurs in case of Polybeam.
• Further, it seems that the function "Obj.IsKindOf(kBeamUnfoldedClass)" does not return True in case of folded beam. Similar, the function "Obj.IsKindOf(kBeamPolyClass)" returns False in case of polybeams.
• So, basically you cannot use this function to filter out folded beams in DSM.
• It looks like the function Obj.IsKindOf() works only on the "major class" level - for "kBeamClass", "kPlateClass", at least when use it in DSM. I know that it works for sub-classes in case of NC scripts and inside joints code.

I am documenting these findings and send them to the development team for additional investigations.

Thank you for your patience in this.

Best regards,
Emy