Digital Paint Discussion Board
Paintball 2: The Game => Help and Support => Resolved Help & Support => Topic started by: Ranger on May 04, 2014, 10:34:49 AM
-
I believe my mouse is Okay, but I have sometimes during playing very uncomfortable lags. I tryed "m_rawinput 1" - it worked Okay for several days and later again mouse lags started. I tryed 2 mouses (everytime the same problem) and I have this problem for a month I guess... Where could be the problem? My laptop or the game?
-
I have 2 laptops on which I play Dp. I have exactly the problem u explained on my 2nd lappy when having TS opened. I tried turning V sync on and it helped a bit.
-
I don't know what you guys mean. Having sensitivity in topic name, do you mean that mouse feels less/more sensitive at certain points? Or doesn't it work at all at certain points? Or wtf.
Matze, since you mentioned Vsync, does this include displaying, or just mouse?
There is big difference between input problems and general game slowness at certain points.
-
In my case the mouse just stops moving for a short amount of time.
I t meant the vsync u can enable in the video setup menu in dp.
-
In my case the mouse just stops moving for a short amount of time.
I t meant the vsync u can enable in the video setup menu in dp.
Does it happen outside DP or in other games?
You can try with various settings (mouse related), it might help. Other than that never occurred for me and never heard of it. I guess Jitspoe might have an idea what this is, possibly you want to give him mouse related settings you use.
-
I guess its my lappy because when I use my other one with the same mouse i dont have these lags.
Edit: In other games I don't have any mouse lags :p
-
I guess its my lappy because when I use my other one with the same mouse i dont have these lags.
I wouldn't think this is mouse, I would think this is driver/OS and way DP handle it.
Of course you don't need to post this, but if jitspoe won't be able to tell wtf from Rangers data, you can help out :P .
I guess we should wait for more data from Ranger so we know more about problem...
Ranger, post your mouse related settings, OS, make sure you are using b40... Also are you sure it's not just whole game being laggy for sec? I personally saw game being laggy for sec on machines that shouldn't have any problem handling DP (and generally don't have such problem).
-
fix your fps and try to use cable for you internet
-
seta cl_drawfps 3
That will show you the lowest framerate every half second or so. See if the fps display drops down when you're seeing these "lags". Sounds like you're getting low framerate spikes causing your view to jump/lag. I don't think it has anything to do with the mouse.
-
Also, are you by any chance playing on linux? I remember having pretty huge problems there with my mouse, just wasn't smooth no matter what i did. But i guess it probably is not your case, because as you said it goes away. The problem i am talking here about is constant.
From my experience, PB doesn't handle high fps well. Try what jitspoe said, and if it doesn't help, you can try the other way, that is lowering your fps.
cl_maxfps X
but Viciouz told me once even better command
cl_sleep 4 makes the CPU wait 4 milliseconds after a frame, which means there is a limit of 250fps, but it's not quite the same as cl_maxfps 250. You could try cl_maxfps 250 instead if you want, I'm not sure it has the exact same effect. Personally I use cl_maxfps 59, 60hz refresh rate and gl_swapinterval 1 which gives me no screen tearing and no mouse lag.
you could try messing around with these commands to see if it helps.
-
What you would use ideally:
60hz refresh
gl_swapinterval 1
cl_maxfps 120, 90, or 66 (66 is ideal for double jumps, can switch to 120 for ramps, 90 for strafes and cjs, 27 for ladders and triples, 22 for standing djs/cjs)
cl_async 0 (i think client forces this anyways)
I had an issue a bit ago with awful response times at random points like you are having, I could have sworn it came up when I was playing the the cl_draw cmds, but who knows. I did a fresh install and I never had the issue again.
-
cl_maxfps 120, 90, or 66 (66 is ideal for double jumps, can switch to 120 for ramps, 90 for strafes and cjs, 27 for ladders and triples, 22 for standing djs/cjs)
How the hell you even came up with this (i know its what you need to use for some ladder jumps, but still) :D. Is there someone who can explain this and why does it make such a difference, switching maxfps value?
Also, what you mean by "120 for ramps" does it mean you fly higher or what ^^. I have been running around with 1k fps capped and could do everything without any difficulties. The only time i had to switch was for some ladder jump on one map, for other maps ladder jump worked just fine with 1k.
-
How the hell you even came up with this (i know its what you need to use for some ladder jumps, but still) :D. Is there someone who can explain this and why does it make such a difference, switching maxfps value?
Also, what you mean by "120 for ramps" does it mean you fly higher or what ^^. I have been running around with 1k fps capped and could do everything without any difficulties. The only time i had to switch was for some ladder jump on one map, for other maps ladder jump worked just fine with 1k.
play some q2jump and u'll understand it
-
How the hell you even came up with this (i know its what you need to use for some ladder jumps, but still) :D. Is there someone who can explain this and why does it make such a difference, switching maxfps value?
Most of the values take advantage of some minor physics manipulation. It seems arbitrary, but they have been tested over a long period of time. 120 is what people have figured for the best "high" fps, any higher tends to be a negative effect. The only way to explain the others is to use them yourself and see the difference. They are all minor advantages, but they still can make things easier.
-
Most of the values take advantage of some minor physics manipulation. It seems arbitrary, but they have been tested over a long period of time. 120 is what people have figured for the best "high" fps, any higher tends to be a negative effect. The only way to explain the others is to use them yourself and see the difference. They are all minor advantages, but they still can make things easier.
mhh i dont think this works for pb
-
Well after playing around with it, 120 doesnt seem to change anything because of the changes to ramps jits did, 90/66/27/22 still work for me though.
-
seta cl_drawfps 3
That will show you the lowest framerate every half second or so. See if the fps display drops down when you're seeing these "lags". Sounds like you're getting low framerate spikes causing your view to jump/lag. I don't think it has anything to do with the mouse.
I tryed. Normal fps during map was around 125, 110.. and when these lags occured, fpw dropped down to 80, 50, 20
-
Do you use a Logitech mouse or keyboard with the Logitech Gaming Software?
-
It seems that "Vertical sync" in video option fixed my problem...
-
Youre welcome. lol.
-
What you would use ideally:
60hz refresh
gl_swapinterval 1
cl_maxfps 120, 90, or 66 (66 is ideal for double jumps, can switch to 120 for ramps, 90 for strafes and cjs, 27 for ladders and triples, 22 for standing djs/cjs)
cl_async 0 (i think client forces this anyways)
I had an issue a bit ago with awful response times at random points like you are having, I could have sworn it came up when I was playing the the cl_draw cmds, but who knows. I did a fresh install and I never had the issue again.
Does anyone know if cl_async can be set to 1(toggled on)?
I found out recently that it is a feature that the pro's use in the real Quake2 Jump servers so that when they lower their FPS with cl_maxfps, they don't experience the "choppy screen effect". However, they still have the advantage of using that specified capped FPS # to perform that specific intended jump.
I think what most of them would do is for any given map, they would toggle between two different fps caps maybe sometimes 3 or more for the entire map. so either like 66 or 90 for one map, and then another 120 66, or 120 90. i'm not 100% but obviously the more times you have to switch your fps in a map for certain jumps might drastically effect your finish time on that map. However I also think that's something the map creators will take into consideration when designing their maps maybe. I'm not too sure on all that map editing stuff but yeah xd
Also I'm not too sure about what FPS is good for what, but I heard that certain fps will make you strafe faster (bigger jumps) and stuff like that so yeah i think most, if not all of what ace is saying is right.
also a cool jump video by n00k!e i stumbled upon last weekish that is really cool you should all check it out. its called n00k!e 1337 miles per hour.
https://www.youtube.com/watch?v=goaEiIY0R-Y
he's most likely the best pure jumper Quake II has ever seen. pretty epic video too 19mins long. he makes it look easy though ;) good music too must watch!!
Also as Ace was saying, cl_async is forced to 0 by the client. I'm not sure why this is? or if it is just default and can be changed... hmm?
-
cl_async is not used in this engine. I think you're confusing it with some other Q2 engines.
The equivalent (well, technically opposite) would be cl_locknetfps. When set to 1, the framerate and network rate are locked together (like classic q2, or cl_async 0). When set to 0, the game framerate and network rate are not locked (you can render more frames than network packets you send). cl_cmdrate controls how many packets/second are sent.
-
cl_async is not used in this engine. I think you're confusing it with some other Q2 engines.
The equivalent (well, technically opposite) would be cl_locknetfps. When set to 1, the framerate and network rate are locked together (like classic q2, or cl_async 0). When set to 0, the game framerate and network rate are not locked (you can render more frames than network packets you send). cl_cmdrate controls how many packets/second are sent.
Wasn't sure if async was forced or just not present. Guess it's not there at all.
Feel free to correct me, but it seems like cmdrate could replace maxfps, without the negative of choppy movement. The only place I noticed chop was on ice. Would love to see what other people think. Not sure how effective it is, but it seemed to do the same tricks as low fps.