RAM Structural System Ideas

Welcome to the RAM Structural System 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 Guest
Created on Aug 30, 2024

RELATED IDEAS

Notify User When Anything is Cleared by RAM

When concrete section cuts are deleted by the program due to geometry changes etc, a popup window notifies the user that this has been done. However, in at least one situation I recently discovered, this type of notification isn't present. And that situation was when I updated my Mean Roof Height in my Code Wind Load Cases in Frame. Apparently doing this clears all of your Merged Load Cases, and I was completely unaware of this until a coworker noticed it. I'm not sure if updating the load cases in other ways also clears the Merged Load Case info, but I'm asking that the user be notified WHENEVER the program automatically clears information, whatever the reason.

  • Attach files
  • Admin
    Seth Guthrie
    Reply
    |     Sep 23, 2024

    We recently modified the logic deleting merged load cases when the original load case was changed. We did this because there were some changes that could invalidate the merged load case leading to load case corruption. A warning, with a chance to opt-out or cancel does seem like a good idea, Thanks. (Product Backlog Item 1525050)