[Brian Hook]

Since every version after 4022, a warning message appears in the log for every steam locomotive used in the simulation. The log message appears in both an activity and in explore mode.
This message does not appear in version 4022. The warning has no impact on running the simulation but does inflate the error log.
Has anybody else noticed this?
Brian.

 OpenRailsLog 4022.zip (4.83K)
Number of downloads: 89
 OpenRailsLog 4032.zip (5.28K)
Number of downloads: 84

[eugenR]

Brian Hook, on 16 March 2018 - 02:52 AM, said:

Since every version after 4022, a warning message appears in the log for every steam locomotive used in the simulation. The log message appears in both an activity and in explore mode.
This message does not appear in version 4022. The warning has no impact on running the simulation but does inflate the error log.
Has anybody else noticed this?
Brian.

OpenRailsLog 4022.zip
OpenRailsLog 4032.zip

The two-state Parameter in the *.eng-File:
SmallEjectorOrCompressor( 0 1 1 )
is producing this warning.
The new Code (after X4022)seams expecting one more Constant number?

Regards
EugenR

[Brian Hook]

eugenR, on 16 March 2018 - 07:00 AM, said:

The two-state Parameter in the *.eng-File:
SmallEjectorOrCompressor( 0 1 1 )
is producing this warning.
The new Code (after X4022)seams to wait for one more Constant number?

Regards
EugenR

Thank you EugenR for the explanation.
Various programmers added enhancements between 4022 and 4032 which could have inadvertently caused this.
By adding an additional number ( 0 1 1 0 ) the warning disappears but this fix is not practicable for every steam loco one may have in the Trainset folder.
Maybe the programmer concerned will see this post and have a look at the section of code responsible.
Regards,
Brian.

[steamer_ctn]

eugenR, on 16 March 2018 - 07:00 AM, said:

The two-state Parameter in the *.eng-File:
SmallEjectorOrCompressor( 0 1 1 )
is producing this warning.
The new Code (after X4022)seams expecting one more Constant number?

As far as I can see OR currently does not specifically handle the input of two state variables such as the above.

As the small ejector recently coded into OR is better defined as a variable controller rather then a two state device a "new" controller has been created for it. This should remove problems with legacy configurations producing an error message from #4091 onwards.

Thanks for identifying this issue.

[Brian Hook]

steamer_ctn, on 18 March 2018 - 09:04 PM, said:

As far as I can see OR currently does not specifically handle the input of two state variables such as the above.

As the small ejector recently coded into OR is better defined as a variable controller rather then a two state device a "new" controller has been created for it. This should remove problems with legacy configurations producing an error message from #4091 onwards.

Thanks for identifying this issue.

Thank you Peter,
Version 4091 has removed the warning message.
Regards,
Brian.