NS SD40-2 LHF Issues

[ExMilwaukeeRailman]

I too have had this problem with the new brake model. It is so unrealistic in my humble opinion. I just cant imagine that anyone out there thinks this is ok.

I have been editing and poking around in the files since Kuju but I cant find anything definitive on this. I really wish there was a way to fix it but I cant find anything that makes me think the performance is editable.

So disappointing. Thanks to everyone who is working to help try to fix this.

Jake

[MontanaRails]

- Much later edit.

Of course, you could try setting the max value for the VirtualBrake control to say, 0.5 instead of 1, that'd halve the input to the script... don't know what it might break elsewhere though.

I was very optimistic about this idea, but unfortunately when I change this variable there is no change in the braking performance. Whatever is controlling it is overriding or ignoring it. I suspect the main railworks.exe is now controlling it. What I'd like to figure out is how to completely disable the 'realistic braking' system but I have yet to find the right sections in the .bin file. Removing the obvious 'BrakeDifficulty' section just renders the locomotive without train brakes.

So...unless DTG understands the importance of this system, and how broken it is, and fixes this the right way, I think we're going to be without useable North American trains from here on out.

[buzz456]

I don't think the main program controls this at all. What makes you think this?

[MontanaRails]

I don't think the main program controls this at all. What makes you think this?

I agree, it sounds really odd, but I have yet to find any scripts or files of any kind that have been downloaded with the SD40-2 LHF or NS Coal route file structure that would explain the new braking system. Perhaps I'm just missing it, but I've sorted all the files by date and the files and folders look surprisingly similar to DLC before the new brake system. The only other file that was updated at the time of DLC download was the railworks.exe.

Edited for clarity.

[wongsing]

Ok, so I hope that didn't miss this somewhere. With all of these problems regarding the brakes on the new NS LHF SD40-2's and the ES44's that are included with the new NS Coal District route it I figured I would try to isolate the problems we are all having.

It seems that it is ONLY the locos listed above that are causing the problems and not the route or the base sim. I ran 4 different consists of different types on this new route and none of them seem to be have the new "super tight" brakes. Also, I tried the new NS locos and rolling stock on a different route and they still act faulty. This is a shame because this seems to be a great route and I have really enjoyed so far the new equipment. Just wish it worked right...

However, while I don't know that RSC even knows about what is going wrong with the new "reaslistic braking" situation, if and when they do I am sure they will fix it.

-Richard

[MontanaRails]

Just found something I had overlooked.

The file named SD40-2EngineScript.out appears to be where the braking is originating. It is located in DTG\SD40-2LNF_Pack01\RailVehicles\Diesel\SD40-2\Default\Engine

It is 19.5 kb, whereas in comparison the same script from the BN SD40-2 DLC is 2.73 kb.

Notepad++ cannot open the file correctly, but I do see references to the ditchlights, and the new braking system. So this is definitely related, if not the smoking gun. From what I understand, an .out file is similar in function to a .lua file, however, it cannot be edited without the source key. I tried to replace this file with the one from the BN SD40-2, and while the sim loads the session, the locomotive is unusable because there are no brakes, and many of the systems don't function.

So...anyone have any ideas how to find a sneaky way into the .out files? It appears this is our only hope of fixing this issue.

[Kali]

.out are just compiled lua, it's the engine script. You won't be able to edit it, as well, it's compiled. You could replace it with another engine script from somewhere else, but you'll lose the extra stuff. Work out how anything specific to the LHF works & you can stick that in a generic engine script & all will be well.

Alternatively ( this is untested ) steal the TrainBrakeControl setup from some engine you like, rename it to something else ( AutoBrake? ), go into the simulation blueprint & make sure you replace TrainBrakeControl there too, and then remove VirtualBrake from the engine blueprint. Then go into the inputmapper wherever it is and replace VirtualBrake with AutoBrake or whatever you called it.

What that's doing is removing any hooks the script has into the brakes - if you left it with the default name you'd be fighting the script all the time. Unfortunately you might not be able to use the HUD brake control, if that matters.

[MontanaRails]

Ok, so I hope that didn't miss this somewhere. With all of these problems regarding the brakes on the new NS LHF SD40-2's and the ES44's that are included with the new NS Coal District route it I figured I would try to isolate the problems we are all having.

It seems that it is ONLY the locos listed above that are causing the problems and not the route or the base sim. I ran 4 different consists of different types on this new route and none of them seem to be have the new "super tight" brakes. Also, I tried the new NS locos and rolling stock on a different route and they still act faulty. This is a shame because this seems to be a great route and I have really enjoyed so far the new equipment. Just wish it worked right...

However, while I don't know that RSC even knows about what is going wrong with the new "reaslistic braking" situation, if and when they do I am sure they will fix it.

-Richard

For the time being, the only way to make the NS ES44 and the NS SD40-2 LHF somewhat useable is to edit the engine bin file, located here: \DTG\SD40-2LNF_Pack01\RailVehicles\Diesel\SD40-2\Default\Engine\sd40_2.bin and similar location for the ES44.

You want to find the cControlContainerBlueprint for the TrainBrakeControl section and the VirutalBrake section. See attached screenshots for the changes to make. What this does is make the hud and keyboard controls far less sensitive. You'll always want to start a brake application by using just 2% of the train brake lever, as this equals the smallest application the new brake system allows (around 16 lbs to the B.C.). Yes, it's still way too strong, but at least you can kind of run the trains now.

train virutal brake.JPG

train brake control.JPG

[MontanaRails]

.out are just compiled lua, it's the engine script. You won't be able to edit it, as well, it's compiled. You could replace it with another engine script from somewhere else, but you'll lose the extra stuff. Work out how anything specific to the LHF works & you can stick that in a generic engine script & all will be well.

