Weird Experience/Problem on Sherman Hill

[donjgatlin]

Today I was driving a scenario with 2 SD70M's and 1 SD40-2. I was on Track 3 traveling at track speed when I looked back and noticed all of my cars had 'detached' from my train. That's not the strange part. My train continued to behave/accelerate and decelerate like as if I was still carrying a long consist (have car mods posted here by someone to make cars heavier and changed the friction coefficients). So, thinking I could go back about a mile or two with just my engines and pick up the cars to finish the scenario, another strange thing happens. I am in the free-movement camera 'standing' beside the cars to make sure I couple to them at the correct speed. Weird thing is, they're making/playing the sound that is normally heard when they're at speed-they are sitting still. I get approximately 2 car-lengths from the first grain car and everything goes to all hell. The line of cars suddenly charges forward into my locomotives at track speed causing a massive derailment. This is by fair the most extreme thing I've seen with the game thus far, and I've seen whole trains thrown into a vortex. Have any of you ever experienced this? I'm quite frankly just confused on how this even was possible.

[bpetit]

What scenario was it?

[GSkid]

Well I've never encountered what you described in terms of cars being left behind. But the part about getting within 2 car lengths and all hell breaking loose? A past post of mine I will quote, might shed a little light on this phenomenon that I personally call the "physics bubble" ......

Let's keep it real here. The coupler issues are only PART of the problem when it comes to the physics. Load up Cajon Pass in free-roam where you start in Victorville. Pick the loco of your choice and ditch the cars connected to it for convenience. Run the loco all the way back to Barstow and try to pick up the line of cars on track 24 of the yard. You won't even get close enough to attach your coupler to it cuz it explosively derails the line of cars instantly when you get within about a car's length . That's one of the many issues with the physics.

Speaking of physics... I've discovered that rail assets have what I like to call a "Physics Bubble" surrounding them. I discovered this when trying to make behemoth size monster trains with a HUGE amount of cars connected together. Cuz when I'm approaching a super long line of cars to couple to, my framerate drops from like 30-40fps down to 4fps according to fraps. I used fraps to get a FPS count cuz Railwork's counter won't show below 14fps. It looks weird for your loco to go into bullet-time when you get close to a huge line of cars when it was just speeding along earlier before it.

Then once I'm connected, my framerate pops up to a whopping 7-8fps and pretty much stays at that while I'm pulling the train. Even turning TSX-OFF and every setting to off or the lowest it could go, didn't change this fact. So MIN or MAX setting, you will hit this bullet-time. At least on my rig. It's this "Physics Bubble" I'm hitting when the cars on track 24 derail before I touch them as well.

That physics bubble might be the issue you are talking about. TS2013 starts including the cars or engines you are about to couple to in it's total physics calculations of your engine you are using about a car length or so before you couple to it. At least that's been my conclusion. Physics bubble simply means the point at which the simulator starts combining the physics. You'd think it would happen only when you have coupled or are pushing against the couple of the other assets. But my observations have proven otherwise.

When I made my HUGE monster trains and then saved, a lot of times the train would derail instantly as soon as I loaded my save up the next time. So I came up with a trick of stopping my train, uncoupling and then saving to avoid that issue. But I figured out that you have to move a few car lengths away from your huge trains before saving. Otherwise it would be close enough to still be in the "physics bubble" and would STILL derail instantly. So I always detach and move away from the trains I am pulling if they are long and THEN save my game. It seems to be less of an issue with smaller train sizes and you can usually save with no problems while still connected to the train. But with monster size behemoth trains you assemble yourself.... it's a MUST that you must distance yourself before saving or you risk having to start from scratch.

Hope that helps a little!

[donjgatlin]

What scenario was it?

The scenario was Red Buttes Westbound [GWD024] on the Steam Workshop.

[thecanadianrail]

Ah, I know what's going on here. for some reason in the scenario something went wrong telling the cars to uncouple. now realistically the cars would come to a rolling stop, but to save power and memory the game freezes them once you get a certain distance away from them...until you get close to them again. had this happen lots, its been around since the days of RailSimulator.

[The_Garbear]

This happened to me in the first default scenario for SH as well. I had RW running in the background as I was on the internet doing whatever and I switched to RW and was quite surprised to find that instead of driving 4 ES44s with a long string of double stacks, I was now driving just three ES44s. Odd.