Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Chaining Sims with similar timetables

You are here: Home > Forum > General > General questions, comments, and issues > Chaining Sims with similar timetables

Page 1 of 1

Chaining Sims with similar timetables 14/11/2010 at 21:33 #2010
ajax103
Avatar
1120 posts
Pardon me for asking the obvious but having no experience in this area if I have a 15th April 2010 timetable for both Peterborough and Kings Cross or a August 2006 0445 timetable for Central Scotland and Edinburgh, could both then be chained together to host a session?

I found a post by welshdragon but I want to double check that I fully understand the logic of chaining:

All 3 sims chain fine provided you have timetables that are similar on all 3 sims (same date/start time), both over L(ocal) A(rea) N(etwork) and W(ider)AN. Ensure that the main sim is using 50505, Secondary sim 50506 and third sim 50507 (and so on for more sims)

I really ought to spend more time on the multiplayer sessions I know but it's finding the time.

Log in to reply
Chaining Sims with similar timetables 14/11/2010 at 21:33 #12498
ajax103
Avatar
1120 posts
Pardon me for asking the obvious but having no experience in this area if I have a 15th April 2010 timetable for both Peterborough and Kings Cross or a August 2006 0445 timetable for Central Scotland and Edinburgh, could both then be chained together to host a session?

I found a post by welshdragon but I want to double check that I fully understand the logic of chaining:

All 3 sims chain fine provided you have timetables that are similar on all 3 sims (same date/start time), both over L(ocal) A(rea) N(etwork) and W(ider)AN. Ensure that the main sim is using 50505, Secondary sim 50506 and third sim 50507 (and so on for more sims)

I really ought to spend more time on the multiplayer sessions I know but it's finding the time.

Log in to reply
Chaining Sims with similar timetables 14/11/2010 at 21:59 #12500
Peter Bennet
Avatar
5402 posts
It requires the author to ensure they are compatible. That means ensuring that all the trains in one timetable to be in the other and for the TDs with suffixes to have the same suffix in each sim (vital for ARS sims anyway). Also the train characteristics need to be cross checked- I think some characteristics transfer and others are picked up from the arriving sim's timetable- exact details I'm a bit vague on.

However, the basic point is that in general timetables for the same date will most probably be OK by default but do require some deliberate work by the author to ensure it.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
Chaining Sims with similar timetables 25/11/2010 at 11:32 #12635
ajax103
Avatar
1120 posts
Peter Bennet said:
It requires the author to ensure they are compatible. That means ensuring that all the trains in one timetable to be in the other and for the TDs with suffixes to have the same suffix in each sim (vital for ARS sims anyway). Also the train characteristics need to be cross checked- I think some characteristics transfer and others are picked up from the arriving sim's timetable- exact details I'm a bit vague on.

However, the basic point is that in general timetables for the same date will most probably be OK by default but do require some deliberate work by the author to ensure it.

Peter
Thanks for that, if I'm right as Kings Cross is a Scrolly Sim and Peterborough is a Paged Sim, is it possible for one host to run both sims in a single multiplayer session if the same timetable is used?

I would welcome the chance to host such a session but not sure how to setup such a session.

Log in to reply
Chaining Sims with similar timetables 25/11/2010 at 14:50 #12638
clive
Avatar
2789 posts
It's nothing to do with scrolly v paged. Some very old sims use a different interface for chaining, and so old and new sims either can't be chained or will have problems if they try.

You can host more than one sim on the same machine at the same time, and have them chain together, provided that each was opened using a different port.

Log in to reply