[jonas]

Jonatan, on 24 February 2023 - 12:19 PM, said:

... Then I set the number of frames in the cvf to 100, the controls moved their full range with smooth motion. ...

Only for my understanding: where do set the number of frames in the *.cvf - in "NumFrames", "NumPositions" or "NumValues"?

[Weter]

Hello.
I always thought, that 0 1 are range limits, either with MS- or OR- -TS.
It seems to me as very interesting assumption, about 100xValue/"second number".
But a have an answer (assumption too, though): this is needed for unification with combined controls description. (where we have splitted range for two controls)

If we go further, I'd think about brake handles, having general range and, inside it, some sub-ranges for some brake functions.

[jonas]

Weter, on 24 February 2023 - 08:43 PM, said:

...
It seems to me as very interesting assumption, about 100xValue/"second number"
.....

This is not only an assumption of mine. I've made many tests and finally an excell-table, witch proves the "100 x NotchValue/second value" in MSTS.

[Weter]

Thanks.
Never expected something new there.
That's an important note, indeed.

What that table for, and what it does?

[jonas]

Weter, on 24 February 2023 - 09:35 PM, said:

...
What that table for, and what it does?

Hi Weter,

I had only created an Excel table for my exploration of the % values of the throttle lever that MSTS showed me on the screen. I used this table to analyze the throttle sequence from post #5, for example.

Excell-table:
 SecondValueInThrottleLine.zip (9.09K)
Number of downloads: 75

[Weter]

Useful tool. Thanks.

[QJ-6811]

jonas, on 24 February 2023 - 03:38 PM, said:

Only for my understanding: where do set the number of frames in the *.cvf - in "NumFrames", "NumPositions" or "NumValues"?

I don't know if this is what you mean and if it helps?
Example of a "29 notch throttle lever".

 29 notch throttle lever.txt (1.76K)
Number of downloads: 73

[Weter]

Graphic naturally points the name of *.ace-file, which contains given control's image(s).

Num frames means how "graphic" image need to be sliced.
No necessity to use all frames then; also, some frames may not contain any image.
Notes:
1. Critical here, that ORTS parces horizontal and vertical numbers in different way, than MSTS does.
2. I suspect, tri-state graphics are hard-coded in ORTS, what is bad: cab authors often arrange frames vertically.

Num positions sets correspondence between cab control positions and frame numbers
(this is exact list of frames, which are needed to be used for this case)

Num values refers the thresholds within control's range, where previously-selected frames need to be changed.

[Laci1959]

https://kephost.net/p/ODc1Mjcy.png

Hello.

A thought for the 20 positions. I created a 512×512 texture including 21 keyframes. I made it a little rough because I only wanted to depict the principle. The 20 levels in the eng file require keyframes from 1 to 20. Of course, in the cvf file, the individual positions must be assigned to the individual numbers. Since the 2d cab is not visible, it does not matter what it represents. If it is important, it is more difficult to prepare, but the principle is the same.

Sincerely, Laci 1959

[jonas]

In the meantime it is also (again) possible for me to correctly display a large number of more than 10 throttle stages in 2D and 3D CabViews. Thanks again for the reminder about NumPositions and NumValues. Almost a bit embarrassing that my forgetting about it brought me to this "maybe it's a bug" topic here. I paused almost a year with working with TS things.
I looked it up and realized that my last work with the two NumValues was longer than 2018, when I built my previous 3D CabView. In fact, the last time I dealt with the NumValues was in a 2D-CabView some times before 2018.

In Jonatans post, only the wording

Jonatan, on 24 February 2023 - 12:19 PM, said:

...Then I set the number of frames in the cvf to 100, ...

made me wonder whether there is another specific parameter in *.cvf-files that can be used to explicitly set the "number of frames ". I might have forgotten or didn't know such a parameter. However, my guess was that he meant the set of "NumFrames, NumPositions, NumValues", but I was just curious to know further about a possible single parameter to which define the number of frames. Now I know there is no specific parameter that kind.

Based on the topic title here and a self-quote from post #9

jonas, on 24 February 2023 - 11:53 AM, said:

...In OR, the notch values are always taken as absolute percentages ...

here my state of knowledge in a picture:

To what extent this also applies to brakes or other levers, I have not tested.

Greetings
jonas