Problem

[DrDeath]

idgamelocal::clientupdateview: timeleft = = usercmd_msec abort

OK, I have just installed i7 930 on x58 chipset and using win 7 64 bit . I have reinstalled etqw and I can get onto a server but have lots of graphics glitches and tearing tho fps is 250 . The console shows hundreds of the above line . It isn't firewall or compatability mode related . Google shows little . Any ideas . I was running on win 7 64 bit before on q6600 and different motherboard but all other hardware is the same .

[Trieb]

Not sure what it meant though I've read a thread in German about some-one who had the same issue.
IF you can call it an issue because it wont effect your game.
The error disappeared out of the blue suddenly in abt 2 days?
I have sometimes similar errors in the console, but that is if I go LeftAlt + Enter to window mode.
I wouldn't bother coz it sometime it's there......sometimes not.

[Bubba]

It looks like someone else had the issue with an i7 on the qw forums, but of course the forum is gone so doesn't help that much (thanks again activision!).

The only titbit I could gather is that is a problem with multicore functionality. I'm guessing

r_useThreadedRenderer

is set to 2 - try changing this to 0 (apparently there should be no issue with this anyway as a single modern core is easliy enough to handle qw).

Hope this helps :)

[DrDeath]

Yeah Bubba , I read the same thing but as you say , no forum , thanks activision. r_usethreadrenderer 1 or 0 fixes it and gets rid of the warning message but takes fps down to 60 . I will have to fiddle around and see , I have forgotten those fecking cvars as I have used the same autoexec more or less since beta .

[DrDeath]

So, fiddling done . Fixed !

com_unlockFPS 1
com_unlock_timingmethod 2
com_unlock_maxfps 300 :D :D :D
r_usethreadrenderer 2

Above now works . No issues with tearing etc . Getting average 250 fps in game :) I didn't have timingmethod and maxfps set in my autoconfig though they were set at 2 and 120 before . I think that increasing the com_unlock_maxfps did the trick and I wonder if that was the cause of my intermittent lag before .

Just to stroke my E-peen

i7 930 (new)
asus P6x58D premium (new, replaced asus striker extreme )
Corsair H50 cpu cooler (new, replaced thermalright 120)(fab piece of kit)
Corsair Hx 850w psu (new , replaced generic shit from pcworld as my seasonic 600w from 5 years ago blew up one day and I had to get one quickly)
Corsair Obsidian 800D case (New)(man it is huge and such a pleasure to use, tidiest build ever)
6GB patriot DDR3 1600 ram (new)
Sapphire ATI 4870 toxic (old , but still a cracker))
creative x-fi elite pro (old,had it 3 or 4 years now)
Samsung F3 1Tb HDD(old)
G9 mouse(old)
BenQ FP 241W(old, but still hard to beat )
Win 7 ultimate 64 bit (got cheaply for Euro 25 from MS employee so was able to splash on case)

Above running at 4Ghz , Prime95 stable (cpu 32-33 deg C idle, 68-69 deg C with prime95 8 threads 100% load)

E-peen stroking over

[ancient]

that error should only appear when you have the console open while starting a command while the server switches map. It should be harmless and can be ignored :)

[DrDeath]

Yeah, that error didn't cause any trouble, just it wasn't there before. Its now gone. The i7 issue was different and above fixed it.