London Bridge recent update

Is anyone having difficulty with London Bridge since updating with todays updates.
I now try and successfully launch the sim with the 2010 to 2014 era but as soon as I try to scroll the up and down scroll bar the scroll bar bottom turns black and the message sim not responding comes up and will not clear. I have tried this some 5 times now and each time it comes up with the same result.

Geoff

northroad in post 109635 said:

Is anyone having difficulty with London Bridge since updating with todays updates.
I now try and successfully launch the sim with the 2010 to 2014 era but as soon as I try to scroll the up and down scroll bar the scroll bar bottom turns black and the message sim not responding comes up and will not clear. I have tried this some 5 times now and each time it comes up with the same result.

Geoff

It's a common problem (not London Bridge specific), which seems to be caused by clicking on the scroll bars.

If we could get some information about your system, OS, graphics cards, driver versions etc it may help us narrow the problem down.

Also check your drivers are up to date.

For a work around, use a scroll wheel (Shift + scroll allows the vertical scrolling)

headshot119 in post 109636 said:

northroad in post 109635 said:

Is anyone having difficulty with London Bridge since updating with todays updates.
I now try and successfully launch the sim with the 2010 to 2014 era but as soon as I try to scroll the up and down scroll bar the scroll bar bottom turns black and the message sim not responding comes up and will not clear. I have tried this some 5 times now and each time it comes up with the same result.

Geoff

It's a common problem (not London Bridge specific), which seems to be caused by clicking on the scroll bars.

If we could get some information about your system, OS, graphics cards, driver versions etc it may help us narrow the problem down.

Also check your drivers are up to date.

For a work around, use a scroll wheel (Shift + scroll allows the vertical scrolling)

HP Envy with Intel(R)Core (TM)i7 4700MQ CPU @ 2.4GHz 64 bit operating system using windows 8 with all updates and drivers fully up to date.

Although why everything should be working fine until I downloaded the updates and then encountering this problem is really hacking me off. Perhaps I should have left well alone because I now have a sim that I cannot use.

Geoff

Yes the work around does work agreed but should I really be expected to have to use a workaround. For something that was working fine last night and not being used again until I have just opened the computer up and the first thing I do is load the update and nothing else then pardon me if I am just a little bit suspicious when you say it has nothing to do with the update.

Geoff

Headshot,
If it helps your investigations then I have just done a system restore from 16:20 yesterday afternoon and everything is working fine when I open the sim. Nothing happened after that point when I closed the computer down as I said so this still leads me to believe that it was the update that has caused the problem

Geoff

But I am always prompted to allow updates to the computer so how do you work that out...something that Sim Sig always does also and I blindly accept it every time figuring that Sim Sig is a trusted source ........sorry if I am appearing a bit dumb here...

Geoff

Loaded a saved simulation, and there were 3 routes which did not have points properly set.

2 resulted in signals stuck at red, one resulted in a call from a train reporting that the points were set against it.

2B18 is duplicated in the timetable it seems to happen about 0815 when the 2nd one enters from Norwood junction while its old one is in P1 at Charing X.

Just got to this - bug or timetable issue ?

2B18 is duplicated in the timetable it seems to happen about 0815 when the 2nd one enters from Norwood junction while its old one is in P1 at Charing X.

Just got to this - bug or timetable issue ?

Neither really - different TOC's using he same headcode at around the same time, I recommend if 2B18 (W30825) has reached Charing X and the next working TD is in the outward berth, delete it, you should then be able to make the incoming 2B18 (W41755) ARS and all will be fine.

ncidentally if the TD of the first 2B18 is not deleted, the ARS handles the second 2B18 without a problem

I think we are now talking in this thread about the actual timetable that was updated at a later date than my initial post so should be given a new thread to help future use and possible help.

Seeing as we are talking about the new timetable and the confusion caused by duplicate headcodes I thought by putting the UID into the timetable when writing was supposed to eliminate this problem of ARS being confused.
Quoting the section on UID's as explained in the new timetable writing part of the Wiki it says...

"Unique ID

A unique ID belonging to the train. This allows multiple trains to use the same headcode throughout the day, without the simulation confusing them. For example, two trains can have a Train ID 1L55, however as long as they have separate Unique IDs (and these IDs are used in activities and rules) the simulation can differentiate them correctly and any activities will function correctly. When a unique ID is specified in an activity or rule, it must be prefixed by a $ symbol. Unique IDs are only displayed when writing timetables- when playing the timetable, only Train IDs will be shown. For example, if a train has a next working with Train ID 1F34 and Unique ID A12356, the activity would be written as N: $A123456 in the timetable editor, however only 1F34 will be displayed when playing. Internally, the simulation uses the Unique ID to ensure the train forms the correct 1F34. Note that a train ID must also be specified, Unique IDs are optional."

If this is not applicable then why do we need to have the UID in the timetable writing as carried out by people....

I think we are now talking in this thread about the actual timetable that was updated at a later date than my initial post so should be given a new thread to help future use and possible help.

Seeing as we are talking about the new timetable and the confusion caused by duplicate headcodes I thought by putting the UID into the timetable when writing was supposed to eliminate this problem of ARS being confused.
Quoting the section on UID's as explained in the new timetable writing part of the Wiki it says...

"Unique ID

A unique ID belonging to the train. This allows multiple trains to use the same headcode throughout the day, without the simulation confusing them. For example, two trains can have a Train ID 1L55, however as long as they have separate Unique IDs (and these IDs are used in activities and rules) the simulation can differentiate them correctly and any activities will function correctly. When a unique ID is specified in an activity or rule, it must be prefixed by a $ symbol. Unique IDs are only displayed when writing timetables- when playing the timetable, only Train IDs will be shown. For example, if a train has a next working with Train ID 1F34 and Unique ID A12356, the activity would be written as N: $A123456 in the timetable editor, however only 1F34 will be displayed when playing. Internally, the simulation uses the Unique ID to ensure the train forms the correct 1F34. Note that a train ID must also be specified, Unique IDs are optional."

If this is not applicable then why do we need to have the UID in the timetable writing as carried out by people....