Modifying Activities

[CNW 5099]

Uh oh. I changed the locomotive from the SD70 to an SD45 and an SD40R, that may have messed it up. The thing is it didn't work for me in the original activity either. We need an OR activity editor ASAP.

[CNW 5099]

Am I the only one having issues with the helper on the EURVQ(?) activity? It never comes out of the siding and connects to the rear of my train.

[CSRX]

Am I the only one having issues with the helper on the EURVQ(?) activity? It never comes out of the siding and connects to the rear of my train.

Which version of ORTS are you using? I found that 1.5.1 works best, and you must leave at least a car length or a bit more between the rear car, and the switch.

[CNW 5099]

Which version of ORTS are you using? I found that 1.5.1 works best, and you must leave at least a car length or a bit more between the rear car, and the switch.

I'm using the latest test version. I definitely pulled up more than a few car lengths but not too far where I think it should cause issues with the helper. I'll try backing up some and see what happens.

[CSRX]

I'm using the latest test version. I definitely pulled up more than a few car lengths but not too far where I think it should cause issues with the helper. I'll try backing up some and see what happens.

You should be using the 1.5.1 stable version, not the test version, as it was designed with 1.5.1 in mind, and I'm sure like always, the test versions will find things to break, which in the case, it seems like it did.

[PerryPlatypus]

Agree with Shawn. And to add to it, if you've done *anything* in TSRE to try to edit that activity in any way, that would most likely break the helper coupler operation as well. In developing these activities I ran into numerous instances where TSRE would inadvertently delete custom activity parameters that I had put into the ACT files - presumably because they were newer ORTS activity parameters that Goku had not yet programmed into TSRE, and thus his program did not recognize them and purged them upon saving. Helper locomotive automatic attachment was one of these features that TSRE would purge

[geepster775]

I use the latest testing version and the only time the helper did not emerge from the pocket was the one time I stopped well past 3 carlengths beyond the switch.

[R. Steele]

Uh oh. I changed the locomotive from the SD70 to an SD45 and an SD40R, that may have messed it up. The thing is it didn't work for me in the original activity either. We need an OR activity editor ASAP.

That's not going to happen ASAP .... there are work-arounds, manual use of editors like ConText, and Notepad++, etc --- more time consuming, but certainly useful. OR has progressed far enough now that the TSRE is doing to OR what the MSTS-AE has always done to OR -- not saving changes/parameters it has not been coded to recognize.

[wwhall]

The TSRE Activity Editor will wipe out a number of things in an activity file--certain events, etc. that it is not coded to understand, as Gerry states. My workaround is to copy an activity before modifying it in the TSRE AE. Then after I modify the activity, I open the copied original file and copy/paste the things in the "new" activity file that the TSRE AE wiped out. Also, if I'm just doing a minor edit, such as modifying an event, etc., I will just do it Context, rather than using the TSRE AE. One of the best features of the TSRE AE is being able to place loose consists exactly where they need to be in the route--something that just wasn't possible in MSTS. I will often use the same loose consists and locations in multiple activities. In that situation, I will just cut/paste the loose consist list from one .act file to another .act file, using Context. It's not the ideal way to have to do things, but it will have to do until a full-featured OR AE is developed. I have not used the MSTS AE since about 2013, and I've made dozens of activities since then, so it can be done. Also, the OR Trackviewer runs circles around the MSTS Path Editor in what it can do.

[R. Steele]

Excellent observation and advice from wwhall [ post #32 ] -- I have been using the same approach for a few years and producing very enjoyable activities, especially when also using the OR Trackviewer to add specialized waiting points to the paths. Making -- editing -- fixing paths is quite easy with the trackviewer.

... Then after I modify the activity, I open the copied original file and copy/paste the things in the "new" activity file that the TSRE AE wiped out. ...

I use the same routine, instead of copy/paste I use a program called "Beyond Compare" >>> https://www.scootersoftware.com/

It is payware, however there is a free trial to check it out. It is extremely versatile, by opening both the "new" activity file and the original activity file in Beyond Compare you can easily move sections between the files however you want. Since I've become proficient in using the program I no longer copy and paste, especially if I have made numerous changes. I just cannot write enough good things about this piece of software...should be in every ones tool kit. It will merge, compare, and synchronize folders and files, with dedicated viewers for data, binary, executables and images. Copy/Paste errors disappear.

[derekmorton]

Gerry,

Off topic, but I use Beyond Compare for global\tsection/dat maintenance.
I could not do without it.

[R. Steele]

Gerry,

Off topic, but I use Beyond Compare for global\tsection/dat maintenance.
I could not do without it.

LOL, we have been wandering off topic for some time now. I didn't think the posts needed to be moved...the sale is over now. I hope the digression is beneficial to some members. You've mentioned before of you using Beyond Compare for global\tsection/dat maintenance. I hope people realize this is one of the functions that take place behind the scenes which is so important to the hobby. Thanks Derek.

[wwhall]

Here is just one example of what TSRE AE will wipe out (every time) when you save an .act file in TSRE AE. A popular addition to any .act file (added using Context) is the AI Crossing Horn Blow command. For a US crossing, the syntax looks like this:

ORTSAIHornAtCrossings ( 1 )
ORTSAICrossingHornPattern ( US )

TSRE will wipe out the second line of that syntax when an .act is saved in TSRE AE. So, if you want the US long-long-short-long crossing whistle/horn blow after using TSRE,AE you have to open the .act file in an editing program (again, I use Context) and add that second line back in. TSRE AE can also wipe out Weather Change events. Also, another bug in TSRE AE is traffic starting times. If one modifies the starting times of traffic in the .trf file, after the initial save of the .act file, TSRE will not "flood" the start time changes into the .act file. From what I can see, that's a problem because OR reads the times in the .act file. None of this should be taken as a lack of appreciation for Goku's hard work creating the TSRE--the reality is that TSRE is a work-in-progress where progress stopped for various reasons. Hopefully, someday it will be finished.

[TrainSimJack]

I use the same routine, instead of copy/paste I use a program called "Beyond Compare" >>> https://www.scootersoftware.com/

I've used Winmerge which is free and seems to work well for both file and directory comparisons.
Not to take anything away from Beyond compare, just offering a free alternative.

- Jack

[R. Steele]

I've used Winmerge which is free and seems to work well for both file and directory comparisons.
Not to take anything away from Beyond compare, just offering a free alternative.

- Jack

Always good for folks to have alternatives, thanks ---