Hello! Mattaf of Railtrack Virtual Works here! I have just uploaded the first in a series of 6 Activties. The activites are a steam trip across 2 routes, Fictional ECML Version 3.1 and The Settle-Carlise line.
In the first activity you drive the deisel locomotive, Nimbus, (Included in the download) to Newark. Any comments are welcome. Enjoy and look out for the second part, coming soon!
The Flying Scotsman
Moderator: Moderators
- asalmon
- Very Active Forum Member
- Posts: 5190
- Joined: Sun Dec 23, 2001 12:00 am
- Location: near Bristol
Hi there.
I downloaded the activity, but have some problems with it.
It seems to need a virgin i/c 125 as well as the two supplied locos.
The filename for the consist for the D9020 ends with a space which seems to confuse MSTS.
The above are both fixable. The main show-stopper is that the player path is broken. This crashes MSTS with the send/don't send message. I attempted to repair it in the activity editor - managed to get it all green, but as soon as you start you get an "activity ended-ignored red light" error.
I don't understand why the above occurs, or how come the path was broken in the first palce - I have version 3.1 and have not had trouble with any other activities.
-Alan
I downloaded the activity, but have some problems with it.
It seems to need a virgin i/c 125 as well as the two supplied locos.
The filename for the consist for the D9020 ends with a space which seems to confuse MSTS.
The above are both fixable. The main show-stopper is that the player path is broken. This crashes MSTS with the send/don't send message. I attempted to repair it in the activity editor - managed to get it all green, but as soon as you start you get an "activity ended-ignored red light" error.
I don't understand why the above occurs, or how come the path was broken in the first palce - I have version 3.1 and have not had trouble with any other activities.
-Alan
- asalmon
- Very Active Forum Member
- Posts: 5190
- Joined: Sun Dec 23, 2001 12:00 am
- Location: near Bristol
Hi Mattaf.
I do apologise. I have discovered the problem was an old path on my pc with the same name, seeming left over from version 3. When I install activities I generally say "no" to the overwrite question, but in this case since I noticed the problem file was dated january I let it overwrite.
I think it is a good idea for all activity creators, when they create paths, to include their initials in the name; or name the paths after the activity (I used to do the latter, but will start doing the former).
Sorry again for causing you unnecessary concern.
-Alan
<font size=-1>[ This Message was edited by: asalmon on 2002-05-27 02:51 ]</font>
I do apologise. I have discovered the problem was an old path on my pc with the same name, seeming left over from version 3. When I install activities I generally say "no" to the overwrite question, but in this case since I noticed the problem file was dated january I let it overwrite.
I think it is a good idea for all activity creators, when they create paths, to include their initials in the name; or name the paths after the activity (I used to do the latter, but will start doing the former).
Sorry again for causing you unnecessary concern.
-Alan
<font size=-1>[ This Message was edited by: asalmon on 2002-05-27 02:51 ]</font>