Open Rails Version 0.6.2 is now available!

[apco25]

Core I7 920 8GB Ram 1GB Radeon 5770, 60GB SSSD, 4 Western Digital Caviar Black Edition 7200 RPM 64mb Cache 1GB drives, Sound Blaster Fatality Extreme Gamer sound card. I'm running 1900 x 1200 res with everything maxed out in OR.

[apco25]

I let several trains sit there and bleed out air for a long time. This improves operation, but if that's the case how are we supposed to start trains on grades with the air set if it causes this screwy behavior?

[OTTODAD]

I let several trains sit there and bleed out air for a long time. This improves operation, but if that's the case how are we supposed to start trains on grades with the air set if it causes this screwy behavior?

Releasing brakes on a long train takes too long in ORTS.

I usually apply regulator when releasing the brakes to stop a train on an incline rolling backward.

O t t o

[longiron]

I let several trains sit there and bleed out air for a long time. This improves operation, but if that's the case how are we supposed to start trains on grades with the air set if it causes this screwy behavior?

Prototype behavior is not screwy. It's easy, just apply less throttle as the brake line pressure releases the brakes. You can monitor ENG slipping via the F5 HUD display. You don't want slipping % to exceed about 25% on most engines. The train will start to move as the brakes release. You can add more throttle as the train builds up speed and slipping decreases. I've easily started 200+ car (6,000+ ton) trains on a grade using this approach in testing. It's just not video game responsiveness.

[longiron]

Releasing brakes on a long train takes too long in ORTS.
O t t o

I must disagree with your comment. The charging and release time is extremely prototypically accurate - assuming the WAG have been set up with the latest physics. We're all used to ridiculously fast charging and release times from our experience with other train sim physics.

If you get impatient, then use the CTRL + ? key to fully charge the brake line instantaneously. This works on almost all consists, but there are some conditions we are investigating where it doesn't work.

[lindsayts]

Just a minor observation AI trains do not obey the speed limits. On the BHPB route the AI trains are doing (the dispatcher says) 105KPH the speed limit for the route being 75KPH.
Experience shows the disptacher is correct as the AI trains are arriving WAY to early compared to MSTS.

Lindsay

[OTTODAD]

The charging and release time is extremely prototypically accurate - assuming the WAG have been set up with the latest physics.

Yes, I agree, having researched the subject of brakes using Westinghouse system ones, but have learned in another thread that using 1000 for the Brake Pipe Charging rate their release can be speeded up, I am happy with.

Doing that and losing the brakes release hissing sound I can live with !

O t t o

[GoGoran]

While long charging times may be correct for the outdated single-release Westinghouse (W) or Matrossov (M) brake systems, what about the newer graduated-release Knorr (KE), Oerlikon (O) and Dako (Dk) systems ? Don't they recharge and release faster ?

[twpol]

Just a minor observation AI trains do not obey the speed limits. On the BHPB route the AI trains are doing (the dispatcher says) 105KPH the speed limit for the route being 75KPH.

Speed limits haven't been implemented at all yet. We'll be sure to make the AI trains obay them when we do, though.

[mikephfl]

Horns don't seem to play right yet Also, one the one activity I started, the lead loco was missing. It had me in the 2nd loco as if the first wasn't even in the consist. Still get great graphics and frame rates, but until the horn is playable it isn't for me.

[twpol]

Horns don't seem to play right yet

This goes for everyone: please could you try and include enough information for anyone to reproduce and understand the issue you are reporting. This means identifying the route, activity, content and whatever else is needed, along with explaining what exactly is happening verses what you expected to happen.

Case in point: I opened up a random route and activity in OR (Hisatsu Line > Isaburo) and tried out the horn. It seemed to work fine, both holding the key and just tapping it. Maybe stayed on a little longer than I expected when I released the key, though.

[longiron]

Horns don't seem to play right yet

This situation may be what's preventing the horn from playing correctly. Could you check the sms file to see if this is the issue?
If at the beginning of the horn stream the Volume statement is set above 1.0, OR doesn't set the volume correctly'

Please attach the OR log file, as it's impossible to assist without understanding exactly what errors are occuring.

Also, one the one activity I started, the lead loco was missing. It had me in the 2nd loco as if the first wasn't even in the consist. Still get great graphics and frame rates, but until the horn is playable it isn't for me.

Please check your OR log file to see what's preventing OR from loading the lead ENG. Rather than fail the entire game, OR tries to load what it can. The OR log file will indicate what the problem is.

[mikephfl]

OpenRailsLog.zipThe route is SLI's Green River route. The engine with the horn problem is their Amtrak F40's. I'll see if I still have the log and attach it later.

The log file is 79K. Too big to attached and too long to past into a message. How do I get this to you?

Hoping this worked.

[OTTODAD]

The log file is 79K. Too big to attached and too long to past into a message. How do I get this to you?

ZIP the *LOG.TXT file and then attach the ZIP to your message.

O t t o

[longiron]

The engine with the horn problem is their Amtrak F40's.
Hoping this worked.

Would you mind attaching the F40PH_EXT.sms file? There are a number of problems that MSTS doesn't seem to mind, but upsets OR like stream count issues that may be causing your problem.
Thanks