Ran it through PIX Remote and the DX dev tools again last night. It is now clear to me that there is a huge delay in the timing loop.
The render calls come at even intervals. But every 1/6th or sometimed 2/6th frame is always delayed. This means that some logic is probably in the loop set to trigger at this interval. It is not fast enough to complete in time for the render call to be in sync.
As for what it is, dunno... You would need source code and PIX symbols to profile it better to find out and only Kunos can do that.
It's been noted as an issue in the past but dismissed and closed every time by Kunos.
So i am not holding my breath for that to happen...
It's a VERY good sim that is flawed by bad tech really...
Because as we know the jitter is not the only problems. It annoys ME the most but many people have other issues still with the core tech ,like the insane CPU stalling for some AI situations... Or the performance hit on AMD using DoF.
As i wrote earlier i was hoping to find fixes to the core rather than excessive content like more Italian hatchback road cars...
The render calls come at even intervals. But every 1/6th or sometimed 2/6th frame is always delayed. This means that some logic is probably in the loop set to trigger at this interval. It is not fast enough to complete in time for the render call to be in sync.
As for what it is, dunno... You would need source code and PIX symbols to profile it better to find out and only Kunos can do that.
It's been noted as an issue in the past but dismissed and closed every time by Kunos.
So i am not holding my breath for that to happen...
It's a VERY good sim that is flawed by bad tech really...
Because as we know the jitter is not the only problems. It annoys ME the most but many people have other issues still with the core tech ,like the insane CPU stalling for some AI situations... Or the performance hit on AMD using DoF.
As i wrote earlier i was hoping to find fixes to the core rather than excessive content like more Italian hatchback road cars...