KSC2 CDE MP Test

KSC2 CDE MP Test

This is just a test session. If multiplayer fails, feel free to play it in single player.

This session uses the CDE car Tagging feature. In your train context menu (CRTL+Right click) you will find a new CDE command set. Also the cars will have an additional window showing their next destination(s).

The aim of this sesson is to deliver the correct cars to their customers. Customers are Ricochet Freight and Ontrack printing. Or virtual off-route destinations that are reached via portals.
The car tags indicate the destinations the car is meant for. If you deliver the car, be sure to update the tag by issuing the 'Update' command in CRTL+Right Click context menu.
This activates the next destination for the car.

Please note:
- Locomotives can have tags too but they are usually to indicate their purpose or a running train number that put them into a complex scheme.
At least at session start.
When you update a string of cars with a tagged loco attached, the tag of the loco gets updated too. In this case - usually erased.
Depending on the complexity of the session, they might be just decoration (like here) or assign locos to certain tasks (yard work, road switcher, local switcher, mainline haul) . The session might make up some naming scheme then.

- In game you can edit tags, add or remove them. While this is optionally possible, the tags are meant to be 'updated' using the command. This basically activates the next planned destination of the car. Please note that there is no check if the car is really at the destination if you issue that command.

- Industry setup is only rudimentary. This session is just a test.

Special locations:

- The yard has a reserved area where empty cars are stored. This is called 'Empty Car Storage' - 'ECS' for short. A yard can have more than one, here it is labelled 'ECS1' and represented by a track mark. Empty cars can be 'delivered' there. The cars planned to go there will have an 'ECS1' tag
- Cars might leave the route via portals. Here we don't have one, just imagine the session ends before the engines for the outbound trains arrives and pick them up.
- Cars might arrive via portals too. Sessions on other routes might make use of portal traffic.
- Cars might start up without tag information. This is either intended - then you don't need to do anything with the car or you are free to use them at your own will. Refer to session instructions.

KSC2 CDE MP Test
• 002.jpg 237.40KB
• 003.jpg 244.93KB
• config.txt 12.14KB
• profile.amd 6.21KB
• profile.dat 58.28KB
• profile.lyr 64 bytes
• profile.not 2.23KB
• profile_-1_0.trk 28 bytes
• profile_-1_0.vtx 28 bytes
• profile_-1_1.obs 28 bytes
• profile_-1_1.trk 28 bytes
• profile_-1_1.vtx 28 bytes
• profile_-1_2.trk 28 bytes
• profile_0_-1.trk 28 bytes
• profile_0_-1.vtx 38 bytes
• profile_0_0.trk 28 bytes
• profile_0_0.vtx 58 bytes
• profile_0_1.trk 28 bytes
• profile_0_1.vtx 108 bytes
• profile_0_2.trk 28 bytes
• profile_0_2.vtx 68 bytes
• profile_0_3.trk 28 bytes
• profile_0_3.vtx 38 bytes
• profile_1_-1.trk 28 bytes
• profile_1_-1.vtx 38 bytes
• profile_1_0.trk 28 bytes
• profile_1_0.vtx 108 bytes
• profile_1_1.obs 9.46KB
• profile_1_1.trk 28 bytes
• profile_1_1.vtx 88 bytes
• profile_1_2.obs 28.86KB
• profile_1_2.trk 28 bytes
• profile_1_2.vtx 408 bytes
• profile_1_3.trk 28 bytes
• profile_1_3.vtx 58 bytes
• profile_1_4.trk 28 bytes
• profile_1_4.vtx 48 bytes
• profile_2_-1.trk 28 bytes
• profile_2_-1.vtx 28 bytes
• profile_2_-2.vtx 28 bytes
• profile_2_0.trk 28 bytes
• profile_2_0.vtx 98 bytes
• profile_2_1.obs 328 bytes
• profile_2_1.trk 28 bytes
• profile_2_1.vtx 38 bytes
• profile_2_2.obs 10.04KB
• profile_2_2.trk 28 bytes
• profile_2_2.vtx 88 bytes
• profile_2_3.trk 28 bytes
• profile_2_3.vtx 48 bytes
• profile_2_4.trk 28 bytes
• profile_2_4.vtx 38 bytes
• profile_3_-1.trk 28 bytes
• profile_3_-1.vtx 28 bytes
• profile_3_-2.trk 28 bytes
• profile_3_-2.vtx 28 bytes
• profile_3_0.trk 28 bytes
• profile_3_0.vtx 58 bytes
• profile_3_1.obs 418 bytes
• profile_3_1.trk 28 bytes
• profile_3_1.vtx 28 bytes
• profile_3_2.trk 28 bytes
• profile_3_2.vtx 38 bytes
• profile_4_-1.trk 28 bytes
• profile_4_-1.vtx 28 bytes
• profile_4_0.trk 28 bytes
• profile_4_0.vtx 28 bytes
• profile_4_1.trk 28 bytes
• profile_4_1.vtx 38 bytes
• profile_4_2.trk 28 bytes
• profile_4_2.vtx 38 bytes
• profile_5_-1.trk 28 bytes
• profile_5_-1.vtx 28 bytes
• profile_5_-2.trk 28 bytes
• profile_5_-2.vtx 28 bytes
• profile_5_0.trk 28 bytes
• profile_5_0.vtx 478 bytes
• profile_5_1.obs 15.12KB
• profile_5_1.trk 28 bytes
• profile_5_1.vtx 38 bytes
• profile_5_2.obs 450 bytes
• profile_5_2.trk 28 bytes
• profile_5_2.vtx 38 bytes
• profile_6_-1.trk 28 bytes
• profile_6_-1.vtx 28 bytes
• profile_6_-2.trk 28 bytes
• profile_6_-2.vtx 28 bytes
• profile_6_0.trk 28 bytes
• profile_6_0.vtx 28 bytes
• profile_6_2.trk 28 bytes
• profile_6_2.vtx 28 bytes
• profile_index.obs 104 bytes
• profile_index.rlr 16 bytes
• profile_index.trk 206 bytes
• profile_index.vtx 206 bytes
• thumbnail.jpg 774.87KB
• thumbnail_alt.jpg 51.25KB