What is MLOG?
MLOG stands for multi-log where multiple type logs are used to simulate the basic part of a logging industry system. There are 2 styles of 3 sizes for a total of 6 different log products in the MLOG system. The first style are the single logs and the second style are the logstacks which are multiple logs fitted together in a bundle. The log sizes are 16, 32 and 40 foot lengths. The single logs are generally about 4 foot in diameter which is similar to the default Auran logs that come with the game. I have developed skeleton cars which will carry all of these logs in one form or another in 3 foot gauge and standard gauge.
The MLOG CDK is provided so that other creators can make cars and objects that are compatable with the MLOG system logs. It is nothing too difficult, all that must be done is to maintain the load attachment spacing and modify the config.txt to utilize the log product kuids. It is assumed that the user has a good understanding of 3D modeling technique and the Auran Content Creator's Guide.
In the CDK you will find a simple gmax model as shown. It contains the load attachment sample array that must be used in your own model for MLOG attachment. The chocks are the blocks that keep the logs in place on "log bunks" common to skeleton cars and flat cars. The sizing box shows how much space a typical 32 foot log load would take up. The MLOGs are randomized in size so they are not "cookie cutter" products. At least a foot of variance must be allowed when sizing for other type logs. So for 16's use an 18 foot reference length. The width of all log sets are standard. You can use the sizing box for reference. The sample log is typical of a 32 foot log single and provided for reference only.
This image shows a skeleton car with the load attachment array placed at 0 on the Y axis. They are named a.load(n) where (n) starts with 0 and continues with 01, 02 and 03. The attachment a.load0 is placed at Y axis and X axis 0 or "center".
The attachment a.load0 is for objects that are centered on the car. The MLOG log stacks are placed on this attachment.
The rest of the attachments are spaced for single logs to form a triple stack.
When placing attachment arrays, ensure that the Z lever arm of the attachments are flush with the top of the log bunk or flat car deck as in this front on view example.
For double loads of the 16 foot logs, two additional sets of attachments will need to be made. In the example, the 32 foot and 40 foot logs will be placed on the center of the skeleton car using the normal centered attachments. The upper and lower sets of attachments are for the 16 foot logs and Auran logs. The spacing for the 16 foot log attachments are set at 20 feet to provide adequate spacing for the randomized load length sizes.
This example shows another view with the load attachment naming conventions. Pay attention to this as you will need to refer to these names later in the config file.
This is what the above double 16 foot load example looks like in Trainz when loaded. If using the other size MLOGs they would be placed in the center.
Once the car is ready to export, the config file needs to be updated. The example shows how the load attachments are used.
The first "load0" queue is for a log stack product. Notice that the "conflicts-with-queues" is set to indicate that this item is not compatable with the load1 product.
The second "load1" queue is for single logs. This is used in the same manner as the default Auran logs where three objects are attached to individual attachment points.
The "allowed-products" is the kuid of the desired log type for the load.
Continue adding "load(n)" queues as required. Be mindful of the "conflicts-with-queues" tags.
The final touch is to add the "MLOG" icon and industry icon to the car's config. This will allow the small icons to show up in the lower portion of the viewer window in the Surveyor mode. You can have up to four icons for an object. In the example I have used the Trainzproroutes Auto-Numbering System that comes with an icon, the default industry compatable icon and my own "MLOG" icon.
For my own standard, I have also indicated what size log the car is compatable with in the upper right corner. This however is part of the 512_art file and not an icon.
The config needs to be modified to accomodate the icons. In the example "icon0" is the Auran "IND" icon and the "icon1" is the "MLOG" icon as seen above.
Test and enjoy. You can find further examples by studying my skeleton car configs and file structures for the MLOG system.