Well I must be doing something wrong. Every time I start making a new act, I click the Convert switches to manual and Convert signals to permissive.

I get the pop up saying something about switches have been changed. Same for signals. I seem to have no problem with some acts, but on the longer one where I do a little traveling, I cannot throw some switches, or get by the light.

Is there something else I have to do ? I am on one now on the revised East Metro, that has pu and so at CL LL Coal plant and I cannot get off the main at either end of the coal plant. Must be doing something wrong. Thanks

Bert

These problems show up on some routes, and not on others.

You are not necessarily doing anything wrong. Occasionally we run into a track switch that won't convert, or a signal that seemingly won't convert. If you can send Steve the specifics about the location, then maybe he will be able to figure out why the track switch is not coverting. We found several on the Stevens Pass route that would not convert no matter what. As for the signal, in time past when I hit one of these signals it usually had to do with how the signal itself was set up, and carefully moving the player train forward or backward, closer or farther, seemed to release the signal to clear. Also, sometimes I had to "save game" and restart for the signal to clear. None of this is your fault -- it is all related to the MSTS signaling mess.

If we cannot get this fixed, then perhaps I can create a specific path to get around this problem.

I am not sure when Steve will be able to help. Another of his daughters is getting married (last weekend? or this weekend?) plus his company is in the middle of a buyout/merger.

Thank you Norm for covering for me! My daughter's wedding was Saturday and it was beautiful, and the buyout closes this Thursday. So I will be more attentive to these forums very soon!

The problem here is the software changes certain flags in the TDB so that signals which once displayed 'STOP' now display 'STOP AND PROCEED' and switches which were flagged as dispatcher controlled (automatic) are now flagged as manual. However for some routes, based on the way that route author set up his/her track objects and the track database, certain signals and switches simply don't convert when these flags are changed. At this point I have not figured out any way to get around this, and the best approach if you need a path into an area that you can't get to by converting signals to permissive or switches to manual is to create or edit the path in the Activity Editor or ask the template designer to do it if that template seems to require work at a spur that can't be reached. (So sorry, back on you Norm on this one!)

Thanks,

Steve

Thanks Norm and Steve

I fecal better now that it has been explained to me. I had a problem at the same location on one of the original activities. I was not able to get off the main at the 1st entry. Was able to back in at the 2nd entry. I will try it again and if I cannot get in I will go on and make another, not using the coal plant.

Speaking of the Stevens Pass route, I live about 1\2 mile from the route here In Gold Bar, WA. I can see the trains in between the trees. We are in the Cascade Mt foothills, about 18 miles from the 8 mile tunnel. Thanks again

Bert

I have run into some issues with signals as well a few times. In some cases, I really feel some issues are caused by the locations of all the trains, player and AI, at the given time when you decide to switch the signals. Make sure you always change them before you pass an absolute signal. Otherwise it won't let you pass if you change the signals after the fact. Such is the case on the Bob Wirth's Seligman Sub where there are multiple signals close together. One thing I haven't tried yet is to run without AI traffic. For switches, I have run into many with the frozen point syndrome, where they do switch, but visually they don't.

Jim

Jim,

Great advice on both counts! Yes it is best to change the signals before passing an absolute, and also I have seen switches that don't seem to throw (no change in the visual graphics) but they throw nonetheless.

Thanks,

Steve

Hi there from a new member.

I have read many posts about switches that will not change, and stop signals that are stubborn, looking for my answer. Not found it so far.

Maybe someone can help me?

I have downloaded one of the best freeware routes (in my opinion and many others too).

I have tried 3 switching activities provided by the route creator and in all of them I eventualy get to a place where I am stopped at a signal or a needed switch will not throw. Judging by the quality of the package, I highly doubt that the creator would include activities that are impossible to complete.

I also generated two activities for the same route with Activity Generator and the template providede by Skyline, and same problem. I get stuck somewhere. The dispatcher always denies permission to pass the signal. I tried the AG options of all switches to manual and all signals to permissive, and even if I start the activity over from the beginning, same deal.

Uninstalled everything, did a fresh install of MSTS and add-on, and still the same. Just seems like a 0 for 5 record is too far off the mark to be just the random problem with MSTS.

I'm still enjoying myself, but it is frustrating to get just so far, and then can't complete to work order.

Anyone have a hint for me? Thanks. :-)

