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!

Add a new idea Subscribe
Status Future consideration
Created by Brett Wyman
Created on Dec 16, 2025

RELATED IDEAS

Preserve Analysis Results for Non-Structural Command File Changes

Description:
Currently, STAAD deletes all analysis results whenever the command file is modified, even for changes that do not affect the structural analysis—such as adding comments, defining groups, or creating envelopes. This forces users to rerun the entire model unnecessarily, increasing time and computational effort.

Suggestion:
Optimize STAAD so that only modifications impacting analysis or design trigger recalculation. Non-structural edits (e.g., comments, group & envelope definitions) should not invalidate existing results. This would improve workflow efficiency without compromising accuracy.

  • Admin
    Carlos Aguera
    Dec 22, 2025

    Thank you for logging this idea. This idea certainly has merit as it is not uncommon for models to contain data, which when modified does not impact every part of the solution. This is most often associated with design results in which changing design parameters has no impact on say the analysis results. So the action to take away from this is decoupling the design solutions from the analysis. This will allow for more rapid prototyping without unduly introducing large delays whilst the analysis is repeated despite not being impacted by a change in the design. The only challenge will need further investigation is how does this correlate with the fact that the output file is a single representation of the actions defined by the data in the input file. However, the input file has changed. What happens to the output file as it will no longer be a true reflection of the current data? However, this should not be insurmountable, but certainly needs thinking about in detail.

    1 reply