[Genma Saotome]

Peter, many thanks for digging into this topic.

WRT r0(), a couple of questions:

• If x is the position of the coupler at rest is it a safe assumption that is where the model shows the coupler -- hence a value of zero?
  
• If y is the maximum travel allowed does the program treat it as a plus/minus range?

IIRC Damping() was used in MSTS to create a spring effect (sometimes people used values that created a too lively spring that would never settle down). Might you take a bit of time and experiment with that? It might be quite relevant to the larger train forces topic w/ specific regard to run-in forces.

Last, what's the purpose of Buffers() and is that used in OR??

[steamer_ctn]

Genma Saotome, on 26 August 2018 - 09:57 AM, said:

If x is the position of the coupler at rest is it a safe assumption that is where the model shows the coupler -- hence a value of zero?

Setting x at zero is what I believe is the ideal setting. However it will depend upon how the modeller has defined the model in the size statement, etc. For example, depending upon the coupler type, it may need to extend beyond the wagon shape a bit.

So some experimentation will be required.

Genma Saotome, on 26 August 2018 - 09:57 AM, said:

If y is the maximum travel allowed does the program treat it as a plus/minus range?

Yes.

The one challenge that I see, will be that the coupler does not actually move with slack movement (independent of the cars), and hence depending upon the current amount of slack, the couplers of two cars may either overlap, or have a gap between them.

Genma Saotome, on 26 August 2018 - 09:57 AM, said:

IIRC Damping() was used in MSTS to create a spring effect (sometimes people used values that created a too lively spring that would never settle down). Might you take a bit of time and experiment with that? It might be quite relevant to the larger train forces topic w/ specific regard to run-in forces.

Currently the Damping parameter are not read and used by OR.

As far as doing any major changes to the coupling code, I am not inclined at this moment to do so, as I don't fully understand the logic used in it. I have attempted to seek clarification from the original developer to understand the model that they have defined, so we will see what happens.

Genma Saotome, on 26 August 2018 - 09:57 AM, said:

Last, what's the purpose of Buffers() and is that used in OR??

Buffers were not used in MSTS (according to the MSTS Docs) and are not used in OR.

As I understand it, couplers have two states, ie tension (pulling) and compression (pushing). I would suspect that the behaviour would be different in each coupler state, and that the buffers would more influence the compression state. At the moment OR appears to treat both states the same, with one being a positive state and the other being a negative state.

[Genma Saotome]

steamer_ctn, on 23 August 2018 - 08:57 PM, said:

In Appendix A of this document are some examples of typical Coupler Forces.

This fails to open correctly for me (I see pages 1 and 2 but the rest never display).

[mbm_OR]

Now Locomotive information is ready.
About, Brake Information, it remains a job in progress.

Some screenshots about Locomotive information:
All locomotives.

Diesel loco.

Steam loco Car 3.

Steam loco Car 5.

Page right scroll.


Attached test file for x4185.
31/08/2018. Deleted, by new code.

Regards,
Mauricio.

[Genma Saotome]

I tried V4185 a few minutes ago, a simple test on level ground of a reverse movement to take up the slack, around 60 cars. I allowed the locomotives to move for about 5 seconds and then throttled down.

What I noticed was the coupler force bounced from zero to 12k fpds (a bit more than 16kN) on some cars; most were around 7-8k fpds (9.5kN - 10,kN) and back again on all cars. I watched this for about 2 minutes and there was an almost imperceptible movement back and forth in the cars for the entire time.

From a game performance issue there were a lot of unnecessary calculations going on as the train speed was zero. I suppose at zero speed extra calculations are a don't care. From a user point of view it's very likely to also be a non-issue (assuming your r0() values are tight)... it you don't look carefully you won't notice the cars moving back and forth. OTOH, if your r0() values are not tight (e.g. cushioned underframe cars) the back and forth could be very noticeable.

From a physics point of view, clearly the damping function isn't there (we all knew this beforehand).

