Railworks America

They have fixed the problem with the cut and paste API key problem,according to the release notes. That alone will help route builders.

CaptainBob
Many thanks for that link which I had missed.
PeterH

The fixed Workshop scenario voting. They fixed Quick Drive resume and AI randomness. And best of all you can run a Workshop scenario from the list again instead of trying to search for it. And the search function is working better too.

And a feature I like, after finishing a scenario you can rate it.

All good stuff!

I haven't downloaded it yet, because I'm worried the rumors are true about them making repaints not be able to be made with this beta. I'm not sure, cause, you know, this is DTG we're talking about.

Nitsujy12345 wrote:I haven't downloaded it yet, because I'm worried the rumors are true about them making repaints not be able to be made with this beta. I'm not sure, cause, you know, this is DTG we're talking about.

I'd have to say those are exactly that, rumors. Who is telling you this stuff?

Nitsujy12345 wrote:I haven't downloaded it yet, because I'm worried the rumors are true about them making repaints not be able to be made with this beta. I'm not sure, cause, you know, this is DTG we're talking about.

Sounds like total BS to me. Everyone is liking how this Beta is working.

"F3/F4HUD Speed & Gradient display improved to read from the front of the train instead of the rear."

This is one of the best things of all. They fixed the discrepancy between the speeds shown on the F4 and F5 HUDs, the speed shown by the cab's speedometer and the speed considered by the dispatcher when checking the "stop at" instructions. In some cases it was the speed of the last car in the consist, in others it was the speed of the locomotive. Now it's the speed of the locomotive and nothing else. So if you come to a halt at your"stop at" location, with the F4 HUD showing 0mph, you will get the tick for the stop at. Before, it depended on what the last car was doing. With a very long consist, because of the way the slack is modelled, the last car could be very slowly (or sometimes quite quickly) going backwards and forwards even if the loco had been at a dead stop for hours, and the "stop at" was checking the speed of that last car, so it would never be ticked. This fix in the beta makes it possible to complete scenarios with very long consists, on routes such as the NS Coal District, that were practically impossible before because of that rubber banding effect at the rear of the consist.

mrennie wrote:"F3/F4HUD Speed & Gradient display improved to read from the front of the train instead of the rear."

This is one of the best things of all. They fixed the discrepancy between the speeds shown on the F4 and F5 HUDs, the speed shown by the cab's speedometer and the speed considered by the dispatcher when checking the "stop at" instructions. In some cases it was the speed of the last car in the consist, in others it was the speed of the locomotive. Now it's the speed of the locomotive and nothing else. So if you come to a halt at your"stop at" location, with the F4 HUD showing 0mph, you will get the tick for the stop at. Before, it depended on what the last car was doing. With a very long consist, because of the way the slack is modelled, the last car could be very slowly (or sometimes quite quickly) going backwards and forwards even if the loco had been at a dead stop for hours, and the "stop at" was checking the speed of that last car, so it would never be ticked. This fix in the beta makes it possible to complete scenarios with very long consists, on routes such as the NS Coal District, that were practically impossible before because of that rubber banding effect at the rear of the consist.

There were two scenarios at least that I tried to run with 100 car consists, in a hilly area, and because the HUD tracked the rear car, controlling the speed was impossible.There would sometimes be a 4 mph difference in the in-cab reading and the Hud reading, which was locked to the rear car. Can't wait to try the scenario again now that they have fixed this.

Or stopping a long train as Mike said with the loco stopped and the HUD saying 5mph or there abouts. I found before the patch that if scenario writers put helpers into long trains this was almost eliminated.