cjakeman, on 24 July 2021 - 10:39 AM, said:
There has been mention of adding a legacy switch to provide enhanced compatibility with MSTS. This could move the setting from 100% to 130% and back again.
When I add functionality to the physics engine of OR I try to work to the following principles (guidelines):
i) Performance - the feature should ensure that the train performs "true to life", and add to the realism of the trains performance in OR. Ideally this should be confirmed against an appropriate railway test report.
ii) Consistency - the feature should operate in the same way regardless of which users PC it is run on.
Sadly I believe that the "Adhesion Correction Factor" breaks these two principles.
Firstly if we consider adhesion and its potential impact on trains in OR.
Typically most early generation diesels had adhesion values around 33%, whereas more modern diesels can have values around 45%. The current OR default value is set is 33%. So when we apply the 130% default value we are changing the OR default value to 42.9%.
So by applying a "global modifier" such as this we are potentially impacting the "true to life" performance of all the diesels operating in our scenario, as we are not allowing for individual performance of diesels, and in some instances we are setting the value artificially high.
In regards to the second principle (consistency), consider the following two scenarios, where the content creator is configuring a locomotive with a adhesion value of 42.9%:
Scenario 1 - If they have their PC set to the default value of 130%, and the user has their OR environment set to 100%, then the user may experience slippage whereas the content creator will not.
Scenario 2 - If the content creator uses 100% to develop the locomotive configuration, and the user has theirs set to 130%, then they will experience a different performance to the content creator.
Hence it appears that we both agree that the appropriate way for adhesion to be handled is for this global value to be fixed at 100%, and appropriate Curtius Kniffler adhesion parameters to be included in the individual ENG file.
However, based upon my observations, very few content creators appear to be setting the Curtius Kniffler adhesion parameters, and hence moving forward and setting this value back to what it should be (100%) I suspect that more users will experience wheel slip situations. Thus we need to consider the OR Depreciation Policy and Notification (by depreciation I mean how do we remove a parameter or feature from OR - this is often done in commercial software).
As an example, in this instance might be:
i) Version 1.4 - flag this function for removal (use bold red(?) text on the option menu and describe what is going to happen to it) and leave the current default of 130%. Place "sticky" notices in the key forums advising that change is going to happen. Contact any commercial content creators that we have a relationship with and advise them so that they can update any of their stock creations as appropriate. Set the default value of 100% in the unstable release once version 1.4 has been released.
ii) Version 1.5 - remove the global parameter and set the default correction factor to 100%.
In regard to the other two adhesion global parameters:
Adhesion proportional to rain/snow/fog - this should be set to permanently on in Advanced physics, and off in Simple physics. (Could be done in version 1.4)
Adhesion factor random change - this should only be available to be set when in Activity or Timetable mode. (Could be done in version 1.4)
cjakeman, on 24 July 2021 - 10:39 AM, said:
I agree with this approach.