Blur Busters Forums

so i been using the launcher command -threads 4 all this time, yes it gives me around the 280 fps but then i switched to -1threads 1 and it feels like less input lag[maybe placebo] and i get less fps to around 240 but its not really a problem ...
so it is placebo or not? =o

maybe, ill figure out soon enough but like most things in life it doesn't really matter

I liked that reply. Will keep an eye on your tests.

Anyway, multithreaded rendering must cause frametime variance in order to overcome inherent latency ("This is because multithreaded rendering has to synchronize with the GPU and render thread to avoid latency that can happen when the GPU or driver allows too many frames to be buffered." Jay Stelly, Valve). But according to their own statements, most multithreaded implementations in games are not coded with modern multicore processors in mind (CS:GO uses the more than a decade old Source engine) and are lacking for that reason.
The implementations probably are compromising between allowing certain pre-buffer ranges (latency) in order to achieve more consistent render timings (frametimes) and higher framerates.

I did tests with multicore rendering and the increased FPS from multicore didn't decrease input lag. It didn't really add any input lag though, it pretty much just stayed the same.

Are you sure stating the game to use 1 thread in steam options disables multithreading. If it only changes affinity for the program it might still be using multithreading. Why? Well even single core processors can run multiple threads. I thought source games had a specific config option to disable multicore rendering.

Trip wrote:I thought source games had a specific config option to disable multicore rendering.

It does have that option. It's called "multicore rendering" in the video settings The "-threads" option just controls the amount of threads used IF the "multicore rendering" option is enabled in-game.

honestly imo the source engine and csgo suck (as in technically) and nothing really matters as long as you get >200fps

flood wrote:honestly imo the source engine and csgo suck (as in technically) and nothing really matters as long as you get >200fps

I'm not sure about that. CSGO and also all previous CS games felt best to me. The controls feels immediate and responsive.

The other FPS games I played, CoD or Battlefield, you name it, feel like a boat. Even with v-sync at 60Hz enabled, CSGO feels great. Battlefield with v-sync... oh my god. I puked.

I don't know what it is they're doing in the CS games, but they are doing it right. Even other games that use the Source engine feel horrible. Like Insurgency or Fistful of frags. They feel sluggish as hell. CS: nope. Responsive like a dream.

idk i think quake and cs1.6 are way smoother than csgo
probably something to do with the fixed framerate

flood wrote:idk i think quake and cs1.6 are way smoother than csgo
probably something to do with the fixed framerate

Can't you just use the fps command to set a max frame rate?