Lusciousdrunk Posted December 1, 2021 Posted December 1, 2021 Whenever I play, no matter what server I play on I always lag. I tried running the pk3 cleaner and changing things in my config and nothing has worked. If anyone has any suggestions on any way to improve this I would appreciate it. I found this config on the internet and this is what I’ve changed everything to. IMG_4054.MP4 1 Quote
Leader rambozo37 Posted December 2, 2021 Leader Posted December 2, 2021 hi! for sure com_zonemegs is to low. i have this and it runs smoothly seta com_zoneMegs "128" seta com_hunkMegs "512" Quote
Lusciousdrunk Posted December 2, 2021 Author Posted December 2, 2021 37 minutes ago, rambozo37 said: hi! for sure com_zonemegs is to low. i have this and it runs smoothly seta com_zoneMegs "128" seta com_hunkMegs "512" Thanks! I’ll try it out. Quote
Lusciousdrunk Posted December 2, 2021 Author Posted December 2, 2021 56 minutes ago, rambozo37 said: hi! for sure com_zonemegs is to low. i have this and it runs smoothly seta com_zoneMegs "128" seta com_hunkMegs "512" Did not seem to work. It’s almost unplayable on F|A 1 1 Quote
Lt Steiner Posted December 3, 2021 Posted December 3, 2021 (1) Do you have internet lag or a low and/or unstable framerate? (2) Do you have the problem in other games as well? Do they only occur in multiplayer or in singleplayer as well? (3) Type 'cmd' into the windows search bar to open the command line and type in "ping google.com -4 -n 100". Your PC will then ping a google.com server near to you 100 hundred times, using IPv4. What are the results? 1 1 Quote
Lusciousdrunk Posted December 3, 2021 Author Posted December 3, 2021 1 hour ago, Lt Steiner said: (1) Do you have internet lag or a low and/or unstable framerate? (2) Do you have the problem in other games as well? Do they only occur in multiplayer or in singleplayer as well? (3) Type 'cmd' into the windows search bar to open the command line and type in "ping google.com -4 -n 100". Your PC will then ping a google.com server near to you 100 hundred times, using IPv4. What are the results? 1) My guess would be internet lag. The game runs smoothly and I get these random spikes. Sometimes I'll get 3-4 spikes in a row. 2) My computer is only a month or so old so I haven't really had time to test out any other games. I played Counter Strike the other night and I noticed I lag there as well. Other than that I haven't done a whole lot of gaming on this computer yet. 3) Pinging google.com [142.250.190.78] with 32 bytes of data: Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=24ms TTL=115 Reply from 142.250.190.78: bytes=32 time=2750ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=57ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=27ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=41ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=44ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=42ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=25ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=52ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=23ms TTL=115 Reply from 142.250.190.78: bytes=32 time=32ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=24ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=38ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=24ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=37ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=41ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=330ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=35ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=28ms TTL=115 Reply from 142.250.190.78: bytes=32 time=29ms TTL=115 Reply from 142.250.190.78: bytes=32 time=22ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=25ms TTL=115 Reply from 142.250.190.78: bytes=32 time=28ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=29ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=21ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=19ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Reply from 142.250.190.78: bytes=32 time=20ms TTL=115 Ping statistics for 142.250.190.78: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 2750ms, Average = 53ms Quote
Lusciousdrunk Posted December 3, 2021 Author Posted December 3, 2021 (edited) Tried to post a video but I couldn't get it to work. Edited December 3, 2021 by Lusciousdrunk video doesn't work Quote
Lt Steiner Posted December 3, 2021 Posted December 3, 2021 (edited) 1 hour ago, Lusciousdrunk said: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 2750ms, Average = 53ms It looks like a connection issue. You have two very high spikes in a span of 100 seconds and 100 packets. What you can do: (1) Try to eliminate all potential sources of interference in your home network. If you use WiFi, try to switch to a channel that is less frequented by neighbors' routers. If multiple people use your home network, try to set up a priority for real time applications or for your PC in the QoS settings of your router, reducing the chance of running into buffer bloat because someone else in your household hogs up all the bandwidth. Alternatively you can also limit the available bandwidth to other users in your household. Sometimes the Windows WLAN background scanning causes ping spikes for people, usually every 60 seconds as Windows by default scans available WLAN connections every 60 seconds. You can try if disabling this background scanning helps to alleviate your problem. You can do this by typing: services.msc into the command line. This will then open a list of all services. Select the WLAN Autoconfig entry and change the startup type from automatic to manual (this way it won't start automatically with you booting into Windows). Restart your PC, ping google.com again and see if this has helped. (2) If all potential sources of interference are eliminated and the problem persists, you have to contact your Internet Service Provider. Depending on your type of internet connection (cable, fiber, DSL) it could be that the ISP has to adjust physical properties of your connection (e.g. attenuation levels), fix faulty wiring in his network (usually first two hops) or that the ISP's routing is subpar. You can check the routing by either using external programs like Pingplotter (https://www.pingplotter.com/) or by using the pathping command in the command line: pathping google.com -q while -q specifies the number of queries per each hop, e.g. 20. You have to keep in mind, though, that many hops are set up in a way to handle ICMP (ping) with a low priority, so this can give false readings: Some hops may show packet loss or high return times but if it doesn't carry through to the final hop, it doesn't say much or even anything at all. Plus, this is stuff your ISP has to tackle - if your home network is fine and you still have extreme ping spikes, it's his job to fix the problem, not yours. Edited December 3, 2021 by Lt Steiner Quote
Lusciousdrunk Posted December 3, 2021 Author Posted December 3, 2021 11 minutes ago, Lt Steiner said: It looks like a connection issue. You have two very high spikes in a span of 100 seconds and 100 packets. What you can do: (1) Try to eliminate all potential sources of interference in your home network. If you use WiFi, try to switch to a channel that is less frequented by neighbors' routers. If multiple people use your home network, try to set up a priority for real time applications or for your PC in the QoS settings of your router, reducing the chance of running into buffer bloat because someone else in your household hogs up all the bandwidth. Alternatively you can also limit the available bandwidth to other users in your household. Sometimes the Windows WLAN background scanning causes ping spikes for people, usually every 60 seconds as Windows by default scans available WLAN connections every 60 seconds. You can try if disabling this background scanning helps to alleviate your problem. You can do this by typing: services.msc into the command line. This will then open a list of all services. Select the WLAN Autoconfig entry and change the startup type from automatic to manual (this way it won't start automatically with you booting into Windows). Restart your PC, ping google.com again and see if this has helped. (2) If all potential sources of interference are eliminated and the problem persists, you have to contact your Internet Service Provider. Depending on your type of internet connection (cable, fiber, DSL) it could be that the ISP has to adjust physical properties of your connection (e.g. attenuation levels), fix faulty wiring in his network (usually first two hops) or that the ISP's routing is subpar. You can check the routing by either using external programs like Pingplotter (https://www.pingplotter.com/) or by using the pathping command in the command line: pathping google.com -q while -q specifies the number of queries per each hop, e.g. 20. You have to keep in mind, though, that many hops are set up in a way to handle ICMP (ping) with a low priority, so this can give false readings: Some hops may show packet loss or high return times but if it doesn't carry through to the final hop, it doesn't say much or even anything at all. Plus, this is stuff your ISP has to tackle - if your home network is fine and you still have extreme ping spikes, it's his job to fix the problem, not yours. Thanks for all the suggestions. I will definitely delve into this further. I’m married with two kids so someone is always streaming something or playing games ect. That was my first initial thought, that I just had too many people using the internet all the time. But the problem persists no matter who is using what. I have this problem at 1am when everyone has gone to bed and in the afternoon when my wife is streaming a show, one kid playing Roblox and the other Minecraft. You offered some great suggestions so I will definitely work on it this weekend. Thank you again. Quote
Lt Steiner Posted December 3, 2021 Posted December 3, 2021 4 minutes ago, Lusciousdrunk said: Thanks for all the suggestions. I will definitely delve into this further. I’m married with two kids so someone is always streaming something or playing games ect. That was my first initial thought, that I just had too many people using the internet all the time. But the problem persists no matter who is using what. I have this problem at 1am when everyone has gone to bed and in the afternoon when my wife is streaming a show, one kid playing Roblox and the other Minecraft. You offered some great suggestions so I will definitely work on it this weekend. Thank you again. Absolutely, keep us informed about the progress! A small addendum to what I wrote: Disabling the WLAN Autoconfig is of course only an option if you use a wired connection. If you use WiFi you can't disable it as you need it to connect to a network via WiFi in the first place. There are some programs, though, which can disable the background scans without having to disable the WLAN Autoconfig altogether as far as I know. Alternatively you can also edit some registry entries. A quick google search might help. I hope you can solve this issue! Quote
XeRoiX Posted December 3, 2021 Posted December 3, 2021 hmm, for ET have you tried typing in /r_primitives 2 in the consol yet? Have you turned off wifi auto searching for other connections? https://www.lifewire.com/disable-automatic-wireless-connections-15337 Give this small guide a look and see if this may help... Quote
Lusciousdrunk Posted December 3, 2021 Author Posted December 3, 2021 34 minutes ago, XeRoiX said: hmm, for ET have you tried typing in /r_primitives 2 in the consol yet? Have you turned off wifi auto searching for other connections? https://www.lifewire.com/disable-automatic-wireless-connections-15337 Give this small guide a look and see if this may help... I tried both of these. /r_primitives 2 doesn’t work. It say’s unknown cmd. I’m also tried turning off the auto searching for connections. Same lag persists. Quote
LarrY Posted December 3, 2021 Posted December 3, 2021 5 hours ago, Lusciousdrunk said: I tried both of these. /r_primitives 2 doesn’t work. It say’s unknown cmd. I’m also tried turning off the auto searching for connections. Same lag persists. Hi there, when ingame the console commands are: /r_primitives -> to show the current value of the property /set r_primitives 2 -> to set a new value (non persistent) use the second one to test if it works, it could ask for a /vid_restart If it works then put it in your cfg file as: seta r_primitives 2 1 Quote
Masa_1964 Posted December 5, 2021 Posted December 5, 2021 have u tryed other servers? just for check? Quote
Administrators daredevil Posted December 7, 2021 Administrators Posted December 7, 2021 What are your PC specs? Lagometer screenshots? On 12/1/2021 at 8:01 PM, rambozo37 said: seta com_zoneMegs "128" seta com_hunkMegs "512" He is going to get messed up if he has 4GB RAM PC with 512 on hunkmegs. 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.