A couple of observations......

[cjakeman]

Hi Bruce,

If the fault doesn't initiate when in the ahead view, it will when looking out one or the other side windows.

You are the first I've met to report such strange behaviour, so that makes it especially intriguing.

Does this have any similarity to this recent Elvas Tower report here?

Is there a sequence which always produces the problem? E.g. starting from initial cab view, Up, left, down, right?
What is your screen height and width in pixels?

[seagoon]

Hi Bruce,

You are the first I've met to report such strange behaviour, so that makes it especially intriguing.

Does this have any similarity to....this recent Elvas Tower report here?

Yes, most definitely, Chris.
I'm not a member of that forum so cannot view the images but the description is definitely similar.

Is there a sequence which always produces the problem? E.g. starting from initial cab view, Up, left, down, right?
What is your screen height and width in pixels?

Chris, I'll check if it only occurs when I follow my regular opening sequence or otherwise.
I always start in the View 2 position (that must be the OR default, I assume) and then I manually go to view 1 (in-cab, ahead) to set lights, brakes, direction etc. Once the brakes are releasing and I'm waiting for them to completely release I usually go to the external view 3 to zoom out slightly, then 4 to make sure the lights are okay and then back to the cab for head-out Home and End, to swing the LH view around from rearward to ahead.
Then back into the cab.

I'll see what happens if I change my sequence.

Also, my screen size is 1366 x 768.
Operating system is W7 Home.
PC is Toshiba Satellite i7 Dual and GeForce Cuda graphics.

Regards,
Bruce

[seagoon]

Chris,
The only definite thing to report is that there is no consistency whatsoever.
It doesn't matter what sequence I follow, the type of locomotive or the route.
Some locos do it when looking out all three cabviews, others only do it when looking out the RH or LH window.
It is consisent on OR v8 and OR X1413.
There is no difference between stretched window 100% or 0%.

The only odd thing that I've seen in all of this is that in the cab of a Little Joe on the MILW RMD_East route this does NOT happen.....well, so far, anyway!
The view just goes up and down as it is supposed to and doesn't venture beyond those points.

Bruce

[cjakeman]

I'm not a member of that forum so cannot view the images but the description is definitely similar.

That forum is open to all; just need to register. I'm repeating the images here - expected view and actual view.

expected_cabview.jpg

actual_cabview.jpg

I always start in the View 2 position (that must be the OR default, I assume) and then I manually go to view 1 (in-cab, ahead) to set lights, brakes, direction etc. Once the brakes are releasing and I'm waiting for them to completely release I usually go to the external view 3 to zoom out slightly, then 4 to make sure the lights are okay and then back to the cab for head-out Home and End, to swing the LH view around from rearward to ahead.
Then back into the cab.

Useful information, Bruce. Thanks.

I'll try to look into it at the weekend. May need to post a version with diagnostics.

Best wishes,

Chris
OR Dev

[seagoon]

Thanks, Chris.
I hope it helps you to come up with a solution.

Bruce

[cjakeman]

I hope it helps you to come up with a solution.

I found a definite bug which I've fixed in v1430.

Please give it a try and let me know whether it's all better or not.

Best wishes,

Chris
OR Dev

[seagoon]

I found a definite bug which I've fixed in v1430.

Please give it a try and let me know whether it's all better or not.

Best wishes,

Chris
OR Dev

Chris, the latest X is showing as X1427.
No mention of the version to which you refer.

Regards,
Bruce

[cjakeman]

Chris, the latest X is showing as X1427.
No mention of the version to which you refer.

We're on a weekly update cycle so it will come through soon.

In the meantime, you can grab just the executable RunActivity.exe here.

Please let me know the outcome,

Chris
OR Dev

[seagoon]

Please let me know the outcome,

Chris
OR Dev

Chris,
I'm sorry to have to report that there is no difference.
The very first route I went into - selected at random - was the MLT "Willamette Pass" route and their default locomotives.
The anomaly was still there in all three cab views; up and down arrows inclined the views skywards and groundwards.

Bruce

[baldwin]

I dont know what you have wrong there, but I am unable to replicate that on the Willemette Pass with the MLT locomotives. Up and Down arrows have no effect in the cab, only left and right.

Using X 1427.

EDIT.
Went back for a more detailed look. The Up/Down arrow keys only work in the right view and do alter the view angle. This angle is then apparent in the conductor view with the driver view being either higher or lower but looking straight ahead. The viewpoint can be returned by going back to the right view and reversing the keypress. Movement is very slow so this is able to be fine tuned.

Changing to the runactivity.exe in post #23 has cured that for me. No up/down movement of the eyepoint.

[seagoon]

EDIT.
Went back for a more detailed look. The Up/Down arrow keys only work in the right view and do alter the view angle. This angle is then apparent in the conductor view with the driver view being either higher or lower but looking straight ahead. The viewpoint can be returned by going back to the right view and reversing the keypress. Movement is very slow so this is able to be fine tuned.....

That is exactly what happens for me in ALL three versions that I have - v0.8, X1413 and X1427.

EDIT:
And also X1430

The glitch occurs with a range of different creators & locos - MLT, Streamlines, NALW, even the default MSTS Dash 9s and GP38s.
It happens on a variety of routes - Willamette, Scenic Sub, Pocahontas, Green River, Soldier Summit......all over the place.
In some cases it only happens when viewing through the RH window, in others when viewing through the LH window and in others it happens when viewing out of any window.

As I've mentioned previously, the only consistant note is the inconsistency!

Bruce

Bruce

[cjakeman]

Hi Bruce,

That is exactly what happens for me in ALL three versions that I have - v0.8, X1413 and X1427.

Please try v1430 as this is the version which contains the fix. You can download it from the link in post #23 below.

It worked for Baldwin and also for Knsgf who reported the similar problem at Elvas Tower.

Chris
OR Dev

[seagoon]

Hi Bruce,



Please try v1430 as this is the version which contains the fix. You can download it from the link in post #23 below.

It worked for Baldwin and also for Knsgf who reported the similar problem at Elvas Tower.

Chris
OR Dev

Chris,
Sorry....I should have referred to X1430 instead of X1427.

I did download that .EXE, overwrote the previous .EXE in that X-folder and ran it but the result is exactly as before.

Bruce

[baldwin]

Chris
The new Runactivity.exe is still reporting as 1427 which is the Open rails exe, not 1430.

[cjakeman]

Chris,
I did download that .EXE, overwrote the previous .EXE in that X-folder and ran it but the result is exactly as before.

Then you did the right thing, but I'm running out of ideas.

One thing that puzzles me is that you report the problem is still present when you return your settings to % 2D Cab Stretch = 100. But in that case, you don't need to use Up and Down arrows to use the cab.

Are you saying that you can trigger these problems without ever touching Up and Down keys?

Chris
OR Dev