Which route is this? Do you have the activity set up with traffic? It is possible to have timing issues with some AI traffic. I also believe somethings won't change if the signals have been set by some traffic that is already within a certain range of the switches and signals you are trying to pass. If you are trying to back the train thru the signal, it is important to change the signals to permissive before you go past the signal in question.

Jim

Thank you for your reply. I didn't say what route, because I didn't want to sound as if I was criticizing it. I really don't think it's the fault of the route creator.

I don't think it really has anything to do with traffic though, because in one activity, the work was entirely within the yard, which I had traveled through and saw no AI traffic at all. In another, I had to enter a yard just to use the Wye, and there was no traffic on the way in, and no matter how long I wait at the signal (hours even), there is still no traffic. I can also zoom out far enough (using MSTS Bin), to see that there are no other trains.

Tricky stuff ;-)

Did you try to tab past the signals?

yes I did - permission is always denied

i even tried running one - yup - activity ended ;-)

No doubt you tried all the other usual MSTS tricks, such as inching up close to the signal and then backing up and then reversing again. And the old save and restart from the save point?

Okay - I figured it out! I'm such a dork.

I was doing this:

1. Push 'Choose Activity File' - I chose it.
2. AG loaded the xxx.csv file
3. Push button - Convert all signals in a route to permissive
4. The default file name box is filled in with the activity .csv file I had just loaded, so i clicked Open
5. Message box says 'succesfully backed up' xxx.csv
6. Click 'OK'
7. Message Box says 'Sucessfuly converted switches to permissive. You may now pass red signals at restricted speed.', but it didn't actualy convert any signals at all, cuz, what it really wanted to load and work on was a .tdb file.

So - error on my part, cuz I should have:

1. Push button - Convert all signals in a route to permissive
2. Choose a .tdb file to load and modify
3. Then it will work right :-)

--------------

Maybe a clues to the switch mystery? :

After actualy changing the .tdb file, I ran the first yard switching activity that I tried previously and had been stopped at a red signal with no way to pass it.

Now - some other signals in the yard are flashing 'permissive', but the switch where I was stuck before is still solid red, dispatcher still denies permission, but I can pass it anyway without 'Ending Activity' penalty. :-)

So - my bad for not actualy looking at the 'file filter box' to see what what type of file was wanted, but maybe a little AG bug too. :-)

Anyway - thanks for the replies and help. I do appreciate it.

Signed,

Happy Camper :-)

EDIT - Where I mention .tdb files above - should say 'sigscr.dat' file (those are for signals)

.tdb's are for the switch modifying

If there is a bug I'd love to fix it. I am not entirely sure what the bug is. We have the File Filter Box set to .tdb for the track database file. Can you tell me what the issue is? Where do you believe the bug is?

Most signals won't do you the courtesy of flashing red if they are set to permissive. The way to know for sure is to use the F4 display, and then instead of saying "STOP", under the red signal, the text should read "STOP AND PROCEED" and/or the speed will be something other than 0 MPH.

Thanks,

Steve

Well - maybe bug is wrong word. More like it doesn't prevent me from being a moron. :-)

1. Push 'Choose Activity File' - I chose it.
2. AG loaded the xxx.csv file
3. Push button - Convert all signals in a route to permissive

4. The default file name box is filled in with the activity .csv file I had just loaded, so i clicked Open, not looking further, since i thought AG already knew what I wanted, and had filled in the default for me.

Here you want to know what sigscr.dat file to work on, but the file select box gets auto filled with the .csv file name i loaded in step 1.

5. Message box says 'succesfully backed up' xxx.csv

6. Click 'OK'
7. Message Box says 'Sucessfuly converted switches to permissive. You may now pass red signals at restricted speed.'

In step 7, AG message tells me signals converted, but there was no conversion at all, cuz i never fed it a sigscr.dat file to work on.

I may be all wacked out too. Anyway, wasn't complaining, just mentioning in case others have same problem.

And yes, I saw the Stop and Proceed in Track Monitor :-)

Thanks A Lot,
Steven

Steve,

I see now what is happening. If you load the CSV file for a particular route first and then go down and choose "Covert all switches to manual" or "Convert all signals to permissive", the Activities directory, the route you just loaded the CSV file for, is the one that shows up. It doesn't default back to "Routes" directory or the main folder for the route you want to change the switches or signals for. It only happens when you load an Activity CSV file.

Jim