I have looked everywhere and can't find a clear explanation of the mechanics behind when it will and won't apply the beam definitions. Apparently the pattern is acceptable, there were no errors when creating that, but the first 3 or 4 spans, the left most beam refuses to be created. Some of the spans it will let me select a beam definition and list it as such in the Beam Definition window, sometimes it won't even let me select a beam type, it just defaults back to the WF66G beam, which doesn't show anyway.
I would love to know the reason for why these beams won't create - given there is no explanation for it I've been trying all sorts of adjustments with no luck.
If anyone can help explain it for me or point me towards somewhere that might help me figure it out I would be appreciative. Thanks.
Giles, Most likely the beam top flange width is falling outside the width of the bridge deck defined in some specific spans. What version of OBM are you running? This is already fixed in the recent releases.
Thanks for taking the time to respond Sri.
I'm running OBM Connect Edition 2019 Release 3 - version 10.08.00.760, it should be the latest version.
That was my first guess too, but I think there is something else at play here, because the spans that don't show the beams are in the straight section of the bridge, and typically the first areas where that sort of issue occurs will be on a curved section, with the beam cutting across the edge of the deck, and the curved section of the bridge isn't having the problem, but as I said the straight section is.
I find it quite perplexing.