Container

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
  
 
== 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.  
+
===Container types===
 +
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.
 +
 
 +
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.
 +
 +
 
 +
===Container from other asset builder===
 +
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:
 
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>
Line 14: Line 21:
 
</CODE>
 
</CODE>
 
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.
 
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.
+
 
 +
===config.txt===
 +
<CODE>
 +
  XXX
 +
</CODE>
 +
 
 +
===acts_container.gs===
 +
<CODE>
 +
  XXX
 +
  YYY
 +
  ZZZ
 +
</CODE>
 +
 
 +
===acts_container_script.gs===
 +
<CODE>
 +
  XXX
 +
  YYY
 +
  ZZZ
 +
</CODE>
 +
 
 +
===acts_container_globals.gs===
 +
<CODE>
 +
  XXX
 +
  YYY
 +
  ZZZ
 +
</CODE>
 +
 
  
 
[[Category:ACTS]]
 
[[Category:ACTS]]

Revision as of 18:47, 24 April 2024

Contents

Container

Container types

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.

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.


Container from other asset builder

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.

config.txt

 XXX

acts_container.gs

 XXX
 YYY
 ZZZ

acts_container_script.gs

 XXX
 YYY
 ZZZ

acts_container_globals.gs

 XXX
 YYY
 ZZZ

Personal tools