Write protect qzconfig.cfg and repconfig.cfg files., Every change made to your cfg (like a fov, sensitivity change or change of crosshair) is instantly saved to those, that process induce a lag/stutter.

I've set both files as "read only" and same shit happens.

Pequliar, no improvement/difference at all?

Not really. I've set both of these files to read only in windows, and I did again the test of switching back and forth fast between weapons and the fps are still doing this annoying crap. I need a smooth transition.

Oh and also at random times there seems to be a "small death" where it freezes for like 1ms and then comes back, the green constant line on the lagometer leaves a small gap. Again this is just random, not triggered by weapong changes that I can tell.

Repconfig and qzconfig should also be empty, setting them to read-only wont help if there's already some crap stacked up or discrepancies in values between your config and those two files.

If you have them empty, set everything to default, restart and reexec, it helps with the cache.

Another reason could be too many commands for one line. Ql doesnt deal with this as smoothly as q3 used to, so either (dont) use vstr, have a separate config for guns only, or simply cut off some commands from the line (I had this happening when my vstr included crosshair color changes).

I have also tried not usin vrsts.. same shit, and I also got rid of everything but the basics (crosshair size, crosshair, sens, accel, fov) and I still get the lag.

Isolating weapon binds and vrsts on their own cfg also did nothing.

Looks like deleting everything inside repconfig and qzconfig and setting them read only did the trick.

Now there's another problem: Every time I change the weapon, I get a console message:

"couldn't write qzconfig.cfg"

This is insanely annoying since it fills the console with that crap and I can't read the chatlog properly...

Why the dumb idea of forcing people to have to deal with these 2 files?

That you have to try to learn to live with. Originally, I might be wrong as usual, but I think those two files were saved to some id server for safekeep every time you exited the game, that way you had easy acces to your cfg if you wanted to play from another computer.

I doubt that's the case anymore. They are just busting our balls as usual with useless shit. I can't live with this bullshit because sometimes im just talking to friends while we warmup and this ruins it. Fucking morons. It works perfectly fine in Q3 but in QL. Where the fuck is Syncerror? fuck it,.

Actually i cant even change cl_maxpackets from 125, its stuk there, it says its cheat protected.

I doubt that's the case anymore. They are just busting our balls as usual with useless shit. I can't live with this bullshit because sometimes im just talking to friends while we warmup and this ruins it. Fucking morons. It works perfectly fine in Q3 but in QL. Where the fuck is Syncerror? fuck it,.

have the same problem since a month or so... fast weapon switch and also quick zooms in/out does lag. (i use a fov/sens change instead of +zoom) and it also lags even if i start a game without bots.
i think it started to lag with that win10 update...

Im using Windows 7.

Any change you do with your binds (like changing sensitivity) will result into being written to cfg file which could cause lag, especially if you have an HDD. It could also lag once a few secs if you have a demo recording turned on. So either install QL to your SSD or even make a RAM drive (2 gigs should be enough, just make sure to move demos/screenshots to another drive when it gets full)

Because you mention that there is a spike on lagometer I will throw this out there.

If you are using maxpackets 250, then try 125 or 63 and see is there still the problem?

I say this because many years ago with the incredibly slow upload of ADSL1 internet I would try maxpackets 125 and I woud lag (noticably on the lagometer) every single time I would jump. It would go away at maxpackets 63

Now im sure your internet is much faster, but it just seems somewhat similar of problem.

No, it's not a spike. It's as if someone cut the green line, and there is a gap.. it kind of dies for a ms and then comes back to life. It's not really internet related, it's the game fucking up because devs are idiots. Q3 works fine.

Another game broken by stink terror

And the fuckers will most likely leave it like that forever. If they aren't going to do anything for the 20th anniversary, a patch that fixes this bullshit would be cool.

I doubt you'll ever see another ql update.
sad. It still works 1,000 times better than qc.

Half full mofo

This is nuts.

i have had the same issue and my problem got fixed by using the command: com_idlesleep 0

try it out, it might help.

Grtz Migs

Same shit, it will still slow down fps unless i have repconfig and qzconfig on read only.