Delay in Updating Outside Views

[PeterB]

Not always, but sometimes when switching from cabview to outside train rear view (3 key), or vice -versa; even when switching from front outside view (2 key) to rear view (or vice-versa), there is sometimes a delay of up to around 5 seconds or so for the new view to be fully rendered (train and landscape).

I have two SSD's, with the Operating System on one SSD, and with MSTS and ORTS on the other SSD.

CPU is i5-13600K at stock frequency (3.5 GHz).
64 GB of RAM at stock frequency (2.8 GHz).
Video card RTX-4060 at stock frequencies (core 650 MHz, memory 2.4 GHz).

I thought with my computer setup that scene draws/rendering would not take so long while running MSTS/ORTS(?)

Comments?

[PeterB]

Bump!

Hasn't anyone else experienced around 5 (or more) second delay in updating video display when switching (outside) views for (long) trains? Or am I the only one experiencing this issue?

I sort of expect slight delay in updating views particularly with long trains as there is more data to process. But 5 or more seconds to update the video display seems to me to be taking a bit too long considering I'm using a reasonably quick computer setup for running the simulation, I would have thought.

[niknak]

For what it's worth I've never personally experienced such a delay.

[PeterB]

Thanks for the comment.

Frankly, I'm puzzled as to why I'm getting relatively slow scene (re)draws when switching from one and of the train to the other end of the train.

Most of the time when changing views from where ever to where ever, there is usually a delay of maybe 1 or 2 seconds before the entire scene is fully rendered. Usually I see just the lead locomotive first with some of the scenery, then the delay of 1 or 2 seconds before the rest of the train and the rest of the scenery is rendered fully. This often applies to the outside view via the 4 key.

But on some occasions, and particularly for long trains (well in excess of 100 cars), there may be a longer delay (5 seconds or more) before new scenes are fully rendered. This often occurs when switching views from one end of the train to the other end.

Tried running an activity with 249 cars and 6 locomotives under Monogame version of Open Rails. The rendering time took literally 20+ seconds before the change in scenery was fully rendered by switching from cabview to the rear of the train (3 key)!?

This delay in (re)drawing scenes is about as bad as my old computer with HDD's only (no SSD's) and with a slightly lower spec video card and slightly lower spec CPU!?

I'm beginning to wonder whether there is something wrong with my new computer because of the relatively poor rendering rate for Open Rails activities?

[crstagg]

Can you stop griping long enough to upload the Log file from the run with 249 and 6? Perhaps we could spot a setting that causes this.

[superheatedsteam]

Bump!

Hasn't anyone else experienced around 5 (or more) second delay in updating video display when switching (outside) views for (long) trains? Or am I the only one experiencing this issue?

Yes, I experience this as well, 6 seconds when the end of train is 4.2km from the head end and 2 seconds when the the end of train is 3.8km away. This is with viewing distance in OR set to 2km. With viewing distance in OR set to 5km there change is almost instant.

Try increasing your viewing distance in OR and see if that helps.

[PeterB]

Can you stop griping long enough to upload the Log file from the run with 249 and 6? Perhaps we could spot a setting that causes this.

Next time ask more politely please!!

Running the long train under Open Rails version 1.5.1 stable.

A couple or so delays up to around 6 seconds for full screen rendering were noted when automatically following the train via the outside view (4 key).

Latest log attached, but I doubt it will help.

OpenRailsLog.txt

[PeterB]

Yes, I experience this as well, 6 seconds when the end of train is 4.2km from the head end and 2 seconds when the the end of train is 3.8km away. This is with viewing distance in OR set to 2km. With viewing distance in OR set to 5km there change is almost instant.

Try increasing your viewing distance in OR and see if that helps.

Thanks for your constructive comment!

It is very late here and I'm about to go to bed. I'll try your suggestion a bit later.

Thanks.

EDIT: Your tip works!

In Open Rails, I set the Video distance from 2000 m to 5000 m, and now the train views change about instantly! Much better!

I'm speculating that with shorter video distance at 2000 m, only video data up to 2000 m is stored in the video card memory. If changing views where the video distance is greater than 2000 m, then the video card requests further data (beyond 2000 m) via the CPU from the SSD with the current route video data. This data request takes a bit more time to complete before video data is available to the video card to then display the data. Hence the delays in displaying the new view which as mentioned before can take some seconds before complete video data is displayed.

With the video distance set at 5000 m (well beyond the length of most trains), then the train and scenery data is already stored in the video card memory for immediate access when required. There is no need for the video card to request further data, and in this case as the data is already within its memory and accessing data from video card memory is much faster, so the video data is displayed just about instantly.

Very good tip! Thanks again!!