Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
How do you not notice the screen tearing (and yes it is there)? I used to do the placebo effect and pretend the tearing was not there, but firing a weapon in the dark and then seeing the tearing constant made me learn that triple buffering exists for a reason and 120 solid FPS is far better than screen tearing.
Caping the FPS, does not stop the tearing, as the frame is still out of sync with the monitor. Think of Vsync as limiting your GPU from sending then next frame until the monitor demands it, without Vsync the monitor takes in as many frames as the GPU outputs thus screen tearing.
there is tearing, you just have tricked yourself into not seeing it. Common sense tells me if you have a 60hz monitor you achive 60 fps and no higher ,and putting a limiter just slows down the screentearing.
I have 120 fps thanks to my 120hz monitor, but i would never not use triple buffering (to which was created just to counter the trouble of double buffering.
144hz monitor will still tear even under 144 fps, why? because the frame is out of sync without Vsync thus the monitor has no way of stopping the 120 fps from going through thus it will still tear.
I have a 120hz monitor even leaving Vsync off for a second with an FPS cap and there is still tearing because at 120 fps without Vsync the monitor as far as its concenred is trying to take as many frames as possible. Vsync is the only way to stop the tearing, your placebo effect ive tried, it dont work.
You capping the game, does not stop the monitor from trying to take every frame off the buffer, and no that cap you placed does nothing at all the to the buffer or the frames the monitor is about to draw off said buffer. I know exactly how FPS works, i know how Vsync works, to which with Vsync off even with an FPS cap, you will still tear becuse the monitor as far as its concerned will try to intake 144+ fps even with a cap, you just cannot see that because you're reading an fps counter.
Trust me, your monitor is still tearing heavily i gurantee that much because without Vsync on you will always tear. Ive tried your fix on this 120hz monitor, it still tears even at 119 fps.
If i cannot stop the tearing with Vsync off at 119 capped FPS, then you cannot stop it with 120 fps set on a 144hz monitor. The tech does not allow it. Only triple buffered Vsync allows your monitor to display the true fps being shoved out of the buffer in match with your monitor refresh rate.
Ive been repairing computers since 1984 so i would know alot more.
wrong. The FPS cap just stops the game from outputting as many frames as possible, not the buffer of the GPU. Sorry but Vsync exists for a reason and the second you reach a single frame above 144 fps you will get tearing as your monitor has no way to sync above 144 fps unless you use Vsync. This is monitor common sense, the higher the FPS the more you tear unless Vsync is enabled toi actually sync the frame to the monitor and its refresh rate.
I have no problem also youve resorted to character attacks "stating an uneducated response in every post. I'm willing to work with you. What is your display's model, and from what company?"
there is nothing to work with. ive repaired PC's since 1984 and owned countless monitors from 200hz CRT's all the way to the cheezy 100$ 60hz monitor. I know how Vsync works, thus why i use it. The input lag stuff was stomped out the second triple buffering existed.
You're tearing stop denying it, you get a single frame above 144 fps (your monitors refresh rate) the screen will be tearing. no cap will stop that, even if you set it 143 .
you've trained your mind not to notice, but its still is there, and wont be going away with a simple FPS cap. If all that was needed was an fps cap, then Vsync would never have been created. Double buffering was a cause of lag to some, thus triple buffering was created to curb that problem.
No, only those who have no idea about hardware and screen tearing leave Vsync off, true pros of C:SS and GO all sync the monitors to 60 and 120 fps respectfully (assuming one does not own the 144hz monitor).
Ive been playing CS, since before 1.4 and all the way till now, ive tried your little command, it does nothing at all the tearing still happens because as far as my card is concerned without Vsync on, itll send as many frames as possible to the monitor even if the game has a cap on it (Which hinders the frames processed through the Engine and not the framebuffer of the card)
Asus VG236 is my monitor, i would suggest you stop calling a 120hz monitor crap when you yourself guranteed basically own the upgraded model to mine which is why it has 144hz.
The only way to remove all screen tearing is with triple buffered Vsync, and this is just how it is, there is no arguement around it. Limiting the FPS just before the refresh rate does nothing because the monitor is still trying to refresh faster than its capable of.
You placebo people are odd in the sense you cannot see what's objectivefully happing on the screen. The Vsync is there to actually ensure when your monitor refreshes the frame is synced to that refresh rate, and no that does not cause any kind of lag (triple buffering).
Ive tried to run with it off before, and learned my lesson to turn it on when firing weapons in dark spaces (you basically get a bunch of tearing firing weapons in a dark room).
I guess with enough motion blur you can hide a screen tear, but its still happening as the frame-buffer with Vsync off is shoving as many frames out of it as possible.
1. fps_max "one unit below max display Hz" ie. 119
2. fps_max "display Hz" ie. 120
I don't know the science behind it but this eliminates that "input lag" feeling (for me at least).
You dont get it, monitors only work a certin way. The CS command you posted only effects the game Engine, and not the buffer (The place where the frame comes from) on the card. This means every single time a frame goes above 144fps you will get a tear, because the monitor is incapable of syncing the frame to its refresh rate, thus a tear happens.
Triple buffering basically how do i put it in laymans terms, it refreshs the frame 3 times per second thus elimating the actual input lag double buffering produced (triple and double are not the same).
lastly most compeitive pros all use 120hz and 144hz monitors respectfully why? well what pro wouldnt want a solid 120 or 144 fps.
did that long ago, it means nothing as the Engine only obeys that command, it has no effect on the framebuffer of the card. I get tearing even with the max fps command because the monitor has no idea when the sync with the card, and that cap does nothing to curb that.
Only triple buffered Vsync elimated all input lag and keeps the screen from tearing.
Screen tearing on some video cards is much more pronounced than others. For example, my gtx470 I used to have had no screen tearing that I could notice in almost every game I played except one, Alan Wake. I ran an AMD 7850 for a while and it had crazy screen tearing along with a LOT of "coil whine" (look it up) and I went back to a 470. Now I have a GTX780 and I haven't noticed a single game with screen tearing. My roommates PC on the other hand has a gt660 and it has tons of screen tearing on most games.
Vsync simply adds noticeable lag to your mouse even if you cap your fps extremely high. I cap at 145 and my monitor refresh is 144 and if I turn on Vsync I get immediately noticeable mouse lag.
The funniest thing about this thread, is that you would be totally right on every word you've said, but you are missing two key things: V-Sync ***IMPLEMENTATION IN CS:GO*** (which is total CRAP, ***EVEN WITH TRIPLE BUFFER***), and the new technologies available that synchronizes GPU and monitor frequencies (G-Sync which is nVidia's proprietary tech and is already available -and also already was when this conversation happened-, and AMD's open-standard-based & still-not-available FreeSync tech).
I bet OP had/has a G-Sync enabled monitor with a G-Sync compatible GPU :P
Returning to CS:GO's V-Sync ***** implementation,it's just a fact. Maybe it's more exaggerated with some hardware/drivers version combination than with others (not taking into account the tier/range, AND NOT RELATED AT ALL TO THE MANAGEMENT/CONFIGURATION SKILLS OF THE USER), but even in the best possible case, I bet it would still be bad enough to not being an option for competitive play.
I have an i7 3960x@4,2Ghz (liquid cooled) + 16GB of RAM in Quad Channel + HD7970Ghz Ed.@1100/1600Mhz + 840 Evo SSD + (currently) AMD Catalyst 14.12 drivers. And the V-Sync is just NOT AN OPTION. Don't even need to synthetically measure the input lag. It's just TOO MUCH, TOO NOTICEABLE. You can't deny that, by any means.
Kind regards.