Feather River GP35s No cab noise at idle.

[niknak]

Just noticed today that when in the cab of WP 3003/3007/3014/3017 ( all GP35s from the WP3 route ), there's no engine noise when at idle when in the cab. I've checked the sms files and can't see any errors and there's nothing in the OR log. Anyone else experienced this?

[slipperman]

Hi Nick,
I am using the original disk version of the Feather River route but can confirm that, in Open Rails, there are no idling sounds for the GP35s. In MSTS, the sounds are all there.
sms_Checker reports several 'Trigger' and 'CurvePoints' errors but even after they are fixed, no idling sounds are heard in the cab when running Open Rails - in MSTS, they are still OK.

No missing or erroneous sound files are reported in the OR log and I haven't found out the cause of the problem (yet!).

Could it be something concerning the use of VariableTrigger ( Variable2 ? I seem to remember some reports of it not working correctly - but I could be wrong!!

Cheers,
Ged

[niknak]

Thanks Ged. I can't run MSTS unless via OR so I'll wait and see if you discover anything.

[niknak]

Just noticed today that when in the cab of WP 3003/3007/3014/3017 ( all GP35s from the WP3 route ), there's no engine noise when at idle when in the cab. I've checked the sms files and can't see any errors and there's nothing in the OR log. Anyone else experienced this?

Further investigation reveals the lack of engine sound in-cab also seems to occur when in notch 4.....

[crstagg]

Tested with WP-GP35 #3007. Have in cab sound at idle and at notch 4 in both MSTS and ORTS.
ORTS Version = T1.5.1-974-g2634ac3be
WP3 is final beta testing version plus any updates after release.

[niknak]

Hi Nick,
I am using the original disk version of the Feather River route but can confirm that, in Open Rails, there are no idling sounds for the GP35s. In MSTS, the sounds are all there.
sms_Checker reports several 'Trigger' and 'CurvePoints' errors but even after they are fixed, no idling sounds are heard in the cab when running Open Rails - in MSTS, they are still OK.

No missing or erroneous sound files are reported in the OR log and I haven't found out the cause of the problem (yet!).

Could it be something concerning the use of VariableTrigger ( Variable2 ? I seem to remember some reports of it not working correctly - but I could be wrong!!

Cheers,
Ged

*Ged can I ask what OR version you were using when you experienced the same as me? Charles is reporting no problems when using the non-MG version.

*Thank you Charles for responding. My version of WP3 was from this site so I'm assuming no updates were necessary? I'm getting the same problem with cab silence at idle and notch 4 if I use OR Stable release 1.5.1

[slipperman]

Hi Nick,
Tested with the following versions of OR :
Stable - 1.5.1
Testing - T1.5.1-974
ORNYMG - 151.2
Unstable - U2024-04-18-0438

Basic Engine sound missing at start and at notch 4 in all versions.

I don't normally use the Unstable version, but that's the last one I downloaded.

Cheers,
Ged

[niknak]

Hi Ged,
Well that's pretty comprehensive testing! Thanks for responding. I'm sure the truth is out there somewhere....

[slipperman]

Hi Nick,
I can't find anything wrong with the GP35 cab sounds. I replaced GP35_power_cruise1.wav with c50_power_cruise1.wav (from default Class 50 loco) and it played OK at idle.
The format of both files appears to be identical, except that the Class 50 file is a little longer.

I also tested with the GP35_power_cruise2.wav file and, again, it played OK at idle!

Still puzzling!!

Cheers,
Ged

[niknak]

Well thanks for your sleuthing Ged. If the mystery remains unsolved then I guess I'll copy and rename power_cruise2 and power_cruise3 or 5 to cover the two files with missing cab sounds. Oh and if you want a different challenge and you have this loco then stick your head out of the engr's window (RH side) on loco SLI_UP SD40 3014 (in folder SLI_UP_FRC_Engines) and see if you get any sound... Head out on conductor's side (looking back) is fine.

[R. Steele]

I'm sure the truth is out there somewhere....

yes, puzzling, I seem to remember this happening when I first purchased the WP3....(over 7 years ago, probably closer to 10 ).

All I can add for now is >>> TruthIsOutThere.jpg

[niknak]

Well Gerry if the sounds are external then I guess they truly are x_files

[dcarleton]

A limitation of MSTS sound sets is that they often used just two streams for all the throttle notches and cross-faded between them. Triggers built into the streams would start a .wav file playing, and then after it faded out would cancel that .wav file and initiate the next. The two streams would alternate so that the first stream would play idle, and then after it faded out the other stream would play notch 1, and then after that faded out the original stream might play notch 2, etc.

In OR, or even in MSTS after the BIN patch allowed a greater number of streams, cross-fading becomes a liability. Especially when running in Auto-Pilot, sometimes one stream triggers off when the other hasn't begun to play yet. The engine sounds become choppy, or stop playing altogether.

In this case, if you're up for an adventure, here's something you can try:

The 567D engine that came in the GP35 uses the same RPM schedule as the 645D engine from the GP40 and SD40. Sounds very, very similar. There is an excellent SD40 sound set available from NAVS, right here in the library. With a bit of work you can apply that sound set to your GP35s. The effect will be dramatic.

[slipperman]

Hi dcarleton,
Just a note - the default Class50 loco uses cross-fading between two streams and that works without any problem in Open Rails! The only difference being that the Class 50 has fewer triggers.

Cheers,
Ged

[R. Steele]

Route is superb, older msts locomotive sound sets --- not so much.