Skip to Main Content
STAAD.Pro Ideas Portal

Welcome to the STAAD.Pro Ideas portal. The purpose of this site is to post ideas for enhancements and new features. We value your feedback and our team regularly reviews your suggestions for consideration in future releases.

You have 3 options for providing feedback:

  1. Vote for an existing Idea. The popularity of an Idea helps us understand its importance to our users.

  2. Comment on an existing Idea. We want to hear your unique point of view.

  3. Add a new Idea. If no existing Idea describes what you would like, add a new one!

When you Vote, Comment, or Add an idea you will also be subscribed to that Idea and will receive status updates. Please note that we may merge or rename Ideas for clarity. Thank you for your support and feedback, it is always appreciated!

Status Needs review
Created by Michael Wood
Created on Apr 1, 2024

Improve beam/node selection for reporting loads

Add some kind of functionality to categorize "connection types" to simplify reporting of loads. While there is functionality to group members and to group nodes, there is no way to overlap them. When I want the connection loads for certain members, I use a member group but the loads are given for both ends of the beam. When I only want one end of the beam, I have to use Excel to further filter the list down to the specific beam+node that I am interested in. It would be nice if you could group "connections" or beam+nodes in STAAD so you don't have to do any further filtering of the results.

  • Admin
    Carlos Aguera
    Reply
    |
    Apr 2, 2024

    Thank you for posting this idea. Do you really mean loads, i.e. the applied loading or do you mean forces resulting from the analysis? I suspect the latter. What might be helpful in describing this idea, is some form of mock up. Would the request be the forces for a given member and from that member pick start/end and get a table of the end forces for all load cases/combinations? or are you looking for the function to also filter the load cases too? Or are you thinking that the request would pick a list of members and from that get the results from the start or end only? All the above can be created relatively simply as an OpenSTAAD macro.

    5 replies