This page lists issues that has been observed in SS6 since it's release
| Defect # | Issue Description | Workaround | Comments |
| - | New STAAD.Pro Editor freezing up/crashing |
| Addressed in 20.07.11.45 |
| 257533 | Section properties for std pipes and extra strong pipes are interchanged for AISC section database |
| Addressed in 20.07.11.45 |
| 257492 | Some newly added wide flange section names in the AISC database had spaces in them which caused the engine to crash |
| Addressed in 20.07.11.45 |
| 264569 | Inclined members are not being split through Geometry > Intersect Selected Members > Intersect | 1. Open the program and go to configuration 2. Set the base unit as English. 3. Open the model and go to the top menu option View > Options > Tolerance 4. Set it to 0.1 inch and click on Apply > Ok 5. Select the members and try to intersect them by going to Geometry > Intersect Selected Members > Intersect. Enter a tolerance of 0.1 inch. | |
| 257167 | The plots of Mz, My, Fy, Fx etc.in the Post Processing Mode > Beams -> Graph page are not displayed for the load cases or load combinations which include wind load generation | The diagrams can be seen in the graphics window by turning on the display icons for these items from the toolbar or one can double click on the individual members and go to the Shear Bending Tab inside the Member Query dialog box to see the diagrams. | Addressed in 20.07.11.45 |
| 257528 | When multiple tapered members are designed in group with CHECK CODE ALL command vs. designed individually, the design results do not match. Noted for multiple codes like AISC /IS 800/ S16. | The only option for now is to design these tapered members individually using CHECK CODE MEMB ... command. | |
| 290989 | For design as per AISC 360-05 or 10 codes, the MNZ and MNY are reported as 0 in the Steel Design tab within Member Query dialog box. This is a reporting error. | Add the design parameter called TRACK and set it to 1 or 2. Rerun the analysis and the MNZ and MNY should now be non-zero in the Member Query dialog box. | |
| 314845 | Design of angles and Tees fail as per the AISC code when seismic provisions of AISC 341 are checked | There is currently no workaround other than commenting out the seismic checks for these sections. | |
323889 | STAAD.Pro is not able to read the external user table files and is generating errors like
*** ERROR : FILE NOT FOUND C:\...\... | Provide the full path name to the file. For example instead of specifying
START USER TABLE TABLE 1 wf1.txt END
specify the input as shown next
START USER TABLE TABLE 1 C:\Model_folder\Model_name\wf1.txt END
| |
| 324630 | STAAD.Pro is crashing during analysis when SELFWEIGHT is applied to a list as shown next LOAD 1 LOADTYPE Dead | Please avoid using the word LIST for now and use only SELFWEIGHT Y -1. | |
| 319346 | There is an error in plotting of the axial force diagram (FX) for TRUSS members. Wedges are formed at the ends instead of a uniform plot. The values are correctly computed in the analysis. | None | |
| 329816 | For tapered member design as per AISC 360-05 code, design results are coming out different when members are designed in groups vs individually | Design the tapered members individually each with its own CHECK CODE command | |
| 327465 | Incorrect section modulus is being used for design of T sections when design is carried out per AISC 360 and section H2-1 is the governing criteria. The stress value reported is highly conservative. | None | |
| 290996 | When the report option Output > Steel Design Detail is used to get detailed design report, the generated report is incomplete for some codes like AISC 360-05 or AISC 360-10 | One can get the detailed design report ( TRACK 2 output ) printed in the analysis output file. A concise version of design report can be obtained by including the option Output > Utilization Ratio Table | |
| 357132 | Some users were not able to access the STAAD News from within the startup page and also not able to connect to the Personal Portal using the Connection Client Widget. | For those users experiencing the problem the following workaround is suggested.
| |
