Cabview - Position des Hebels in Texture
#62
Posted 24 November 2016 - 07:34 AM
Here...
Attached File(s)
-
cd_150225_hk.eng (50.16K)
Number of downloads: 165
#63
Posted 24 November 2016 - 10:40 AM
I have checked. As far as I can see, OR works like MSTS.
#64
Posted 24 November 2016 - 12:16 PM
When I set NumPositions to NumPositions ( 5 0 3 4 5 6 ) the frame is so displayed in this order: 0 1 2 3 4 bad
When I set NumPositions to NumPositions ( 5 3 3 4 5 6 ) the frame is so displayed in this order: 3 3 4 5 6 good
Why does it so working?
When I set NumPositions to NumPositions ( 5 3 3 4 5 6 ) the frame is so displayed in this order: 3 3 4 5 6 good
Why does it so working?
#65
Posted 24 November 2016 - 12:36 PM
Icik, on 24 November 2016 - 12:16 PM, said:
When I set NumPositions to NumPositions ( 5 0 3 4 5 6 ) the frame is so displayed in this order: 0 1 2 3 4 bad
When I set NumPositions to NumPositions ( 5 3 3 4 5 6 ) the frame is so displayed in this order: 3 3 4 5 6 good
Why does it so working?
When I set NumPositions to NumPositions ( 5 3 3 4 5 6 ) the frame is so displayed in this order: 3 3 4 5 6 good
Why does it so working?
Because in the first case every number is greater than the preceding one; in the second case it is greater or equal. In the first case an adjustment is done (I found this already in the software), I assume for MSTS compatibility.
I would like that you check with MSTS too to confirm what I found. I don't want to do something different from MSTS.
#66
Posted 24 November 2016 - 12:42 PM
Sorry, but it is not logical. Why OR can not to read so precise like the order is defined?
#67
Posted 25 November 2016 - 11:53 PM
Hi Icik, I made more accurate tests. In fact OR behaves differently than MSTS. I will see if I can correct that.
#69
Posted 26 November 2016 - 12:32 PM
I have a problem: I have created a version where your case works, however this other case, taken from the default GP38, does no more work using the same rules as used in your case:
Also in this case there is a number of positions and values that is different from the number of frames. However here the correct way of doing is to add couples of positions and values up to the number of frames. So, what can OR use to distinguish between the two cases?
Lever ( Type ( ENGINE_BRAKE LEVER ) Position ( 93 401 145 42 ) Graphic ( IndBrake.ace ) Style ( NOT_SPRUNG ) MouseControl ( 1 ) NumFrames ( 18 2 9 ) NumPositions ( 2 0 1 ) NumValues ( 2 0 0.3 ) Orientation ( 0 ) DirIncrease ( 0 ) ScaleRange ( 0 1 ) )
Also in this case there is a number of positions and values that is different from the number of frames. However here the correct way of doing is to add couples of positions and values up to the number of frames. So, what can OR use to distinguish between the two cases?
#70
Posted 26 November 2016 - 01:22 PM
MSTS has certain defined exceptions for enrollment NumPositions (2 0 1), which displays all frames from 0 to maximum.
Can you also implement this exception?
Can you also implement this exception?