[gpz]

Sid P., on 27 December 2014 - 09:54 AM, said:

GP-38 has reversed mouse control of the direction lever, I think.

You are right. But I don't understand how it is set up, since both throttle and reverser have the control setting

Orientation ( 0 )
DirIncrease ( 1 )

which means they are horizontal and increasing from right to left. This seems like a quest, solution is appreciated.

[Sid P.]

Hi Peter,
I'm thinking out loud here...
I am beginning to think there is another aspect to cabview files - how does MSTS know which picture in the set of images has the control at the left ?
Note that the throttle lever's first picture is a lever to the right, and the direction lever's first picture is a lever to the left, but they both have the same indicated direction of increase = 1.
The MSTS cabview editor says they both "increase to the left". How does it know which picture is which? I must be overlooking something.
Also, I notice MSTS has a different mouse behavior when there are only three positions, or two positions, or multiple positions - sometimes it shows a + or - sign to indicate what will happen when you move the mouse.
It reminds me of some head scratching when we were trying to make the needles on the dials move correctly.

Cheers,
Sid

[Csantucci]

I'm here to add a further element of confusion...
In my country they made some tests about the MSTS behaviour for specific command Types() and specific Style() types.
What came out is that, for specific commands, MSTS does not consider the Style() and considers only the command.
To be more specific with some example: for Type ( PANTOGRAPH TWO_STATE ) you can put either Style(ONOFF) or Style(PRESSED) : in both cases MSTS behaves the same, that is with a single click and release you change panto position. For Types (SANDERS TWO_STATE) or (HORN TWO_STATE) instead the command remains active from the moment you press the mouse (or the keyboard key) to the moment you release it, and this both with a Style(PRESSED) and a Style(ONOFF).
As there is a large installed basis of trainsets, it would not be bad if ORTS could behave the same way (maybe under the Enhanced MSTS Compatibility option, if one wants to keep also the "pure" version).

[Sid P.]

Csantucci, on 28 December 2014 - 12:18 AM, said:

What came out is that, for specific commands, MSTS does not consider the Style() and considers only the command.

Yes, I just did some tests with MSTS on the direction lever data in the .cvf file. MSTS knows that it is working on the direction control from the name, I assume.
It knows that there are three images; it does not care if the definition is ( 3 1 3 ) or ( 3 3 1 ) - it draws the lever positions correctly !
Even if you enter the wrong value for the dirIncrease, it shows a + sign when a key press will move to a forward condition, a - sign when moving backwards
and works as you would expect. So I can make the values correct for ORTS and they still work fine for MSTS...
So one has to be careful in studying .cvf files to determine what the rules are.

MSTS also includes detents for the train brake, so that it takes an extra click to move to release, for example.

Cheers,
Sid.

[gpz]

In r2744 I added the MSTS specialities as exceptions/overrides. Now GP38 reveser, horns, and others listed in this topic should work as in MSTS. Carlo, if you have some more of these, please feel free to add them to CVFFile.cs at about line 870.

[markus_GE]

Sid P., on 28 December 2014 - 02:23 PM, said:

[...] MSTS knows that it is working on the direction control from the name, I assume.
It knows that there are three images; it does not care if the definition is ( 3 1 3 ) or ( 3 3 1 ) - it draws the lever positions correctly !
[...]

Don´t forget about the NumValues and NumPositions lines. These define positions to be taken if a certain value of the variable being controlled by the cab-control is reached. Thus, increasing and decreasing directions, and especially which frame is to displayed when, can be guessed, I´d say (correct me if I´m wrong - still a little shaken up from a car accident).

Cheers, Markus

[Csantucci]

gpz, on 29 December 2014 - 06:32 AM, said:

In r2744 I added the MSTS specialities as exceptions/overrides. Now GP38 reveser, horns, and others listed in this topic should work as in MSTS. Carlo, if you have some more of these, please feel free to add them to CVFFile.cs at about line 870.

Thanks Peter,
I've launched my country friends to the hunt of differences between MSTS and OR regarding cabview mouse control ;) If something significant and feasible comes out, I'll try to introduce that.

Markus,
sorry to read that. I wish you a fast healing.

[Csantucci]

Peter,
I've got the indication that Bell works as Horn in MSTS, that is, even if Style is set to ONOFF, bell is activated until the mouse button is released. As bell operation has been already discussed sometimes in the forum, before modifying the code I would like to have an OK from you that there aren't counterindications.

[gpz]

No, I have no problem with modification of the bell, just go ahead. ;)

[Csantucci]

Done in r2747.

[markus_GE]

Csantucci, on 29 December 2014 - 12:13 PM, said:

[...]
Markus,
sorry to read that. I wish you a fast healing.

;), but nobody was injured (thank goodness), and there´s only little damage to both cars. I meant to say "metally shaken up", ´cause I was the one at fault.

Cheers, Markus