ContainerBridgeCrane: Difference between revisions

From TrainzOnline
Jump to navigationJump to search
Ek.skirl (talk | contribs)
Created page with " ==Container Bridge Crane== A bridge crane consists of several running parts. This parts are some kind of parented. The hirarchy of this parts look like this: '''TBD: Insert..."
 
Ek.skirl (talk | contribs)
No edit summary
Line 19: Line 19:
</CODE>
</CODE>


==Asset files==
==Asset files pre version 0.1==
The files compile errorless and the messaging runs well. No more functionality implemented and tested in this pre version.
 
===config.txt===
===config.txt===
<CODE>
<CODE>

Revision as of 13:34, 24 April 2024

Container Bridge Crane

A bridge crane consists of several running parts. This parts are some kind of parented. The hirarchy of this parts look like this:

TBD: Insert hirarchy ... from script comments

Reachable area

The special reacharea parameters for the bridge crane prototype looking like follows:

 acts.reacharea-251489 {
   reacharea.dimension.x       30000
   reacharea.dimension.y      100000
   reacharea.dimension.z       26000
   reacharea.origin_inset.x    15000
   reacharea.origin_inset.y    50000
   reacharea.origin_inset.z     5000
   max_container_count             7
 }

Asset files pre version 0.1

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

config.txt

 XXX

acts_bridgecrane.gs

 XXX
 YYY
 ZZZ

acts_bridgecrane_script.gs

 XXX
 YYY
 ZZZ

File is located in dispatcher library.

acts_bridgecrane_reachable.gs

 XXX
 YYY
 ZZZ

File is located in dispatcher library.

acts_bridgecrain_globals.gs

 XXX
 YYY
 ZZZ

File is located in dispatcher library.