Marc Nelson's "Surfliner" Amtrak locos - no cabview in OR

[seagoon]

They display fine in MSTS and did display in earlier versions of OR but in the X1755 experimental an advisory note appears when pressing '1' that the cab-view is unavailable.

Bruce

[nicober]

I confirm this problem of no displaying cabview of the F59PHI Amtrak and the F59PH Metrolink of Surfliner route with version X-1744 & X-1755. But no problem with version X-1705 and many other locomotives of 3DTrains.

Nicober

[baldwin]

It might be caused by the sanding line in the eng file, another example of lazy coding.

Sanding ( 15mph #sanding system is switched off when faster than given velocity )

Change to

Sanding ( 15mph ) Comment ( sanding system is switched off when faster than given velocity )

and the cabview should be restored.

[roeter]

When using a Surfliner push-pull consist, there is a further problem as both the HOME and END view are shown at the wrong end of the train.
It is not likely to be the 'comment' problem as that would show an error in the logfile.
Bug has been reported on this (no. 1226794).

Regards,

Rob Roeterdink

[seagoon]

Thank you for the suggestion.
I'll give it a try.

Bruce

P.S.
Yep...that did the trick.
Thanks again.

[nicober]

After modification of the line

Sanding ( 15mph #sanding system is switched off when faster than given velocity )

for

Sanding ( 15mph )
# (sanding system is switched off when faster than given velocity )

Note: # or comment are equal.

The cabview is now visible again.

Thank you very much!

Nicober

[latimers]

Not sure why this is described as "another example of lazy coding". It was written for MSTS and runs without problem in MSTS. Just because OR requires different coding doesn't mean the original was an error!

[OTTODAD]

Apart from the missing cab view mine has no train brakes at all and the said to be fixed one move faster train brakes release is still not working with my Dash-9, bug report posted.

[seagoon]

Apart from the missing cab view mine has no train brakes at all and the said to be fixed one move faster train brakes release is still not working with my Dash-9, bug report posted.

Thanks very much for letting us know about additional items in a thread that focused on the cabview of one specific locomotive!

[baldwin]

Not sure why this is described as "another example of lazy coding". It was written for MSTS and runs without problem in MSTS. Just because OR requires different coding doesn't mean the original was an error!

It works in MSTS because the way MSTS was coded allows this to happen. I call it lazy coding because it is lazy to include comments inside of a dataset instead of creating a separate comment. MSTS actually ignores the # in such circumstances.

[eric]

It is also lazy coding on MS's part, as they're making up for the missing paren --- everything after a # should be ignored.

I've seen other examples where MS code does error correction when you don't ask for it. One of my favorites was in Streets and Trips, where the GPS would be ignored and he display would force the indicator to follow a road, even when off-roading.

[OTTODAD]

Thanks very much for letting us know about additional items in a thread that focused on the cabview of one specific locomotive!

This thread is about the 3DTrains Surfliner and it's brakes not working on mine at all is related and would appreciate a helpful reply from its users who have posted in this thread rather than a sarcastic one !

[baldwin]

It is also lazy coding on MS's part, as they're making up for the missing paren --- everything after a # should be ignored.

Which is exactly what OR is doing in this case, thus no cabview because that line follows the # symbol.

[mikephfl]

I just fixed all of my 3dtrains engines with a few key strokes and mouse clicks. After reading this post I had a good thought (one of my rare ones) and came up with the idea of a new feature for YardMaster that lets you specify a quick "find and replace" type function for eng and wag files so that these easy fixes can be done for a bunch of files all at once.

wagfixpic.JPG

I have about 47 eng files that need to be edited and this made it much easier and can handle any other changes of this type in the future.

I'm planning to release a new version of YardMaster in early October with a bunch of new features along with some tweaks and fixes for the exiting ones.

[OTTODAD]

Using my UltraEdit-32 editor replaced all these #sanding lines in all my Trainset *.eng files with ) as shown below and still have no cab view.

That line also stopping ORTS to read the rest of the file is the cause for its train brakes not to function !