1. Update Item
1) The Activation Method of the component has changed
2) Component activation speed increased
3) The way data is processed has changed
4) A new Component has been added
5) UI improvement
6) Bug Fix
2. Description
1) The Activation Method of the component has changed
It was difficult to control the data because the components ran immediately whenever the data changed.
[Modification]
A Run button running the API is added to prevent it from running automatically.
2) Component activation speed increased
By improving the fact that it took a long time to run and operate APIs individually, such as node generation components, the same API was changed to proceed simultaneously.
[Modification]
For components that run APIs separately, such as node-generated components, it took a long time to operate.
3) The way data is processed has changed
There was a hassle of having to run a component that was updated every time.
[Modification]
A component that collects the same type of API and a component that runs the API at once have been added.
This prevents components from being re-executed each time a variable was changed after the modeling was created, or API execution was interrupted by differences in API processing speed for each component.
[Caution]
As the way data is processed changes, the Node, Beam, Plate, and Solid components, which are modeling generation components, have changed,
The previously searched beam modeling information at once has been changed so that node information and element information can be searched.
This is so that when you finally run the API on the Builder component, you can control the Node and Element information of that element separately.
It has also been changed to allow each Node and Element to be assigned a number that the user wants.
Because of this, the following changes occur after the change.
1) You must reconnect an existing connected element.
Existing components are ①MATL②SECT③LINE for Input and ⓐBeam for Output.
However, the changed component is ①Elemet No. ②Node No. ③MATL ④SECT ⑤LINE for Input, and new data is added to the front of the existing data in the order of ⓐ Node ⓑBeam for Output.
This is to encourage users to use the API later to naturally create a Node in the Builder component and then create a Beam.
Therefore, for existing files, you must try to reconnect the components that create the elements.
2) You must delete internally stored model information.
Existing components immediately ran the API when connected and immediately stored the DB in the component.
However, when you copy and use components, the DB is duplicated inside, and after the update, the API needs to be pressed to run, so the DB continues to accumulate internally, and even after copying the components, the DB is automatically updated.
(The component UI has some changes.)
Through this, if the existing DB information is used as it is, there is a possibility of conflict with the existing DB if there is a change in modeling at least once.
Therefore, you should be able to delete the entire existing internal DB.
Here's how.
a. Right-click an icon
b. Clear Temp DB Civil NX Click
c. New Input Connections
d. New Output Connections
4) New Created Component
- Tools
- Merge Data
- Model Builder
- Structure(New)
- Span Information
- Span Information Item
- Properties
- Change Property
- User Material
- Effective Width Scale Factor
- Static Loads
- Using Load Combinations
- Using Load Combinations
- Prestress
- Approximate Tendon Losses
- Approximate Tendon Losses
- Moving Load
- Vehicles Classes
- Plate Element for Influ.Surface
- Dynamic Load Allownace
5) UI Improvement
There was only one way to select the data, the Dropdown method, which made it less usable.
[Modification]
For data that can be divided into execution or non-execution, such as on/off, a radio button method has been added.
6) Bug Fix
A. User Define Es Not Working
The User Define Es feature was found to be inoperative and corrected.
[Modification]
The User Define Es function can only be implemented in JTG 3362-18(S) of Steel Material and has been changed to be used in that standard and modified to work.
B. Modify a Section DB that was not created
There was a problem that some of the Section DBs were not created, which did not match the DB stored in the grashopper with the latest version of Civil NX.
[Modification]
Modified the DB to match the latest Civil NX.
C. Get Elem Node Component Not Working
When the Get ELEM Node component was connected to the Beam, Plate, and Solid components, it was found to be inoperative.
[Modification]
It has been changed so that Node information can be extracted normally when connected to Beam, Plate, and Solid components.