DirectX 10 was a complete rewrite, throwing out a lot of legacy code in order to improve performance and efficiency.
Adding to that, modern GPUs and drivers tend to focus on the more modern APIs, features and techniques when optimising performance, sometimes sacrificing the legacy stuff (which they can largely brute force in older games). They are now pixel/vertex shader machines.
Both of these probably contributed to the improved performance somewhat.
DX10+ is also able to handle multiple threads better, which has the potential to reduce the reliance on a single, fast CPU core.
Your in-game name: [TC-R] Elmo
Protested driver's in-game name: M@CI3K
Session: Race
Lap: 6
Timecode of the incident: 00:08:23
A brief explanation about the incident:
I was hit from behind when pulling into the first pit stall, which caused be to spin and lose just over 4 seconds. This cost me 2 places (I would have crossed the pit-exit SC line right behind Jeff, based on time loss).
M@CI3K didn't brake at all and only lifted off throttle briefly as contact was made.
I still haven't got around to customising the button range for TCLights, however there shouldn't be any buttons drawn except when the menu is open (unless you have the HUD enabled).
It's possible that Lazy is trying to update the lights status text of a button which TCLights has deleted (ie when closing the menu)?
If you have the TCLights HUD on, try turning it off.
If TCLights HUD is off, does it still happen if you haven't opened a TCLights menu since last starting Lazy & LFS?
Edit: Looks like I was ninja'd. May still be useful for others to troubleshoot though.