Elvas Tower: How do You verify timetables, you writing? - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

How do You verify timetables, you writing? Lifehacks sharing.

#1 User is offline   Weter 

  • Member, Board of Directors
  • PipPipPipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 6,936
  • Joined: 01-June 20
  • Gender:Not Telling
  • Simulator:ORTS
  • Country:

Posted 17 February 2021 - 06:25 PM

Hello.
I guess, there could be your question, where and how I seen the errors, that I described.
As well, I would both: to advise my way to see, how my timetables work and to learn another tricks, if you'll want to tell about.

So, I create separate train (the name could be "<Station or other location's name>_tester" to see it clearly among other trains in the list;
Choose a train consisting of just single locomotive with simple, low polygonal body shape;
Define for it the test path, looking like path for #static consists: short path along spur or unused siding (towards its dead-end for guarantee, that tester train will not influence any signals and traffic behavior);
Then, define the start time, meaning the time, when I would to see, what is actually happening at location of interest (station)

I can start ORTS with tester choosen, switch to key 8 free camera (2viewports will be created automatically) and move that two (or create some more,if needed) cam FOVs to places, from hear I can see the trains activity clearly.
I use time acceleration (Ctrl-Alt-PgUp) and traffic path reserved+signals visualization(Ctrl-Alt-F11) to see additional info.
And watch timetable at editor and printed at paper, where I can write pencil remarks.

#2 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,424
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 18 February 2021 - 02:07 AM

That's what in other posts has been called an 'observer', and it is indeed the recommended way to test a timetable. Keeping a close eye on the dispatcher hud is also important.
And apart from a good way to test a timetable, it's also a nice way to do some virtual trainspotting.

Regards,
Rob Roeterdink

#3 User is offline   Aldarion 

  • Engineer
  • PipPipPipPipPip
  • Group: ET Owner
  • Posts: 629
  • Joined: 11-February 13
  • Gender:Male
  • Location:Lisbon, Portugal
  • Simulator:Open Rails
  • Country:

Posted 18 February 2021 - 03:24 AM

View Postroeter, on 18 February 2021 - 02:07 AM, said:

(...) it's also a nice way to do some virtual trainspotting.



Amen to that. I do it so much :)
Pampilhosa Station

#4 User is offline   Weter 

  • Member, Board of Directors
  • PipPipPipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 6,936
  • Joined: 01-June 20
  • Gender:Not Telling
  • Simulator:ORTS
  • Country:

Posted 18 February 2021 - 06:36 AM

Glad, that you approve this way of acting.

Quote

Keeping a close eye on the dispatcher hud is also important

This is the next level of debugging, as I think (after all station work verified)
But if that HUD could be scrolled...(I used not MG testing versions)

Quote

... it's also a nice way to do some virtual trainspotting.

agre and vote with both hands.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users