Container
| Line 2: | Line 2: | ||
== Container == | == Container == | ||
There are ten container types used in the aCTS: 10ftsc, 10fthc, 20ftsc, 20fthc, 40ftsc, 40fthc, 45ftsc, 45fthc and 53ftsc, 53fthc. An aCTS usable container is predefined with its origin at the geometrical middle of the bottom face. So the container assets of other asset builders need possibly a variant with config setted position and rotation. Additionally the scale may be needed to set for fitting the technical dimensions. | There are ten container types used in the aCTS: 10ftsc, 10fthc, 20ftsc, 20fthc, 40ftsc, 40fthc, 45ftsc, 45fthc and 53ftsc, 53fthc. An aCTS usable container is predefined with its origin at the geometrical middle of the bottom face. So the container assets of other asset builders need possibly a variant with config setted position and rotation. Additionally the scale may be needed to set for fitting the technical dimensions. | ||
| − | All containers that don't fit the technical dimensions and the logical origin position and rotation have a config extensions sub soup with the name "acts.delta-251489" and tags for correcting the assets values to the aCTS fitting ones (accuracy 0. | + | All containers that don't fit the technical dimensions and the logical origin position and rotation have a config extensions sub soup with the name "acts.delta-251489" and tags for correcting the assets values to the aCTS fitting ones (accuracy 0.1 mm and 0.1 °), looking like follows: |
<CODE> | <CODE> | ||
acts.delta-251489 { | acts.delta-251489 { | ||
Revision as of 20:02, 23 April 2024
Container
There are ten container types used in the aCTS: 10ftsc, 10fthc, 20ftsc, 20fthc, 40ftsc, 40fthc, 45ftsc, 45fthc and 53ftsc, 53fthc. An aCTS usable container is predefined with its origin at the geometrical middle of the bottom face. So the container assets of other asset builders need possibly a variant with config setted position and rotation. Additionally the scale may be needed to set for fitting the technical dimensions.
All containers that don't fit the technical dimensions and the logical origin position and rotation have a config extensions sub soup with the name "acts.delta-251489" and tags for correcting the assets values to the aCTS fitting ones (accuracy 0.1 mm and 0.1 °), looking like follows:
acts.delta-251489 {
px.delta 0.0
py.delta 0.0
pz.delta 0.0
rx.delta 0.0
ry.delta 0.0
rz.delta 0.0
}
Unfortunately the scale of the mesh may not be corrected by some factor to fit the aCTS dimensions. So for containers with other dimensions one may see a small gap between stacked containers or they run optical into each other. A container knows its container stack and its position in it. A container is able to report its parameter soups, including a yet not used virtual list of content to transport within it.
