Railworks America

when I examined the coupling proxyxml I found this reference: <Pathname d:type="cDeltaString">G-TraX\PortlandTerminal</Pathname> I don't have Portland Terminal ... never did, and it is no longer available.
How should I edit the file to make it work?

Ken

OK, so after looking at some other Coupling.proxyxml files I think it should read GNTX\StevensPass in place of G-TraX\PortlandTerminal, but when I try to edit the file using Notepad++ it won't let me. Do I need a different utility to edit this file, or do I need to turn on some feature of Notepad++?

Ken

Hi Ken,

Once you've saved your new proxyxml, drag it to the serz.exe in your main railworks directory folder and it will update the proxybin. Or you can do it RW Tools somehow but I never do it that way.

Matt

Here's the strange thing .... I edited the file in RW_Tools and clicked "Files Save .xml file", but when I opened it in Notepad ++ the change hadn't taken place. It still had the old pathname reference.

Ken

Ahh, I was using the wrong tab in RW_Tools.

Ken

So I dragged the modified Coupling.proxyxml file to serz.exe, a quick window flashed on the screen, but the date/timestamp did not change for the Coupling.proxybin file in the Coupling folder. Where does the updated file turn up if not back in the original folder? Did serz even work?

Well, I tried the scenario in Stevens Pass and now I have coupler sounds, but I'm not sure exactly why it worked. I read somewhere that if the proxyxml file is newer, TS will use it instead of the proxybin file. Any body know for sure?

Anyway, I now have coupler sounds, so I'm happy if not completely satisfied about how I did it.

Ken

GEtrack wrote:So I dragged the modified Coupling.proxyxml file to serz.exe, a quick window flashed on the screen, but the date/timestamp did not change for the Coupling.proxybin file in the Coupling folder. Where does the updated file turn up if not back in the original folder? Did serz even work?

Well, I tried the scenario in Stevens Pass and now I have coupler sounds, but I'm not sure exactly why it worked. I read somewhere that if the proxyxml file is newer, TS will use it instead of the proxybin file. Any body know for sure?

Anyway, I now have coupler sounds, so I'm happy if not completely satisfied about how I did it.

Ken

You did it right. Serz updates (or creates if there isn't one) the proxybin in the same location of the proxyxml that you dragged to serz in the first place. The only way to check if the proxybin changed is to open it up and see if there is a difference.

IIRC, for some reason you need both files and they must have the same contents.
At least this was true last time I tinkered with sound files.
This is different from the way other blueprints work.

So you must make the changes in the proxyxml file AND generate the proxybin file from that proxyxml file.

IIRC, for some reason you need both files and they must have the same contents.
At least this was true last time I tinkered with sound files.
This is different from the way other blueprints work.

So you must make the changes in the proxyxml file AND generate the proxybin file from that proxyxml file.
Also don't forget to clear the blueprint cache for this provider/product.