Things you should know about MSTS, but obviously didn't!

[delticcity]

Try this one to avoid SPADDING when you are caught out, usually at high speed, by a red signal. Very quickly close the throttle and select reverse before you SPAD. If you then wait until the section ahead is clear, or reverse back behind the red signal, you can usually avoid being thrown out of the activity. I think this has only been possible since the BIN patch enabled cab swapping, and it isn't 100% successful, especially if you cannot see the section ahead has cleared or you don't wait long enough. Dave.

[douglee]

HI All,
The switches (Points) can be thrown (changed) by a left mouse click on the F8 Switch Aid.
It only took me 10 years to discover that!!!!!!!

Who said We live and learn?

Good luck
Doug

[jbilton]

Hi

Cabviews.

Just recently started editing a couple of DMU ones again.

I'd never worked out why the overspeed monitor light worked on 'line speed' on the Class 120 (which I like), but only on the top speed of the Class 124.
Finally noticed that the Class 120 was a 1 cab , but the Class 124 was correctly a 2 cab.

Unfortunately changing the cab to a 1 seems to 'fix' the overspeed, but stops the reset and headlight buttons animation working....(Something else I previously had never figured out why on the Class 120 cab.)

I need to look at a few 'electric' cabs to see how/why their switches work.

Cheers
Jon

[jbilton]

Hi

I need to look at a few 'electric' cabs to see how/why their switches work.

Cheers
Jon

Hi
Just tried the Headlight switch off the series 2000 .... and it doesn't animate..... the Acela doesn't seem to have a headlight switch.

Anyone know of an Electric cab where the Headlight switch does animate ?

Cheers
Jon

[rlmathers]

Hello Jon

The Acela and the Series 2000 have working headlight switches, both animated and with operational light statements in the .eng files.
Both use the TriState routine in the .cvf files:
TriState (
Type ( FRONT_HLIGHT TRI_STATE )
Position ( 470 433 46 38 )
Graphic ( acelalight.ace )
NumFrames ( 3 3 1 )
Style ( NONE )
MouseControl ( 1 )
Orientation ( 1 )
DirIncrease ( 1 )
)

TriState (
Type ( FRONT_HLIGHT TRI_STATE )
Position ( 315 429 31 30 )
Graphic ( LightSwitch.ace )
NumFrames ( 3 3 1 )
Style ( NONE )
MouseControl ( 1 )
Orientation ( 0 )
DirIncrease ( 1 )
)

Other electric locos which I have checked use the TriState routine, example below of the Class 86 cabview:

TriState (
Type ( FRONT_HLIGHT TRI_STATE )
Position ( 350 359 15 20 )
Graphic ( ../../Common.Cab/86cab/86lightSW.ace )
NumFrames ( 3 3 1 )
Style ( NONE )
MouseControl ( 1 )
Orientation ( 0 )
DirIncrease ( 0 )
)

Hope this is of some help.

Kindest regards
Ray

[jbilton]

Hi Ray

Thanks.... but do they actually work (animate) ? .... because I've tried the Series 2000 and it doesn't.
I'll try the Acela .... if I can find one.


Cheers
Jon

[rlmathers]

Hi Jon

grab_000.jpg

grab_001.jpg

grab_002.jpg

Does for me Jon.

Kindest regards
Ray

[jbilton]

Hi

Thanks Ray ..... I wondered if that was the case.

I currently don't have an electric route .... so couldn't test it in an electric train / loco.
There must be a relationship (Hard coded) to the 'type' of engine file too.

So back to the drawing board on the overspeed monitor.

BTW....the other third item that stops working is the wiper switch .... although the sander switch (which is the same) still works.

Cheers
Jon

[rlmathers]

Hi
There must be a relationship (Hard coded) to the 'type' of engine file too.

BTW....the other third item that stops working is the wiper switch .... although the sander switch (which is the same) still works.

Cheers
Jon

Hi Jon

