|
|
|
Member 150 posts
Registered: Nov 2006
typing "show net" / "r_netstats 1" i get this result. With that option from Nvidia CP AUTO, i get 0% Bad delta. Does this affects anything ?
Administrator 1025 posts
Registered: Apr 2006
Ah so that's why I'm getting 100% bad delta, would be nice to get an answer from someone who knows .
Member 485 posts
Registered: Feb 2006
It means delta compression is failing? Which means net packets are bigger. Which can mean higher ping, depending on connection. You can toggle it with cl_nodelta.
Member 150 posts
Registered: Nov 2006
On that network statistics board shows the size of packets IN and OUT, inspite of the 100% Bad Delta the IN packets have same size when i have Threaded Optimization AUTO, having 0% Bad Delta. So i guess compression is not failing. If i set cl_nodelta 1, the IN packets increase alot.
Moderator 1329 posts
Registered: Apr 2006
I tried this settings using threaded optimization: auto and I don't see anything problematic. All four packet loss indicators give me 0% and packet sizes are ~1400 (total 2800) and when I turn cl_nodelta 1 it states "no delta compr" and the in stat goes to 3100 from 1400.
The better question is, why should (or would) threaded optimization of drivers affect packet loss?
Member 150 posts
Registered: Nov 2006
I dont know, i think it shouldnt. But since fog happens same thing i guess its not a my computer thing. How can i post an image so i can show you ? Ah Renzo, you said you tried it AUTO. Did you try it OFF ? bad delta happens to me when its OFF.
Moderator 1329 posts
Registered: Apr 2006
Nope, optimization=off affects only fps to me. It still shows me 0% on all packet loss indicators, however I lose ~100fps if I disable threaded optimization.
To check whether it really works just use cl_maxfps 0 and check cpu usage in the task manager, if cpu% is >50% on dual core system then threaded optimization is enabled and if it's only 50% at max then it's disabled.
Member 150 posts
Registered: Nov 2006
When set to AUTO cpu% = 90, OFF = 49/50. With timedemo i have alot more fps with it set AUTO, so i think its working ok. You have linux ? maybe its a windows related issue ?
Moderator 1329 posts
Registered: Apr 2006
XP 32bit/sp3, I think it's some system wide configuration mishap or something related to drivers otherwise.
Member 150 posts
Registered: Nov 2006
I'm using ForceWare 175.16 with XP 32bit/SP3. Could be drivers version? Fog: what system and drivers you have ?
Administrator 1025 posts
Registered: Apr 2006
Using driver 169.21 with my 7900GTO/GTX on Windows Server 2008, Core 2 Duo E6300.
And I get 100% bad delta with Threaded optimization off/auto, but with it On i get 0% bad delta..
Member 150 posts
Registered: Nov 2006
Renzo, are you using scr_newhud 0 ? And you Fog ? If i set scr_newhud 0 i get 0% Bad Delta with Threaded Optimization OFF. Now, i don't know if the new hud just can't read data, or actually is getting Bad Delta.
Member 150 posts
Registered: Nov 2006
I do not know why i even bother...
Member 116 posts
Registered: Mar 2008
hmm This is a known problem on either AMD x2 processors or NV drivers on SMP systems.
The problem SHOULD be resoveld by installing http://www.amd.com/us-en/assets/content … er_113.zip and if that doesn't help turn off the threaded optimization from NVIDIA control panel (or you could first try this). http://www.quakeworld.nu/forum/viewtopic.php?id=3083 not sure if that is related. but that guy had a dual core CPU too with Nvidia video card.
Moderator 1329 posts
Registered: Apr 2006
AMD specific fixes shouldn't be used with Intel hardware (mostly because they don't work), hopefully you didn't mean that but something else.
Member 116 posts
Registered: Mar 2008
sorry my bad, I should have realized that was intel cpu
|
|
|
|