IPB
viagra super force buy buy online

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
AG not changing STOP to permissive, AG not changing the sig file
KQXZ
post Mar 12 2012, 11:03 AM
Post #1


Conductor
**

Group: Members
Posts: 10
Joined: 5-March 12
Member No.: 247,499



Hello Folks,

I've got version 4.2.12 and when I try to make the STOP permissive - I get a message that it has backed up the sig file and that I can now proceed to go through the STOP signals.

The thing is -- When I try to do it -- I get the passed stop signal message and the activity ends.
MRW
Go to the top of the page
 
+Quote Post
KQXZ
post Mar 14 2012, 09:25 AM
Post #2


Conductor
**

Group: Members
Posts: 10
Joined: 5-March 12
Member No.: 247,499



Everything is ok now except perm 2 -

The lights still won't let you through but my other routes are fine now - I did not realize I had saved the stop light state and needed to back up a little to get through. mellow.gif

Does anyone know of an upgrade or file that fixes perm 2 ?

Other than that all is well - thanks
Go to the top of the page
 
+Quote Post
dgionet
post Mar 14 2012, 02:33 PM
Post #3


Train Master
*****

Group: Members
Posts: 1,014
Joined: 4-February 07
From: Canada
Member No.: 21



Hi MRW,

I have written in the topic mentioned below over the signalling issue of the Perm 2 route which was a major issue and couldn't resolve completely.

Here's the topic link to the route template done in late 2009. That will give you an idea of how best I have tried to offset this signalling issue.

http://skylinecomputing.com/forums/index.p...550&hl=perm

Unfortunately, there is no update for the route.


--------------------
Denis Gionet
Go to the top of the page
 
+Quote Post
Guest_xxmikexx_*
post Aug 22 2012, 09:13 PM
Post #4





Guests






QUOTE(dgionet @ Mar 14 2012, 02:33 PM) *
Hi MRW,

I have written in the topic mentioned below over the signalling issue of the Perm 2 route which was a major issue and couldn't resolve completely.

Here's the topic link to the route template done in late 2009. That will give you an idea of how best I have tried to offset this signalling issue.

http://skylinecomputing.com/forums/index.p...550&hl=perm

Unfortunately, there is no update for the route.


I've been having similar problems with several different routes, but now I think I understand what's been happening and what the workaround probably is ...

xxxxxxxxxxxxxxxxxxxx

MSTS probably has a "scenery cache" just as MS Flight Simulator does. For purposes of this post let's assume that it does. Now ...

When you save a situation, the information in the save file says nothing about what's in the scenery cache. As a result, if you then run AG4 and tell it to twiddle the switches/signals descriptions, it will do the right thing regarding the files in ROUTES/[routename] but it will do nothing at all to whatever working copies of some of those files were sitting in the cache when you bailed out of MSTS after the save. If you then go right back into MSTS and restore the saved activity, it probably will be running with some unmodified file copies still sitting in the scenery cache, making it as if the AG4 switches/signals twiddler had never modified certain of the switches/signals.

If I'm right (I may not be), the workaround would be to "flush" the cache before reloading the saved activity. The best way to do this would be to switch to a different activity in a different route, and then to return to the saved activity in the route of interest.

I haven't tested this because I sidestep the entire issue by twiddling the switches/signals with AG4 before running any activities in a route. Since I began doing this I have never had a failure of a supposedly-permissive signal. They seem all now to always say "stop and ...".

I hope this helps. I'm not going to insist that I'm right, but I will say that the theory is reasonable, and if MSTS shares the same platform that MSFS uses, it almost certainly is right. MSFS has an option to force a scenery cache flush upon startup but to my knowledge there is no such option mentioned in any of the command line switch options for MSTS that I've come across so far.