The .cvf and the correct .eng file which if declared in the .cvf file: EngineData () statement, determines the cabview operation for the types of controls etc.
Assuming the control and the display element statements are correct.
The only other problem area for some of the cab elements (control or display) not to work is an incorrect CabViewControls ( counter statement. Greater or less than the elements declared in the .cvf file.

Kindest regards
Ray

[jbilton]

Hi Ray

Thanks....but I think we already know all that.

The situation we have here is a type 1 cab with a diesel..... ( this makes the overspeed monitor work with line speed)
Some of the controls work OK.... but others ( light,reset,wipers) stop working.

Cheers
Jon

[rlmathers]

Hi Jon
In the .cvf file.
CabViewType (1) - Electric
CabViewType (2) - Diesel
CabViewType (3) - Steam

The .eng file wagon section Type () must match one of the above or the correct displays & controls will not be recognised.

I have tested the Class 120 with cabViewType (2) with the following overspeed parameters:
OverspeedMonitor(
MonitoringDeviceMonitorTimeLimit( 0 )
MonitoringDeviceAlarmTimeLimit( 0 )
MonitoringDevicePenaltyTimeLimit( 0 )
MonitoringDeviceCriticalLevel( 60 )
MonitoringDeviceResetLevel( 0.1 )
MonitoringDeviceAppliesFullBrake( 1 )
MonitoringDeviceAppliesEmergencyBrake( 0 )
MonitoringDeviceAppliesCutsPower( 1 )
MonitoringDeviceAppliesShutsDownEngine( 1 )
MonitoringDeviceAlarmTimeBeforeOverSpeed( 3 )
MonitoringDeviceDoesSuppressionReset( 0 )
MonitoringDeviceTriggerOnOverspeed( 65 )
MonitoringDeviceResetOnZeroSpeed( 0 )
MonitoringDeviceResetOnResetButton( 1 )
)
With MaxVelocity ( 65mph ) in the wagon section of the .eng file.

All displays & controls are operational and animated.

grab_006.jpg

grab_007.jpg

Kindest regards
Ray

[NiallGray]

Ray,

Get rid of that version of the route and download the latest one!

[rlmathers]

Sadly Niall, I no longer have the means. 79th in a queue and 5Kb/s download speed is beyond my patience or endurance.
If you would kindly consider placing the route on another site it would be greatly appreciated.
The new route looks absolutely superb, thank you for creating it.

Kindest regards
Ray

[jbilton]

Hi Ray

Yes thanks .... but that is what I mean .... in a type 2 diesel cab the over speed only works on the top speed of the vehicle.
In a type 1 electric cab the overspeed works (reads) on the max line (route) speed .... which I think is better.

Hope you follow what I'm trying to explain.

Cheers
Jon

[rlmathers]

Hi Jon

Two distinct sets of overspeed instructions, ignore the values:
CabViewType (1) - Electric:
OverspeedMonitor(
MonitoringDeviceMonitorTimeLimit( 0 )
MonitoringDeviceAlarmTimeLimit( 5 )
MonitoringDevicePenaltyTimeLimit( 0 )
MonitoringDeviceCriticalLevel( 151 )
MonitoringDeviceResetLevel( 0 )
MonitoringDeviceAppliesFullBrake( 0 )
MonitoringDeviceAppliesEmergencyBrake( 0 )
MonitoringDeviceAppliesCutsPower( 0 )
MonitoringDeviceAppliesShutsDownEngine( 0 )
MonitoringDeviceTriggerOnTrackOverspeed( 1 )
MonitoringDeviceTriggerOnTrackOverspeedMargin( 15 )
MonitoringDeviceResetOnZeroSpeed( 1 )
MonitoringDeviceResetOnResetButton( 0 )

CabViewType (2) - Diesel:
OverspeedMonitor(
MonitoringDeviceMonitorTimeLimit( 0 )
MonitoringDeviceAlarmTimeLimit( 0 )
MonitoringDevicePenaltyTimeLimit( 0 )
MonitoringDeviceCriticalLevel( 60 )
MonitoringDeviceResetLevel( 0.1 )
MonitoringDeviceAppliesFullBrake( 1 )
MonitoringDeviceAppliesEmergencyBrake( 0 )
MonitoringDeviceAppliesCutsPower( 1 )
MonitoringDeviceAppliesShutsDownEngine( 1 )
MonitoringDeviceAlarmTimeBeforeOverSpeed( 3 )
MonitoringDeviceDoesSuppressionReset( 0 )
MonitoringDeviceTriggerOnOverspeed( 65 )
MonitoringDeviceResetOnZeroSpeed( 0 )
MonitoringDeviceResetOnResetButton( 1 )

I have tried by experiment placing the electric instructions into the diesel engine file, unfortunately they are not interchangeable, max velocity was still being detected.
Sorry Jon, but it looks as though we are stuck with what is available.
If you do find a solution please let me know.

Kindest regards
Ray