Elvas Tower: Cannot parse the constant number. - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Cannot parse the constant number. Warning message appeared between 4022 and 4032. Rate Topic: -----

#1 User is offline   Brian Hook 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 29
  • Joined: 31-January 13
  • Simulator:ORTS
  • Country:

Posted 16 March 2018 - 02:52 AM

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.

Attached File  OpenRailsLog 4022.zip (4.83K)
Number of downloads: 308
Attached File  OpenRailsLog 4032.zip (5.28K)
Number of downloads: 300

#2 User is offline   eugenR 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 472
  • Joined: 15-April 13
  • Gender:Male
  • Simulator:MSTS
  • Country:

Posted 16 March 2018 - 07:00 AM

View PostBrian 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.

Attachment OpenRailsLog 4022.zip
Attachment 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

#3 User is offline   Brian Hook 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 29
  • Joined: 31-January 13
  • Simulator:ORTS
  • Country:

Posted 16 March 2018 - 09:32 AM

View PosteugenR, 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.

#4 User is offline   steamer_ctn 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 1,879
  • Joined: 24-June 11
  • Gender:Male
  • Country:

Posted 18 March 2018 - 09:04 PM

View PosteugenR, 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.

#5 User is offline   Brian Hook 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 29
  • Joined: 31-January 13
  • Simulator:ORTS
  • Country:

Posted 19 March 2018 - 02:01 AM

View Poststeamer_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.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users