[Icik]

Csantucci, on 28 October 2015 - 01:59 PM, said:

Hi Icik, can you attach file bse.ace, so I can test?

http://uloz.to/xNXDYcbD/bse-ace

[Csantucci]

Icik, on 28 October 2015 - 02:06 PM, said:

Hi, I can´t. He say "Error You aren't permitted to upload this kind of file"

Thank you for the link. Next time simply zip your file, and then you will able to upload it.

[Csantucci]

Hi Icik,
try this version

P.S. Version updated at 12:00
P.P.S. Version for x.3287
6/11/15 File removed because now function available in standard OR version

[Icik]

Thanks, but it is same. Nothing was changed. Still as I wrote.

Wenn ich den Satz "NumPositions ( 5 4 3 2 1 0 )" verwende, es sollte erst Bild 4 dann 3 dann 2 bis 0 aus Texture angezeigt werden.
Aber OR zeigt das Bild 0 dann 3 und dann nur leere weisse Rechtecke an.

https://youtu.be/2r56qcWhrPY

[Rogue]

Icik, on 29 October 2015 - 02:17 AM, said:

Thanks, but it is same. Nothing was changed. Still as I wrote.

Wenn ich den Satz "NumPositions ( 5 4 3 2 1 0 )" verwende, es sollte erst Bild 4 dann 3 dann 2 bis 0 aus Texture angezeigt werden.
Aber OR zeigt das Bild 0 dann 3 und dann nur leere weisse Rechtecke an.

https://youtu.be/2r56qcWhrPY

Translation:

When the line "NumPositions ( 5 4 3 2 1 0 )" is used, pictures 4, then 3, then 2 down to 0 should be displayed.
But instead OR displays picture 0, then 3 and after that only white squares.

[Csantucci]

Sorry Icik,
I forgot to insert two .dll files in the .zip file. Pls. download again the above .zip and try again.

[Icik]

Yes, now the order read back. But when I change the order to NumPositions ( 5 6 3 2 1 0 ), Openrails is reading frame 4 3 2 1 0 but no 6 3 2 1 0.

Please fix also this.

[Csantucci]

The actual OR data structure does not allow this as far as I can see. "Holes" within the texture frames list are not possible. You will have to live without this. By the way, why should a texture be built this way?

[Icik]

I have no idea why some cab are builded this way.

Anyway thanks for good work with backreading of texture. This is helpfull.

[copperpen]

Even in MSTS there should be no "holes" in a texture used in a cvf. The data such as NumFrames ( 10 5 2 ) specifies that there are 10 frames in the texture and that these frames are in 2 rows of 5 frames. Looking at the ace file uploaded to this thread, it has 3 lines of 3 with the last 4 frames being blank, so it does not match the frames of 10 5 2. In MSTS if it finds a blank frame, it will not display it, instead leaving the display at the previous known good frame.

If you look at the Dash9 combination throttle/dynamic control there are 18 frames in 3 rows of 6 and all frames display in both directions.In the cvf they are numbered from 0 to 17, with 9 being the centre neutral position.