12-15-2008, 11:27 PM
With R2256 I committed a bunch of optimizations to try to speed up the framerate, especially on dense tracks with a lot of objects. Part of the optimizations traded CPU calculations for GPU calculations -- that is, less computation for the CPU but more for the GPU. On my system (AMD X2 3800+, geforce 7900GT) the framerate improvements were enormous; in Kyalami for example my framerate went from about 30 FPS to 100 FPS in one area I was using as a benchmark.
I'm curious if anyone sees a DECREASE in framerate with the optimizations in R2256. If you want to do a comparison, you can disable the optimizations by changing src/track.cpp line 862 to:
If the optimizations decrease anyone's performance I'll make it a display option; otherwise I'd rather not.
I'm curious if anyone sees a DECREASE in framerate with the optimizations in R2256. If you want to do a comparison, you can disable the optimizations by changing src/track.cpp line 862 to:
Code:
const bool optimize = false;
If the optimizations decrease anyone's performance I'll make it a display option; otherwise I'd rather not.