Posted 23 June 2022 - 10:48 PM
I have checked the code. In all OR versions there is a limit about the maximum number of digits that can be displayed for a digital control in 3D cabs. This number is 6. If the real string is shorter, blanks are inserted in a position that depends from the justification of the control, as defined in the .cvf file.
In the ORNYMG version there is a check (that probably has been dropped in the official OR versions) about the length of the string to be displayed. If this length is bigger than 6, the check aborts the execution of OR, which indeed is a hard measure.
In the other versions there is simply no check, and only the first 6 characters are displayed.
Indeed, if seconds have to be displayed, 6 chars are not enough. There should be 8 (considering also the ":") separators.
Now I can easily remove the length check, and so there wouldn't be the crash, and excess chars wouldn't be displayed.
Increasing the max number of displayable chars to e.g. 8 would also be easy, but maybe might lead to misalignmens with respect to actual OR versions.
Having a variable max number of displayable chars (that is setting it to 8 for clock displays with seconds) is a bit more complicated.
So by the moment I will only remove the length check, and wait for comments by the 3D cab creators for further changes.