Obviously real railroad cars do stop... the question I suppose then is this: Is there a simple, temporary solution that can be implemented until such time Damping() is properly figured out and coded? Something effectively akin to a calculus limit, perhaps tied to low speed, perhaps tied to low force?

Q: Does positive rolling resistance have an effect upon push-in coupler forces? Does it take into account the effect of no slack in the attached car(s) located in the direction of the push?

[hroch]

Mauricio

about locomotive information:
When the 1280x1024 resolution at the diesel locomotive is not displayed value of flow.
normal screen


page right


When the 1024x768 resolution at the diesel locomotive is not displayed value of load
normal screen

page right


When resolution is 1280x1024 at the steam locomotive does not move the line at a fire.


When resolution is 1024x768 at the steam locomotive does not move the line at a Status and is not displayed value of Combust.
normal screen

page right


When resolution is 1024x768 at the electric locomotive does not work move.
page right

[mbm_OR]

Thanks for your detailed feedback.

hroch, on 31 August 2018 - 02:06 AM, said:

When the 1280x1024 resolution at the diesel locomotive is not displayed value of flow.

Please, try the attached new code.

hroch, on 31 August 2018 - 02:06 AM, said:

When resolution is 1280x1024 at the steam locomotive does not move the line at a fire.

I have noticed that with the same display resolution, there are different amounts of data displayed.
In the steam locomotive information, there are more sections displayed in your screenshots.
Normal:


First page right:


Second page right:



Maybe, the font text used is different. I need to take a look.

Attached test file for x4185.

19/10/2018. Deleted, by new code.

[steamer_ctn]

mbm_OR, on 31 August 2018 - 11:00 AM, said:

I have noticed that with the same display resolution, there are different amounts of data displayed.
In the steam locomotive information, there are more sections displayed in your screenshots.

Depending upon the type of steam locomotive some additional data might be displayed.

For example, a compound locomotive will have two lines of steam cylinder pressures, ie the high and low cylinder pressure, whereas for a simple locomotive normally on one line of information is displayed.

Genma Saotome, on 30 August 2018 - 09:04 AM, said:

Q: Does positive rolling resistance have an effect upon push-in coupler forces? Does it take into account the effect of no slack in the attached car(s) located in the direction of the push?

I am not 100% sure what is meant by the question, however I think the answer is yes to both questions.

[mbm_OR]

steamer_ctn, on 31 August 2018 - 10:24 PM, said:

Depending upon the type of steam locomotive some additional data might be displayed.

Thanks Peter.
That is already taken into account by the code. The different steam locomotive data it's taken from the current Getstatus() code. The steam locomotive data are only formatted, not modified, by lines and columns according to the selected display resolution.

But, if we compare the same steam locomotive, with the identical screen resolution, the information, which fits on the hroch screenshots and mine, is different.
I suppose it could be an issue related to the type of text font used.

Regards,
Mauricio

[Coolhand101]

steamer_ctn, on 09 August 2018 - 12:14 AM, said:

With OR release #4168, wind resistance has been added.

I have just updated OR to x4185.

Using this feature, my EMU trains struggle to get pass 75mph on the level. The level balancing speed is 82mph. I have notice that the wind resistance is very high on certain coaches, namely the motor coaches. All the coaches have the same size but slightly difference mass.

My default EMU consist has this setup:

ENG+ENG+WAG+ENG.

If i use this test setup using the same mass and size as my default consist:

ENG+WAG+WAG+WAG

My EMU can get to 81-83mph on the level, depending on the wind strength and direction.

It appears the wind resistance is greatly enhanced if the consist has more than one engine, irrespectively of their size parameters.

Obviously these are my initial findings, so would the "ORTSWagonFrontalArea" and "ORTSDavisDragConstant" for my default consist that uses more than one engine, make the performance on par to my test consist?

I cannot seem to find any example setups on these two wind resistance parameters!

Thanks