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.
Also I have tried making the spacing from the edge greater that the usual 3 ft which I set by default, which would usually fix it if it is this issue, and it doesn't seem to help at all.
There is a newer version of OBM available. If that does not resolve your issue, I would suggest filing a support ticket for someone to take a look at your file.
Thanks Steve. For some reason the Connection Client wasn't notifying me of this available update.
Still, this hasn't resolved the issue. I've tried recreating the structure several times, and creating the beam layouts one span at a time. In the latter case, by then pulling the edge distance to 3.5 ft it did allow the left beam to be defined for the first span I created, but the second and third spans still won't create.
I don't have the greatest understanding of what is meant by Chord, or whether this is somehow playing a part, though I don't believe so as I have tried switching that on and off (I did notice a very slight shift in the beam layout lines when doing this, though I still haven't figured exactly the meaning and can't find a clear definition anywhere.)
I'm going to submit a support ticket now and see if I can get anywhere that way.
Thanks for your help though guys, it's greatly appreciated.
Just an update on this, I did update OBM, but the issue was still occurring. I submitted the issue to Bentley, and they found it to be some peculiar bug, but I don't see any notification from them since, so I don't think I have received any update from them with a solution.
Ok, I eventually found the SR on the system. It seems my company moved me from one account to another and so I no longer had this SR listed on my SR registry.The end result of the SR was simply a message Bug 365571. No other explanation or details of what is being done about it, whether any progress has been made or anything. I appreciate software bugs are unpredictable by nature, but more info on what is being done, if any, from the software developer would be appreciated.