ContainerStack

Revision as of 23:32, 24 April 2024

Container stack objects

Description

A stack may be reachable by more than one crane. It knows the asset specified maximum count of stackable containers and the stackable container types. Additionally it knows the next stackable container types and at which attachment points.

The maximum count of stackable containers has a special meaning for stack kinds that may stack multiple container types. Here the sense is the count of container layers.

There are different stack types: 10ftsc, 10fthc, 10ftschc, 20ftsc, 20fthc, 20ftschc, 40ftsc, 40fthc, 40ftschc, 45ftsc, 45fthc, 45ftschc,, 53ftsc, 53fthc and 53ftschc. These stacks have all a defined length for stackable containers.

Some more complex mixed stacks may be later implemented, such as stacks with mixed containers in multiple layer lines.

A stack is able to report its parameter soups including a list of the current stacked containers, the possibly next stackable container types as well as if it is full stacked.

TBD: The maximal count of stackable containers. Depends on maximum stackable containers from all reachable cranes and the z height of the stack in relation to the z height of the crane.

TBD: Container cars were considered as temporary stacks. The locations and rotations have to be calculated and the attachment points for container products has to be investigated and some were listed per asset within the aCTS global values or in an extensions sub-soup.

Asset files Version 0.1

The files compile errorless and the messaging runs well. No more functionality implemented and tested in this pre version.

config.txt

XY is the KUID part, LL the length and HH or hh the height for the container type.

X   1 for 10ft, 2 for 20ft, 3 for 40ft, 4 for 45ft and 5 for 53ft
Y   1 for standard height, 2 for heigh cube height and without Y for mixed heig cube and standard cube containers.
LL  the fitting length as 10, 20, 40, 45, 53
hh  the fitting height as sc, hc, schc
HH  the fitting height as SC, HC, SCHC

 kuid               <kuid2:215489:11003XY:1>
 username           "aCTS CONTSTACK LLft HH Scenery Utility V0.1"
 kind               "Scenery"
 category-class     "BU"
 description        "aCTS CONTSTACK LLft HH Scenery Utility V0.1"
 
 trainz-build       4.6
 
 surveyor-only      0
 
 script             "acts_contstack.gs"
 class              "acts_contstack"
 
 kuid-table {
   scriptinclude    <kuid2:215489:110000:1>
 }
 
 script-include-table {
   scriptinclude    <kuid2:215489:110000:1>
 }
 
 mesh-table-lod-transition-distances    1000
 mesh-detail-level-count                1
 
 mesh-table
 {
   contstackLLfthh-lod0
   {
     mesh                   "acts_stack_LLfthh.trainzmesh"
     auto-create            1
     lod-level              0
     effects {
       name {
         kind       "name"
         name       "GOID"
         att        "a.name"
         font       "swiss"
         fontsize   0.3
         fontcolor  1.0,1.0,1.0
       }
     }
   }
 }
 
 thumbnails
 {
   0
   {
     image          "acts_contstack_LLfthh_thumb.jpg"
     width          240
     height         180
   }
 }

TBD: (???) For single length stacks there is no need to diferentiate the mesh container name, the mesh file name and the thumb file name in different heights, because there are no attachmentpoints used. (???) 

acts_contstack.gs

 XXX
 YYY
 ZZZ

acts_contstack_script.gs

 XXX
 YYY
 ZZZ

File is located in dispatcher library.

acts_contstack_globals.gs

 XXX
 YYY
 ZZZ

File is located in dispatcher library.