Released as a hot fix delivered to individual user(s) on December 2, 2015; the changes first appear for the general public with version 9.2.
Important Note – These are descriptions to changes implemented in version 9.3.1 and may not reflect current program behaviour.
Starting with version 9.3, when selecting Fixed bottom end conditions in Column view, both Fixed and Pinned would appear to be selected, and the actual end fixity would remain as pinned. The Free option would not become available for the top fixity. The effect was to restrict the fixity options to pinned-pinned. This has been corrected and all fixity choices are again available.
When loads input view was shown in a pop-up window, and the column load face d was selected, both the d and b faces appeared to be selected and the actual load face would remain as b. The effect was to render it impossible to change from the b load face to d.
Note that if you were to show the Load view in a docked window, then return to a pop-up window, the problem was resolved.
For glulam members loaded on the weak (y) axis, the system factor KH and size factor Kzb reported in the FACTORS table of the Additional Data section of the Design Check output were those for glulam member loaded in the x-direction, rather than the constituent sawn lumber members loaded as if they were in x-direction ( y-axis glulam beams are designed as a sawn lumber built up beam, as per O86 7.5.3.) This has been corrected and the sawn lumber factors are now shown.
The bearing reactions shown in the Analysis diagrams for built-up beams made with custom sections, that is widths or depths not from the standard database, included the self-weight of the entire member multiplied by the number of plies, so that it was too large by self-weight x ( n-plies - 1) .
This problem was a display issue only and did not affect bearing design, and has been corrected.
If a point load was added after any UDL, partial UDL or partial area load, the start location of the point load was displayed as millimetres or inches, rather than meters or feet. This has been corrected.