Class 77 Avaliable.

[andyw823]

I am not very happy with the 77. The spedometer shoes the wrong numbers (I hate to drive with the HUD) and the loco jerks and jumps over the track at speed. No smooth riding. The 76 goes much smoother. And in my eyes the buffers are to big for the loco.

It looks like there were electric blue 77s with and without yellow warning panels. Or the yellow warning panel were added later?

The 76 (as in RW and real life) are built differently to the 77, the 76 loco actualy consits of 3 vehicles, bogie+body+bogie (bogies are actualy coupled together) so it behaves differently which is what gives it that nose lift when pulling off. The 77 is built mounted on its bogies and the boucing effect "i think" in RW is to simulate the track joints, if this bounce lined up with the track joint sounds it would give a better feel, but i don`t think thats possible. I do think the 77 is bouncing too much given its on triple axle bogies and the physics would be more suited to the class 142!

[windberg]

It could be that my English is not correct. At my computer the 77 twitchs in the direction of the ground and back at high speed (above 40 mph). I mean not the bouncing effect. If I drive around 10 mph the speedometer says around 20 mph. I can not drive the loco with the speedometer.

What is your problem with my criticism paulz6? I would like discuss the 77 with other users in this forum and after the discussion I will write an email to support.

[metrobus]

Well to be fair when were BR Speedos accurate, sometimes you could be travelling 25mph but the speedo is bouncing so much you could be doing anwhere between 15 and 45 And thats nothing to say of the accuracy even if they weren't bouncing
regards
Edward

[Marc1972]

Could it be someone has confused it with the class 77 the traction mode lever and the reverser? Hopefully will be repaired. Or was it really a difference between two both locomotives (76 <-> 77)?

[windberg]

@Marc1972: The levers are fine. The 76 and 77 are different.

[Marc1972]

Are you sure? The manual makes no difference. Why? Manual wrong? This difference is illogical and not typical of British design. In practice, the constant danger of confusion. Why should the traction mode lever are so far right? The reverser is not used constantly in the difference in traction mode lever, it is in fact no gear lever as in a car next to the driver.

[tialho]

The speedo looks to be reading kilometers per hour (a reading of 100 corresponds with 62mph on the F3 display) - must have been recalibrated in advance of sale to NS!

Tim

[michaeldono]

Maybe it's a hint to a NS 76

[windberg]

@Marc1972: The cabs are really different and the levers in the Class 77 are OK. The manual is wrong. It describes the Class 76. In the real Class 77 the master controllers have four handles: from left to right (1.) a removable forward and reverse key, (2.) an accelerating lever for notching through all three motor combinations, (3.) a regenerative and weak field lever which varies the amount of regeneration by altering the excitation of the traction motor fields and moved in the opposite direction enables three steps of weak field to be obtained on the motors while taking power, (4.) a lever for selecting the motor combination in regeneration. This is different to the Class 76.

[JeroenO]

It's easy to fix the speedometer.

Go to the Class 77 engine folder (<steamdir>\steamapps\common\railworks\Assets\RSC\Class77Pack01\RailVehicles\Electric\Class77\Default\Engine). Convert the Class77.bin to Class 77.xml using serz.exe.
Now open the Class77.xml with a text editor and search for the following lines:

Code: Select all

<cControlContainerBlueprint-cControlValue d:id="56742136">
	<ControlName d:type="cDeltaString">SpeedometerMPH</ControlName>
	<DefaultValue d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</DefaultValue>
	<MinimumValue d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</MinimumValue>
	<MaximumValue d:type="sFloat32" d:alt_encoding="0000000000005340" d:precision="string">76</MaximumValue>

Change the value in the last line (maximumvalue) from 76 to 120.

Code: Select all

	<MaximumValue d:type="sFloat32" d:alt_encoding="0000000000005340" d:precision="string">120</MaximumValue>

Now save the file and convert it back to Class77.bin (again using serz.exe). You should now have an accurate speedometer.

Now you should do the same for the other two class 77 liveries (BR blue and green).

[transadelaide]

Good advice.

Just an extra note though, you can use RWTextEdit (freeware) or RW_Tools (payware) to automate the Serz.exe decode/encode process.

[paulz6]

What is your problem with my criticism paulz6? I would like discuss the 77 with other users in this forum and after the discussion I will write an email to support.

No problem with your constructive criticism. My comment was about how slowly the file moderators was approving files towards the end of the last week as there was a queue of Woodhead scenarios, one of which had gone around 48hours for approval. Usually it is done within 24 hours. Sorry, it wasn't clear and I meant to put it in the Woodhead scenarios thread.

[FoggyMorning]

What is your problem with my criticism paulz6? I would like discuss the 77 with other users in this forum and after the discussion I will write an email to support.

No problem with your constructive criticism. My comment was about how slowly the file moderators was approving files towards the end of the last week as there was a queue of Woodhead scenarios, one of which had gone around 48hours for approval. Usually it is done within 24 hours. Sorry, it wasn't clear and I meant to put it in the Woodhead scenarios thread.

I think there was a backlog as everyone decamped to Brighton on a Jolly Boy's Outing

[Traveller54]

What is your problem with my criticism paulz6? I would like discuss the 77 with other users in this forum and after the discussion I will write an email to support.

No problem with your constructive criticism. My comment was about how slowly the file moderators was approving files towards the end of the last week as there was a queue of Woodhead scenarios, one of which had gone around 48hours for approval. Usually it is done within 24 hours. Sorry, it wasn't clear and I meant to put it in the Woodhead scenarios thread.

The major flie moderator works shifts btw.

[Easilyconfused]

OK guys - if you have a problem with file approvals then feel free to email support@atomic-systems.com for an update of where your file is at.

It is true that both the site admins were at the Brighton Show from Friday - Sunday. Pete did the set up on Thursday afternoon and like me he found the wifi access at the Premier Inn was appallingly slow. Files were approved over the weekend. The Brighton Show is one of the highest visibility shows we do and being a 3 day show that means Pete is away for nearly 4 days and reliant on the wifi at the Premier Inn for file approvals.

FYI Pete is happily retired these days. Matt works insane hours but not shift work (although it might appear that way to casual observers).

Under normal circumstances files are approved generally twice a day - early in the UK morning and later in the day. If there are problems with the file then an email is sent but since a depressing amount of those bounce due to missing / faulty emails in the accounts those files can wait a while until the uploader raises the issue. The other problem is that BT / Yahoo still routinely block UKTS emails unless you are whitelisting UKTS so the emails never get through and the files sit there unapproved.