Alternatively ( this is untested ) steal the TrainBrakeControl setup from some engine you like, rename it to something else ( AutoBrake? ), go into the simulation blueprint & make sure you replace TrainBrakeControl there too, and then remove VirtualBrake from the engine blueprint. Then go into the inputmapper wherever it is and replace VirtualBrake with AutoBrake or whatever you called it.

What that's doing is removing any hooks the script has into the brakes - if you left it with the default name you'd be fighting the script all the time. Unfortunately you might not be able to use the HUD brake control, if that matters.

Very interesting idea. I'll try this. HUD doesn't matter to me much - I use it exclusively for ease of use during testing.

Update: It kind of works... the brakes seems to be working correctly (and control is missing from the HUD as you predicted) but the brake needles are missing too from the gauges. Oh well, it was worth a shot!

[ExMilwaukeeRailman]

What's the best way to get this issue in front of the right people? I've tried emailing their support but only got the generic "try to clear your cache" email. Do any of the Dovetail people read or participate here?

I feel like I wasted my money ATM. $58 for the route and Sd40 is not pocket change to me. And there was no reason to suspect it would be so broken from the screenshots and description.

[artimrj]

When you email support you always get a canned message telling you the immediate action you can take. This basically lets you know they got it. Now imagine how many got sent? This means they mght get to your in how long? After 200 or 300 or more other emails. If I am not mistaken there are only like 2 or 3 guys answering emails. Which means you could have a good wait. But chances are someone else a head of you also reported the a same issue, probably quite a few people due to all the chatter everywhere about it, so it may already be being looked at it. I know you don't want to hear this but a little patience is required.

A few of the team do stop by here. We have alot of good people here, thats why RWA is in the credits of the sim.

[Kali]

Update: It kind of works... the brakes seems to be working correctly (and control is missing from the HUD as you predicted) but the brake needles are missing too from the gauges. Oh well, it was worth a shot!

Well that's because it needs more work. Go back in the engine blueprint and change these control names:

aMainReservoirPressurePSI -> MainReservoirPressurePSI
aEqReservoirPressurePSI -> EqReservoirPressurePSI
aAirBrakePipePressurePSI -> AirBrakePipePressurePSI
aTrainBrakeCylinderPressurePSI -> TrainBrakeCylinderPressurePSI

Should get the underlying values from the sim engine rather than the script then. You might need to play with the brake setup after that.

BTW the handrail texture looks like someone autounwrapped it, same as the roof of the UK class 76 that came with woodhead. Not surprising given unwrapping cylinders is horrible to do but eh, not anything I'd put up with :)

[MontanaRails]

Update: It kind of works... the brakes seems to be working correctly (and control is missing from the HUD as you predicted) but the brake needles are missing too from the gauges. Oh well, it was worth a shot!

Well that's because it needs more work. Go back in the engine blueprint and change these control names:

aMainReservoirPressurePSI -> MainReservoirPressurePSI
aEqReservoirPressurePSI -> EqReservoirPressurePSI
aAirBrakePipePressurePSI -> AirBrakePipePressurePSI
aTrainBrakeCylinderPressurePSI -> TrainBrakeCylinderPressurePSI

Should get the underlying values from the sim engine rather than the script then. You might need to play with the brake setup after that.

BTW the handrail texture looks like someone autounwrapped it, same as the roof of the UK class 76 that came with woodhead. Not surprising given unwrapping cylinders is horrible to do but eh, not anything I'd put up with :)

Thanks, that fixed that! I might have been a little hasty with my positive assessment last night. I just tried it again (on a grade), and while it appears the brakes work, the throttle control responds to inputs, but the engine doesn't change rpm in response to the inputs. Seems like we're really close to finding a solution, so I wouldnt be surprised if it's just a few more tweaks. However, the dynamics and independent brake works correctly along with the train brake...so all is good in those respects.

I know enough about poking around in the back end of this program to be dangerous, but not enough to figure things out reliably!

And yes, that handrail is impossible. I poked around with it several times for a few hours trying in vain to find all the truly random spots to paint. I got about 60% of it done before I'd had it - and called it a lost cause.

[Kali]

Hmm. I suspect there's some throttle interlock with the brakes which might be looking for TrainBrakeControl ( or even VirtualBrake ), which will make things tricky. Might have to add the TrainBrakeControl control back ( don't set it up for brakes ) and copy the value of the real brake control to it - but now this is going beyond simple blueprint editing because that needs a bit of scripting to encapsulate the existing script and there's a few things I'm unsure about there.

[MontanaRails]

Hmm. I suspect there's some throttle interlock with the brakes which might be looking for TrainBrakeControl ( or even VirtualBrake ), which will make things tricky. Might have to add the TrainBrakeControl control back ( don't set it up for brakes ) and copy the value of the real brake control to it - but now this is going beyond simple blueprint editing because that needs a bit of scripting to encapsulate the existing script and there's a few things I'm unsure about there.

I agree...I think I'll just avoid it for the time being. At least the NS ES44's brakes don't feel too bad when there are 100 loaded coal cars behind you - I can tolerate that.

For a second I was tempted to get the just-released NS GP38-2 as it is 50% off, but...I think I'll pass until this brake thing gets sorted. My default procedure when I download a new DLC is to modify it before I even run it. I apply custom physics to all the rolling stock, modifying the drag, rolling resistance, and brake settings, install new engine sounds + horn, krellnut's new rolling stock sounds, adjust couplers so they're non-springy, etc. I don't mind doing that editing to tweak things, but when it require such involved workarounds, it kinda takes the fun out of it.

Thanks for all the help! We gave it a reasonable effort!