(As I said the other day, I may be new to MSTS but I'm learning quickly.)

xxxxxxxxxxxxxxxxxxxx

thx,
Mike McCarthy
Go to the top of the page
 
+Quote Post
jrmeindl
post Aug 23 2012, 12:00 PM
Post #5


Train Master
*****

Group: Members
Posts: 287
Joined: 6-January 07
From: United States
Member No.: 14



MSTS uses a script file to control the signals. so I don't think it has anything to do with a cache file. When using the signal and switch changers in Activity Generator, the program basically rewrites the script file by changing some of the variables. In the sigscr.dat file, it changes Absolute (Stop and Stay) signals to Stop and Proceed. Now, there are some cases where AG can't change the file for some reason. One thing I have found if you must change the signals, you will need to do it before you pass that particular signal. Otherwise, you will have trouble getting the signal to allow you to pass, if you change it after the train went by it. I believe MSTS saves the signal state in the saved file, thus not allowing you to modify the file after the fact.

The issues with the Perm II route lie within the signal script files. That issue I ran into on the Boston & Maine route. AG was not able to change all the signals for some reason. However, since the B&M was not able to support AI traffic, I was able to modify the script file so it would never show a red signal to the player trains.

Jim
Go to the top of the page
 
+Quote Post
Guest_xxmikexx_*
post Aug 23 2012, 12:33 PM
Post #6





Guests






QUOTE(dsweiner @ Jan 28 2012, 01:28 PM) *
Hi Denis:
Thanks so much for the info.

David



QUOTE(jrmeindl @ Aug 23 2012, 12:00 PM) *
MSTS uses a script file to control the signals. so I don't think it has anything to do with a cache file. When using the signal and switch changers in Activity Generator, the program basically rewrites the script file by changing some of the variables. In the sigscr.dat file, it changes Absolute (Stop and Stay) signals to Stop and Proceed. Now, there are some cases where AG can't change the file for some reason. One thing I have found if you must change the signals, you will need to do it before you pass that particular signal. Otherwise, you will have trouble getting the signal to allow you to pass, if you change it after the train went by it. I believe MSTS saves the signal state in the saved file, thus not allowing you to modify the file after the fact.

The issues with the Perm II route lie within the signal script files. That issue I ran into on the Boston & Maine route. AG was not able to change all the signals for some reason. However, since the B&M was not able to support AI traffic, I was able to modify the script file so it would never show a red signal to the player trains.

Jim




The script file controls the signals but the behavior of MSTS says that it does not contain the signal state. If a scenery cache exists, and the behavior of MSTS says that it does, then signal state has to be recorded in the cache or the caching scheme would do the wrong thing. If the state of the cached signal happens to be different from the state of the signal state contained in the static file, exactly the observed behavior would result.

I believe that it is the existence of the cache that causes the "back up before asking the dispatcher to clear you to proceed" strategy to not always work. If true, anything that force-flushes the cache will prevent the strategy failures, which unquestionably exist. (They'd been driving me crazy.)

Since the cache apparently is not cleared on activity restart (which is why restarts often are quicker than activity cold starts), the only certain way to clear the cache would be to fire up a different activity on a different route. Even restarting MSTS might not do it since the cache apparently persists across MSTS restarts, or at least that's my impression. (I haven't tested this specific point since these days I force-set switches/signals before ever running the route.)

xxxxxxxxxxxxxxxxxxxx

Anyway, I was getting failures before my new approach even though I was following the recommended procedures, and now I'm getting nothing but successes, so I don't plan to do things any differently. The cache viewpoint offers a plausible and complete explanation for all the symptoms. It exists with 100% certainty in MSFS; the behavior of MSTS strongly suggests that it exists here too.

By the way, the existence of a scenery cache is further suggested by the beneficial effects of hard drive defragmentation on scenery stuttering. The scenery prefetch algorithm (loads the cache) is able to operate more quickly on a marginal machine like mine, dramatically reducing the frequency with which a demanded tile is not in the cache when requested by the main application. For this reason I make clones by copying, then I defrag, and then I switch the clones (one per addon route) in and out of service via cut-and-paste rather than by copying.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



Lo-Fi Version Time is now: 28th March 2024 - 03:29 PM
viagra super force bitcoin