I installed the latest version of STAAD.Pro (22.02.00.26) earlier this week and have already experienced at least 4 crashes. Two gave me the opportunity to send a report. One just shut STAAD down with no warning. The other one shut down the Analysis Output with no warning but STAAD still thought it was open because I couldn't reopen it. This is very frustrating. Is anyone else experiencing this?
Oh, and no, I wasn't doing anything unusual. And yes, I'm using my local hard drive for the input file.
Can you please try deleting the default user settings as explained in the first wiki below. If you have made any customization to the interface, you may follow the instructions in the second wiki below to save those XML files first and then delete the user settings
https://communities.bentley.com/products/ram-staad/w/structural_analysis_and_design__wiki/43121/staad-pro-connect-edition-has-stopped-working
https://communities.bentley.com/products/ram-staad/w/structural_analysis_and_design__wiki/41423/how-to-retain-customizations-in-staad-pro-connect-edition
Thanks Sye. That sounds familiar. Maybe I've had that problem before. Anyway, I've had two crashes since following the instructions above but other weirdness was going on so maybe it's unrelated. Time will tell.
Hmm . . . not looking good. Crashed this afternoon with no warning message/opportunity to send report. All I was doing was zooming by rolling the center mouse button.
I've had 5 more crashes since Nov. 11. Are any other of you folks who have upgraded to the latest version experiencing this? The only think I can think of that has changed about my computer is that I've started using OneDrive to keep my local files backed up, but I started using this before I updated STAAD and didn't notice all of these crashes.
Yes, I also experience crashes with version 22.02.00.26. Deleting settings as Sye suggested did seem to lessen the frequency. But neither that step nor a full reinstallation of all Bentley software has stopped them from happening. I haven't been able to link them with any particular action. They do seem to occur more frequently with bigger models. We've advised people who haven't yet upgraded to hold off until the next version in hopes that they can get this fixed.