-
Notifications
You must be signed in to change notification settings - Fork 4
Known Issues
For general issues identified and planned to be fixed see the issue page.
There are some known limitations with the MidasCivil object model that may result in information being lost when pushing to the software. The known limitations are outlined below.
It is important that all unique section properties, materials, constraints and releases have a unique name, to be able to push all objects to MidasCivil. Objects with the same name will be treated as the same object.
It is possible in MidasCivil to apply both a spring and a support to the same node, when this is read by the MidasCivil_Toolkit the spring will overwrite the support. MidasCivil does offer fixities within spring so this is considered bad modelling practice.
When pushing loadcases, you must push to an empty file (i.e. with no existing loadcases), owing to the fact that Midas gives its loadcases by name only and not by number.