[NickonWheels]

And seemingly the same registration issues are in place at launchpad.net (not accepting any password).

Bad luck I guess...

[cjakeman]

Hi NickonWheels,

 NickonWheels, on 08 June 2020 - 09:15 PM, said:

And seemingly the same registration issues are in place at launchpad.net (not accepting any password).

Just tried it out and had problems too trying to create a new account.

If you send me the details for the blueprint, then I'll add it for you.

[NickonWheels]

 cjakeman, on 15 June 2020 - 10:03 AM, said:

Just tried it out and had problems too trying to create a new account.

If you send me the details for the blueprint, then I'll add it for you.

What blueprint do you mean? The MSTSWagon.cs uploaded here before is still the same.

I also deleted my first broken account on Launchpad and will try it again.

[cjakeman]

 NickonWheels, on 15 June 2020 - 11:25 AM, said:

What blueprint do you mean? The MSTSWagon.cs uploaded here before is still the same.

I've added a blueprint called Parameters to adjust friction at low or no speed and included that as a link in the Pull Request.

The purpose of a Blueprint is to:

• summarise what the feature is going to achieve
• to provide a form to record the status and progress of the work

[NickonWheels]

Thanks, Chris

In order to make future code changes/blueprints myself is there anything noteworthy if I could finally get on Launchpad? At this point I only know that code lines have to be added and/or deleted somewhere. I´m just asking because with this code extension it works only for static weights and I always wanted to try it with dynamic weights too.

Also I just found out ORTSMergeSpeed works with kph/mph prefixes as well... awesome

[YoRyan]

NickOnWheels, your feature has been mainlined and will be available starting from tomorrow's testing release. B)

I've modified your code substantially, so if you intend to add support for dynamic weights, you should obtain a new copy of the Open Rails source code and start from there.

As for Launchpad and GitHub, here's the general rundown on code changes:

• File a bug report or blueprint on Launchpad
  
• File a pull request on GitHub, containing:
  
  • Your code changes
    
  • A manual update with a description of your new feature

[NickonWheels]

Thanks for your advice, Ryan. But do you really mean testing release, not unstable?

[YoRyan]

Yes, I do. The one that builds every Friday and can be selected as an update channel.

[NickonWheels]

I know but lastly I´m switching randomly between them to hopefully get something that is not truly unstable (because ORTS crashes alarmingly often for some time, but maybe my computer just has a heat problem and shuts down automaticly)

I just tried U2020.06.18-1751 and the extension is already in it... AWESOME!

[Lamplighter]

Hi,
I have a few questions for this solution:
I can't find anywhere how the values ​​of the ORTSStandstillF (force) and ORTSMergeSpeed ​​(speed) parameters are determined (or calculated).
I overlooked something?

In the example of the Dash 9 locomotive, low torque bearings are defined at the same time as the higher starting resistance ORTSStandstillFriction.
ORTSDavis_A ( 1842.82 )
ORTSDavis_B ( 42.2945 )
ORTSDavis_C ( 7.705134 )
ORTSStandstillFriction ( 3400 ) <-----
ORTSMergeSpeed ( 0.869698 )
ORTSBearingType ( Low ) <-------
It's alright? Does the Dash 9 locomotive really have this type of bearing? I thought that the better the bearings, the easier the start. But in the example, the initial resistance is artificially difficult.