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 Future consideration
Created by Michael Wood
Created on Mar 2, 2023

Make Material Definition properties apply for steel design

Currently, according to Bentley Support, the Material Definition properties are only used in the Connection Design module and are not used for steel design & code checking. The SGR, FYLD, FU parameters must be used instead to define the material properties. The Material Definition properties should be used for all subsequent steps. It is not optimal to define material properties more than one time.

  • Admin
    Carlos Aguera
    Reply
    |
    Apr 4, 2023

    Thank you. For this idea, we will take this to be 'Extend the capability of using the material definition as the steel grade for AISC 360-10 design, mirroring the behaviour provided for AISC 360-16.'

  • Admin
    Carlos Aguera
    Reply
    |
    Mar 22, 2023

    Thank you for posting this idea. This functionality is already used in the AISC 360-16 design code. The parameters provided will thus be overrides for any definition provided in the material definition. Were you looking for this to be added to any other specific code? It will be used as the principal for any new design codes added to STAAD.Pro, but adding it retrospectively to other codes would require significant refactoring.

    3 replies