Thanks but I am still confused.
When I run the "NewYear_MG" version, I get an "OpenRails" tab in the "Options" menu and can control the loco from the RailDriver unit. I set all of this up several months ago.
When I run the "Stable", "Testing" and "Unstable" versions, I do not get access to the "OpenRails" tab in "Options" and can only control the loco from the RailDriver unit when I follow the procedure detailed in the Open Rails manual.
Is this how it should be? I am using the latest versions available for all of the four versions of Open Rails.
Raildriver adoption
#52
Posted 06 August 2021 - 10:25 AM
dforrest, on 06 August 2021 - 06:38 AM, said:
Thanks but I am still confused.
When I run the "NewYear_MG" version, I get an "OpenRails" tab in the "Options" menu and can control the loco from the RailDriver unit. I set all of this up several months ago.
When I run the "Stable", "Testing" and "Unstable" versions, I do not get access to the "OpenRails" tab in "Options" and can only control the loco from the RailDriver unit when I follow the procedure detailed in the Open Rails manual.
Is this how it should be? I am using the latest versions available for all of the four versions of Open Rails.
When I run the "NewYear_MG" version, I get an "OpenRails" tab in the "Options" menu and can control the loco from the RailDriver unit. I set all of this up several months ago.
When I run the "Stable", "Testing" and "Unstable" versions, I do not get access to the "OpenRails" tab in "Options" and can only control the loco from the RailDriver unit when I follow the procedure detailed in the Open Rails manual.
Is this how it should be? I am using the latest versions available for all of the four versions of Open Rails.
your observations properly reflect the current status
#53
Posted 08 August 2021 - 05:05 AM
#54
Posted 11 August 2021 - 10:17 AM
Main branch versions ("Stable"/"Testing"/"Unstable") still implement the original method of calibrating the RailDriver, which also uses fixed/non-user-assignable key mappings on the the buttons. The Open Rails documentation describes how to use the RailDriver's original calibration tool to generate a calibration file so it will work in Open Rails.
The "forked" versions ("OR_NewYear_MG" and "Ultimate") have the updated RailDriver calibration and button assignments in a tab of the OR "Options" menu as long as the RailDriver is plugged in when Open Rails starts.
That's probably the easiest way to explain the difference.
The "forked" versions ("OR_NewYear_MG" and "Ultimate") have the updated RailDriver calibration and button assignments in a tab of the OR "Options" menu as long as the RailDriver is plugged in when Open Rails starts.
That's probably the easiest way to explain the difference.
#55
Posted 11 August 2021 - 10:40 AM
Understood. Any my question. "Is this how it will remain, or are there plans to use the version currently available with "NewYear_MG", with all versions?"
#56
Posted 11 August 2021 - 10:21 PM
There are not yet any concrete plans to improve Raildriver support in the mainline branch, but I am interested in investigating it after Open Rails 1.4 is released.
#57
Posted 13 September 2021 - 01:35 PM
From two friends who thank you very much for the program that has made the Rail Driver work perfectly in the New Year.
greetings
Pedro
greetings
Pedro