Railworks America Website

by **jwtheiv** » Sun Jan 12, 2014 2:17 pm

Engine appears, but no working horn or bell.

by **charliechan** » Sun Jan 12, 2014 2:26 pm

Good Morning:

I uninstalled the updates and RWA-Pack. Then installed the RWA-Pack and Bobs fix, no joy. I had the textures but no horn or bell. Uninstalled again, first installed the RWA-Pack, second installed Chacal patch, and finally I installed Bobs fix and lo and be hold its all there. Wow nice job guys.

Thanks

by **artimrj** » Sun Jan 12, 2014 2:48 pm

Hmmm on the proxy sound files I only edited the .BIN and not the .XML. Do they both need to be editted? I assume like everything else RW is only uses the BIN file that was made from an XML file?

by **JWStilwell** » Sun Jan 12, 2014 2:50 pm

After unzipping the RWA_NW2_Sound_fix, Norton deleted the RW_assetSetup.exe file. Installed the files manually on the first fix, then installed Bob's fix. I have smoke, but still no horn or bell. I do have the US assets pack.

nw2warning.jpg

by **artimrj** » Sun Jan 12, 2014 3:51 pm

Ok a little more exploring. I tried combining some of Chacal's files with mine. I discovered a sound emitter added to one of the files is what made the textures disappear. Please try this one on a fresh install the package.

Norton also did not like the routesetup.exe for me JW.

by **Chacal** » Sun Jan 12, 2014 4:15 pm

I wasn't sure about the sound emitter. It was there already in the donationware pack but not referenced by any blueprint. I added the reference.
Probably this is all that's needed to change on my fix.

BTW, there is no need for the NW2 basic kit. The RWA NW2 is independent.

Bob, what I have discovered by trial and error is this:
- for all blueprints except sound proxys, you need only the .bin file; it is better to delete the xml file in case of discrepancy;
- for sound proxys you need both the .proxyxml and the .proxybin file and they must be exactly similar;
- the .proxyxml must be in ASCII format (maybe UTF-8 as well), NOT in Unicode format.

The latter is responsible for countless hours I wasted with things that sometimes worked, sometimes didn't.

by **charliechan** » Sun Jan 12, 2014 4:19 pm

Good Morning:

Installed RWA-Pack and Bobs latest patch in a virgin install of RW14 and all is working.

Thanks

by **artimrj** » Sun Jan 12, 2014 4:27 pm

Chacal wrote:I wasn't sure about the sound emitter. It was there already in the donationware pack but not referenced by any blueprint. I added the reference.
Probably this is all that's needed to change on my fix.

Bob, what I have discovered by trial and error is this:
- for all blueprints except sound proxys, you need only the .bin file; it is better to delete the xml file in case of discrepancy;
- for sound proxys you need both the .proxyxml and the .proxybin file and they must be exactly similar;
- the .proxyxml must be in ASCII format (maybe UTF-8 as well), NOT in Unicode format.

The latter is responsible for countless hours I wasted with things that sometimes worked, sometimes didn't.

I used your proxyxmls and made my own for ones that were not there. I believe they are all the same no bin and xml that is. I also discovered the reference to the Kuju folder for the cab sounds instead of RailworksAmerica\ModernUSFreight inside the engine bins. Did not catch that the first time around. Could not figure out what you edited in the engine bins.

Well this worked for Chandler, thanks for testing that Chandler. Hopefully it will work for everyone.

by **Chacal** » Sun Jan 12, 2014 4:53 pm

artimrj wrote:I used your proxyxmls and made my own for ones that were not there. I believe they are all the same no bin and xml that is. I also discovered the reference to the Kuju folder for the cab sounds instead of RailworksAmerica\ModernUSFreight inside the engine bins.

Ah yes there is still a bad reference for the cab occlusion blueprint. Good catch.
In the engine bins I fixed several such bad references.

Edit: I don't think there's anything wrong with rwassetsetup.exe, I think Norton doesn't like setup programs, also there's always been a problem with Mike's web site and certain antivirus programs, it seems to be a reputation problem from what I'm seeing in the above screenshots.
BitDefender seens no problem with it and I trust BitDefender much more than Norton.

by **artimrj** » Sun Jan 12, 2014 5:04 pm

On the setup.exe. Several people use them on here. Harry and Buzz do I believe, Norton never whines about their copies for me. Only yours did. Maybe you need a newer one?

by **jwtheiv** » Sun Jan 12, 2014 5:18 pm

Clean install of RWA Pack + Version 2 of the Patch worked for me. Good work guys. *!!thnx!!*

by **Chacal** » Sun Jan 12, 2014 5:24 pm

Worked for me too.

artimrj wrote:On the setup.exe. Several people use them on here. Harry and Buzz do I believe, Norton never whines about their copies for me. Only yours did. Maybe you need a newer one?

I was using RW Tools 5.0.32, that's fairly recent. I don't know what's triggering Norton. Maybe I'm not packaging correctly.

BTW, how did you make your rwp package? I tried the RSC packager, but it wouldn't let me select files already used in other packages. They were showing in blue color and labeled "protected", whatever that means.

by **artimrj** » Sun Jan 12, 2014 6:56 pm

I am working on another route and made a copy of Railworks with only my route and assets in it. I copied the finished RWA pack to that installation and used the Utilities program/Packager Manager from there. In my copy of Railworks is 84 gig of stuff that takes about 35 minutes for Package Manager to refresh. My work copy takes about 15 seconds to refresh. Then I went in and just ticked of the files we changes or added and packed them up.

Is it possible some of your folders are write protected. Seems like every now and then I get folder as READ ONLY and things start happening that you are not expecting.