The update should be installed over the top of your existing, functioning version of AG. The update does not include all of the needed files. You say that you have backed up AG. Did you backup the entire folder? If so, you should be able to simply copy this folder from the back up CD ROM into the usual place. Once you do, verifiy that it works, and then install the update over it.
One thing to check: make sure that AG is trying to access the correct directories through the path it should. Sometimes we have heard from users who just could not get AG to work, only to discover that somehow AG was looking in the wrong place for the files -- similar to your statement about not finding the activities.
If you cannot back up to a point where AG was working properly, then maybe you should download the most recent full version. To do this, I think you will need to contact Steve.
Greg,
It sounds like you installed an update but don't have the base program itself. My advice is to go to "Add/Remove Programs" in Control Panel and Uninstall MSTS Activity Generator. Then use your original AG3 full install zip file to unzip and run setup.exe to do the full install. After that install the latest update.
To make sure you have the latest full install please email me directly at SteveDavis@skylinecomputing.com and I will send you the link to download it. It may take me 24 hours to respond though, I am traveling.
Thanks and sorry about the problem,
Steve
Greg,
1.0.6 is the very old SwitchList generator program and doesn't upgrade to Activity Generator. It will only run older SLG Classic templates but it will run those perfectly every time.
It sounds like you will need to reinstall Activity Generator from scratch. Please e-mail me directly at SteveDavis@skylinecomputing.com and I will send you the link to download the latest version, which INCLUDES SLG 1.0.6.
In the future if you start having problems with AG and didn't before, don't uninstall AG itself, it is very unlikely that is the cause of your problems (since it didn't change). You should instead examine what you DID change: new rolling stock you downloaded, new routes, templates, etc. Those things are likely where your problems are.
I have found that the easiest way to find and fix most of these problems is to use TrainStore. Store everything but one route, then see if AG works. Keep unstoring routes until you start to see problems. Usually it's the rolling stock or activities associated with the route that are the actual problem. Also ConBuilder and RouteRiter can be extremely helpful in isolating and fixing these problems. Problems like "run time error overflow" and other things that SEEM LIKE AG problems are almost always the result of errors in .eng, .wag, consist, or other MSTS file related problems. The trouble is my program isn't "smart" enough to always figure out and tell you what's wrong with the file that caused the problem. But that's what the great MSTS file-fixing utilities like ConBuilder and RouteRiter are for, AG and AM don't compete with those programs, they work WITH those programs.
Thanks and sorry about the problems,
Steve
Norm has told me that for some routes, AG won't convert the switches to manual. Not sure about Clinch Valley. If Norm says to convert the switches in his docs then it should work. I'm not sure that's a mini-route though?
If you're saying that you're taking routes which are not mini-routes and making them mini-routes, then I can't guarantee that AG will work perfectly. It expects a certain file structure and that structure will have been altered.
Thanks,
Steve
Greg,
I am sorry, I sent you the link but it was returned to me. Either you have a spam filter that is blocking me from sending or your email address in the header is not correct (I hit reply and got the error).
Here is the error I got:
This Message was undeliverable due to the following reason:
Each of the following recipients was rejected by a remote mail server.
The reasons given by the server are included to help you determine why
each recipient was rejected.
Recipient: <cd636@nbnet.nb.ca>
Reason: #5.1.1 bad address cd636@nbnet.nb.ca
Greg,
I'm glad this solved your problem! And don't worry about the bother, it's NEVER a bother helping folks out who are just trying to use our programs!
Happy Trainsimming,
Steve