RS Stutter returns......

[Makeone]

I had an interesting 'stutter' recently.

I downloaded a workshop scenario for woodhead, a heave coal drag from wath to manchester. When i loaded the scenario, it started almost with clear land, all i was able to see was the trains, soon after it loaded, very slowly though, the rest of the yard and route...looked almost unreal. Never had that sort of load stutter with RS/RW/TS's. Woodhead as other routes normally load without any problems, apart some class 77 scenarios for woodhead.

I have a decent machine and haven't defragged for ages.
i5-2400
8Gb(ytes)
Nvidia GTX660
Win 8 Pro

[smarty2]

have you checked for your disk being fragmented. You will probably find that though the files may not be too fragmented they may not be in the same area of the disk. This means that the heads have to move and then wait for the disk to be in the correct place. If its a slow disk then this will exacerbate the problem.

Thus when the next set of objects is loaded the disk goes into overdrive trying to get the file parts, but is too slow causing the stuttering.

I defrag my disk regularly with My Defrag, it isn't that that is causing this dreadful stutter as my non .ap file routes work as before even better than 2013 in fact.

Everytime i read this topic i just think about my own experience with "tile load lag" that i talked about elsewhere... it sounds like you are suffering the same thing

However, i see you have already posted in that topic - so would i be correct in assuming you have tried unzipping the .ap file (and repopulating all the empty folders with the original files) to see if it solves your problem?

Yes I tried it but made no difference at all.

[firstborn]

However, i see you have already posted in that topic - so would i be correct in assuming you have tried unzipping the .ap file (and repopulating all the empty folders with the original files) to see if it solves your problem?

Yes I tried it but made no difference at all.

That's weird, because once you have done that, the game shouldn't even be touching the .ap file anymore, which would imply that your problem is not with the .ap file but elsewhere

[PaulH2]

I had an interesting 'stutter' recently.

I downloaded a workshop scenario for woodhead, a heave coal drag from wath to manchester. When i loaded the scenario, it started almost with clear land, all i was able to see was the trains, soon after it loaded, very slowly though, the rest of the yard and route...looked almost unreal. Never had that sort of load stutter with RS/RW/TS's. Woodhead as other routes normally load without any problems, apart some class 77 scenarios for woodhead.

I have a decent machine and haven't defragged for ages.
i5-2400
8Gb(ytes)
Nvidia GTX660
Win 8 Pro

I experienced a very similar experience loading a scenario on the GEML route with the scenery appearing over something like 30 seconds after the scenario initially loaded. Likewise, I've never seen that before TS2014.

For the record, I have what is probably by modern standards a mid range system (Core 2 quad extreme edition, 8GB RAM, Radeon HD7970) but my storage solution is pretty good (the OS is on an SSD and TS2014 is on a 4 drive RAID 10 hardware array, so the stutter isn't hardware related).

I have reported the issue to RSC as the issue does not present itself with TS2013 in the same scenario (though as its a 3rd party scenario, I don't expect to get much traction).

[scefhwil]

I had an interesting 'stutter' recently.

I downloaded a workshop scenario for woodhead, a heave coal drag from wath to manchester. When i loaded the scenario, it started almost with clear land, all i was able to see was the trains, soon after it loaded, very slowly though, the rest of the yard and route...looked almost unreal. Never had that sort of load stutter with RS/RW/TS's. Woodhead as other routes normally load without any problems, apart some class 77 scenarios for woodhead.

I have a decent machine and haven't defragged for ages.
i5-2400
8Gb(ytes)
Nvidia GTX660
Win 8 Pro

This very slow scenery loading effect has been around for me for years, probably since the early days of Railworks, so it's not explicitly a new issue with TS2014. Of course something may have changed in the last update that makes it more likely to happen.

[firstborn]

I think, purely based on my own observations, that slow loading scenery at the start of a scenario, is caused by the driven loco being placed on the route a long distance from the scenario marker.... causing the game to need to jump across the map quickly, into an area where no scenery was loaded during the initial scenario load.

[ttjph]

This very slow scenery loading effect has been around for me for years, probably since the early days of Railworks, so it's not explicitly a new issue with TS2014. Of course something may have changed in the last update that makes it more likely to happen.

Likewise. I've seen this in WCML-N, and I haven't upgraded to 2014 yet.

[PaulH2]

This very slow scenery loading effect has been around for me for years, probably since the early days of Railworks, so it's not explicitly a new issue with TS2014. Of course something may have changed in the last update that makes it more likely to happen.

Likewise. I've seen this in WCML-N, and I haven't upgraded to 2014 yet.

Admittedly I've seen it (to a much lesser extent) once or twice over the years, but this is much worse, and it does it consistently on a scenario I had run a couple of times on TS2013 without that effect (and I defrag regularly, so I don't think that's the issue). So it may well not be a new effect, but at least for me it is much more pronounced in TS2014.