A little time digging - Flickering problem
Posted: Sun Dec 11, 2011 7:42 pm
Has anyone ever been running railworks when suddenly, the controls for the loco/train you are driving, lock-up and the cab view starts to flicker rapidly?... This happened to me recently so I started digging into the problem, bearing in mind that this may happen even when you are running at a steady 25-30fps.
I have now been able to recreate the issue on demand through a bit of scenario creation and have saved a screenshot of the performance from my MSI GTX 560N graphics card (see below).

(this is a screenshot taken after having passed through the station with extremly high levels of AI and custom scenario scenery)
During the test Railworks was running at 30fps along an unpopulated section of the WCML (south of Carstairs). The closer my train got to the station at Carstairs the worse the issue got. Now this is not to say that there is a problem with the WCML North route. Far from it. Let me be clear in that I believe this issue has more in the way to do with tile loading than any other issue. On the left side of the image (highlighted in the box in orange) is the Memory usage of my graphics card. Flickering and control lockups seem to occur when railworks loads tiles, resulting in a huge 'jump' up in memory usage. The flickering issue will then disappear once the tile information is dumped by the game engine.
Now the strange thing is that when driving through highly populated sections of the route, i.e. Motherwell and Glasgow, I cannot see this issue repeat itself. Upon reviewing the logs from my graphics card there is no big leap in memory usage, just a steady increase over a few minutes. So it seems like the control lockup/flickering issue is caused as a result of big jumps in my GPU's memory usage. (GPU load and processor load both remain stable throughout the test).
Has anyone else came to the same conclusion???
regards
chris
I have now been able to recreate the issue on demand through a bit of scenario creation and have saved a screenshot of the performance from my MSI GTX 560N graphics card (see below).

(this is a screenshot taken after having passed through the station with extremly high levels of AI and custom scenario scenery)
During the test Railworks was running at 30fps along an unpopulated section of the WCML (south of Carstairs). The closer my train got to the station at Carstairs the worse the issue got. Now this is not to say that there is a problem with the WCML North route. Far from it. Let me be clear in that I believe this issue has more in the way to do with tile loading than any other issue. On the left side of the image (highlighted in the box in orange) is the Memory usage of my graphics card. Flickering and control lockups seem to occur when railworks loads tiles, resulting in a huge 'jump' up in memory usage. The flickering issue will then disappear once the tile information is dumped by the game engine.
Now the strange thing is that when driving through highly populated sections of the route, i.e. Motherwell and Glasgow, I cannot see this issue repeat itself. Upon reviewing the logs from my graphics card there is no big leap in memory usage, just a steady increase over a few minutes. So it seems like the control lockup/flickering issue is caused as a result of big jumps in my GPU's memory usage. (GPU load and processor load both remain stable throughout the test).
Has anyone else came to the same conclusion???
regards
chris