<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SET THE NUMBER OF SECTIONS FORCE FOR MEMBERS CALCULATED DURING THE AANLYSIS PROCESS</title><link>https://communities.bentley.com/products/ram-staad/f/ram-staad-forum/146613/set-the-number-of-sections-force-for-members-calculated-during-the-aanlysis-process</link><description>Hi all, 
 For a beam, when I check the internal force by report =&amp;gt; sections forces... I get an table with the interal force at 13 sections, but in Beam force detail we can see for 5 section. 
 Can anybody tell me where we can set these sumber (13/5) before</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: SET THE NUMBER OF SECTIONS FORCE FOR MEMBERS CALCULATED DURING THE AANLYSIS PROCESS</title><link>https://communities.bentley.com/thread/722429?ContentTypeID=1</link><pubDate>Wed, 20 Jul 2022 15:44:38 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:6cc7b47a-5dc2-4696-baae-8a7adb35c0ca</guid><dc:creator>Philip Heid</dc:creator><description>&lt;p&gt;I have the same question. I have nearly 1million lines of stress results and staad will not export the beam stress report due to size. I could live with three data points per beam rather than 13 if it meant I could export this report to excel for post processing&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SET THE NUMBER OF SECTIONS FORCE FOR MEMBERS CALCULATED DURING THE AANLYSIS PROCESS</title><link>https://communities.bentley.com/thread/486597?ContentTypeID=1</link><pubDate>Thu, 18 Oct 2018 16:00:26 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e483f6ae-42d1-4c2a-baa7-7a268fee65c4</guid><dc:creator>just humm</dc:creator><description>&lt;p&gt;This method doesn&amp;#39;t seem to be working for me. After making the settings changes that you&amp;#39;ve suggested (setting the increments to 5), the report table that I&amp;#39;m selecting (Report Menu --&amp;gt; Beam Stresses...) is still showing the stresses at 13 increments for each beam.&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5932/1732.Capture1.JPG" /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5932/3187.Capture2.JPG" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5932/0871.Capture3.JPG" /&gt;&lt;/p&gt;
&lt;p&gt;I am using STAAD.Pro V8i (SELECTseries 6), Version 20.07.11.82.&lt;/p&gt;
&lt;p&gt;Is there another setting that I need to change in order to reduce the number of sections shown in a report table?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SET THE NUMBER OF SECTIONS FORCE FOR MEMBERS CALCULATED DURING THE AANLYSIS PROCESS</title><link>https://communities.bentley.com/thread/445678?ContentTypeID=1</link><pubDate>Mon, 05 Feb 2018 13:02:52 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:14279dee-aee2-4609-b328-dada9d9859ea</guid><dc:creator>Modestas</dc:creator><description>&lt;p&gt;To change the detail increments for the reports, go to the Report Setup -&amp;gt; Items tab and change the number of Report Details Inrcements.&lt;/p&gt;
&lt;p&gt;To change the amount of sections reported in the post processing tables, go to Results -&amp;gt; Select Load Case -&amp;gt; Range tab and change the number of the Increments.&lt;/p&gt;
&lt;p&gt;Please note that this will not have any impact on the analysis speed as it is just a post processor setting.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>