FUCKING SCREEN TEARING FUCKING VSYNC INPUT LAG FUCKING 800 DOLLAR

>>385760608
vsync was a mistake

File: 1500497760471.png (66KB, 510x332px) Image search: [Google]

66KB, 510x332px

Are you ok OP?

>>385760608
Just turn off vsync and limit your framerate you cockmongling retard

File: 20170731_154325.jpg (191KB, 600x582px) Image search: [Google]

191KB, 600x582px

>>385760608
No.

>>385761359
>limit fps to 60
>constant tearing at the center of the screen
>limit fps to 59
>constant tearing at the bottom
>unlock framerate
>tearing EVERYWHERE
I CANT FUCKING WIN

>>385761535
same, I aint gonna buy a $400 monitor

>>385761535
Buy a new monitor.

>>385761535
>Buy a non-shit monitor
>Don't adjust any frame rate settings
>No tearing ever
Werks fer me :^)

>>385761359
Literally all the drawbacks of vsync and none of the benefits.

File: 1489271444149.png (266KB, 368x657px) Image search: [Google]

266KB, 368x657px

>buy monitor
>rotate it sideways so its tall
>never notice screen tearing

>>385761535
I've literally done that all my life with multiple different pc's and/or laptops and never EVER had screen tearing.

>>385761817
Except vsync causes input lag and tanks performance like a motherfucker. while limiting the framerate doesn't.

If you render enough frames the tears become so small that you can't notice them.

>>385761605
a good monitor is literally around 100 bucks. maybe 120.

PC master race amirite guys

>>385760608

Why are you like this?

>>385762179
Can't get screen tearing if consoles can't even reach half the refresh rate of a standard TV.

>>385762058
Limiting your framerate causes input lag as well, why do you think quake pros run the game at like 300fps instead of capping it at 60?

>>385762337
Why do you think "quake pros" don't get screen tearing?

Vsync causes much more input lag than just limiting framerate.Besides, you don't have to limit it to 60. Limit it to a framerate that doesn't cause screen tearing.

Look at it this way. You have 2 options excluding gsync. limit framerate and get a little bit of input lag OR enable vsync and get input lag AND possible performace issues. Or ya know, you could just play it in borderless window.

>>385762738
borderless window uses windows vsync

>>385762886
Never heard of "windows vsync". If that's true then that vsync is better than the one any game uses.

Also, how come "windows vsync" doesn't cause a framerate lock but removes screen tearing?

>>385762738
>Why do you think "quake pros" don't get screen tearing?
They do.
>Vsync causes much more input lag than just limiting framerate
[citation needed]
>Besides, you don't have to limit it to 60. Limit it to a framerate that doesn't cause screen tearing.
No such magic framerate number exists.
>Or ya know, you could just play it in borderless window.
Look at this fucking faggot. Borderless window doesn't have screen tearing because desktop composition forces vsync on everything. Also it's actually worse for input lag since on top of being framelocked anyway, apps are also not running in exclusive fullscreen and therefore frames aren't pushed directly to the screen but have to be piped through the desktop window manager.

File: 1416768454432.jpg (38KB, 374x374px) Image search: [Google]

38KB, 374x374px

I have literally never experienced screen tearing. Am I doing something wrong?

>>385763168
the vsync that windowed mode uses causes incorrect fps readings
i noticed this heavily in wow i would be getting 65 fps but it felt like 40

>>385763421
Vsync causes more input lag because it affects more than just framerate. Back when i had a weaker pc i could noticably tell if vsync was enabled or not just based on the feeling. I don't know the technical stuff behind it since i'm not exactly sure what vsync does behind the scenes.

>No such magic framerate number exists
Of course it does. It's usually around 60, depending on the monitor. 58 or 59. If that doesn't stop the tearing than you should get out of your moms basement and buy a better monitor instead of playing games on a 24hz 4:3 monitor.

I know how borderless works. But it's about the smoothness of the game. Who cares if it also causes input lag and is not exclusive. As long as it runs better than standard ingame vsync, doesn't cause tearing, and doesn't limit framerate, who gives a fuck? I don't know how to prove to you that vsync causes more input lag without doing a benchmark, which i'm not going to do just because some random faggot on the internet doesn't believe me.

>>385764102
I noticed the same. But only in WoW though. It might be their ducktaped engine.Wow is the only game that runs better on fullscreen for me. Every other game always runs best in borderless.

>>385764643
>I don't know the technical stuff
This is all you needed to say. Basically everything you said is completely wrong and shows an absolute lack of understanding of even the most basic concepts at work here, but whatever works for you I guess. Just, you should probably stop telling others what they should or shouldn't do.

>>385765013
Can you read? I said I only don't know the technical stuff behind vsync. What exactly Vsync does on a deeper level. I never cared for it since i just turn it of and everything works (better). If you know, feel free to enlighten me oh glorious all knowing vsync master.

>>385760608
>Regular monitor
>Horizontal line splits the screen whenever the images change too fast
How do I fix this?

>>385765326
>feel free to enlighten me
Go fucking google it, your ignorance doesn't affect me either way and if you want knowledge you ought to work a bit for it.

File: comp3.bmp.jpg (200KB, 1280x720px) Image search: [Google]

200KB, 1280x720px

>>385765654
I don't need to google it to know that you are full of shit. Vsync is horrendous and it should not exist. I've programmed a DX engine before, I know the gist of it, but I didn't make vsync myself. DX just gives you an option to sync in the SwapChain by a specified interval. And that is what i don't know. How it works behind those scenes. what happens when I set the interval to 3 for example. Nobody fucking knows what the DX devs did to make that bullshit work. Everybody knows that the api is a mess.

Any good 4k Memeitors yet?

>>385766512
>>385765654
Just to specify that interval part. I know what happens but i don't know how it works. Hopefully you understand and can read that.

>>385766512
>I've programmed a DX engine before
Bullshit. I call fucking bullshit. I refuse to believe a professional programmer working with 3D engines doesn't even know how vsync or even a monitor itself works. Or you're a yanderedev tier "programmer" who got by copypasting code and watching video tutorials.

>>385766913
I'm not a professional engine programmer. That was a project i did for fun. Fucking big surprise I don't know everything there is to know about everything programming. Especially stuff like vertical syncronisation which, like I stated previously, I am not interested in. I implemented it, it worked and I didn't question it. Tell me one good reason why I should know how exactly vsync works on a core level if i know that it's shit and should not be used. At the time I implemented that, the only thing i had was a little cube jumping around from corner to corner. Not rendering anything. Limiting the framerate did just what it suggests. It limited the framerate to a specified number. Say 1000, at the time, since unlimited would be around 10k. Ive monitored the input and performance. The input delay after pressing the space bar to change the color of the material was around 0.002ms without the limiter. 0.008 with the limiter. Now get this: With vsync enabled the framerate obviously jumped to my monitors refresh rate (144hz) while in full screen mode. The input delay was fucking 0.15ms. After that i obviusly removed it and limited the framerate again to 144 this time. The delay was ~0.025ms.

>>385767757
>Tell me one good reason why I should know how exactly vsync works on a core level if i know that it's shit and should not be used.
Because this statement is wrong.
>The input delay was fucking 0.15ms
Oh no, a fraction of a millisecond. Say it isn't so.

>>385768156
You obviously don't know how horrible a delay of 0.15ms is if the only thing being rendered is a moving colored cube.

>Oh no, a fraction of a millisecond. Say it isn't so
That statement alone made everything you said invalid. That's as if I would say "Half life has an input delay of 12 seconds. Oh well, it's only a fraction of a millennium"

>>385768538
>You obviously don't know how horrible a delay of 0.15ms is if the only thing being rendered is a moving colored cube.
It's literally less than a fucking frame, at 144hz every frame takes ~7ms, it's literally impossible for a person to even notice the delay being there unless it happened right after a frame was rendered in which case the maximum delay would be 1 frame so ~7ms.
>That statement alone made everything you said invalid. That's as if I would say "Half life has an input delay of 12 seconds. Oh well, it's only a fraction of a millennium"
Human reaction time is measured in milliseconds, not fractions of milliseconds, and the average human takes over one hundred milliseconds to react to external stimuli. Anything under one millisecond is negligible.

Enjoy your $800 heater :^)

>>385769186
yeah, one cube. one color, one simple movement. 0.15ms. now add millions of other cubes to make a game with actual meshes. The cube has 6 polys if they have not been triangulated. A single character in a modern AAA video game has around 100k polys. probably even more. And that's just one character. Now add textures to that and animation, as well as physics calculations. Now check the delay. Probably not a fraction of a ms anymore. probably closer to around 0.5s which is noticeable. Now of course, AAA games are more optimized, so it's vsync probably wouldn't cause 0.5s input delay. but it will still be too high.

Anyway. all i was saying is that shit adds up. And 0.025ms add up to WAAAAAAY less than 0.1fucking5ms.

freesync

File: 1487105908305.gif (113KB, 351x398px) Image search: [Google]

113KB, 351x398px

>>385770046
Holy shit my dude, vsync has absolutely nothing to do with scene complexity, and it's not something that can be "optimized". As you saw on your engine experiment, it either works or it doesn't.

>>385770554
Whatever you say nigglet. I'm not going to explain anything anymore.If you don't believe me then don't. You're just like one of those flat earthers. "The earth is flat no matter how good a job you do disproving it."

HAHA STUPID FAGGOT GOT OWNED

any tips on how to limit my monitors velocidensity

>>385770965
>doesn't know what he's talking about
>has stated several times that he doesn't know what he's talking about
>"I'm not going to explain anything anymore"
You should be a comedian.

File: dead-ox.jpg (25KB, 303x345px) Image search: [Google]

25KB, 303x345px

>>385760608
>not having vsync off and using the Fast option in the nvidia control panel

File: 1490413672568.png (339KB, 962x1251px) Image search: [Google]

339KB, 962x1251px

>not owning a 1440p 144Hz G-sync monitor
Buncha fukkin plebeians in this thread.

>>385760608
I'm with you OP, I just hate it so much.
What's the biggest factor? Having a good monitor? Better GPU? Why does scrolling in Firefox give me such bad screen tearing? Why is it 1000x worse on linux?
Does my equipment just suck, or am I hypersensitive to screen tearing? I hate it so much.

>>385771394
fast is only good if you have 2-3x your refreshrate in framerate

File: 1496554928034.png (61KB, 311x304px) Image search: [Google]

61KB, 311x304px

>have massive screen tearing in literally every game unless i have vsync on
>with vsync on i get micro stutters
IM GONNA FUCKIN FREAK

>>385760608
Got a 144hz g-sync monitor on black friday. You should start saving anon.

>>385771537
Monitor doesn't matter, good GPU allows you to avoid dropping frames with vsync on which is what causes that sluggishness or stutter when vsync is on.
>Why does scrolling in Firefox give me such bad screen tearing?
Enable desktop composition aka aero.
>Why is it 1000x worse on linux?
Linux doesn't vsync the desktop. Maybe it's an option, google it.

>tfw paid ~$250 for a freesync 144hz monitor but I can't even tell the difference in refresh rate and freesync doesn't work on Linux

>>385771439
I do.
>mfw backlight bleed
>mfw IPS glow
the colors are really damn good but I can't help but feel I got fucked in the ass

>PC gayming

>>385772172
>falling for the IPS meme
I have literally never had an issue with TN panels.

>>385772172
>TN has shit colors
>IPS has glow and shit
>VA has bad motion
>OLED has burn in and the colors die
good panel tech when?

>>385771897
>Linux doesn't vsync the desktop
Eh, I'm asking compton to run with opengl vsync and that sort of helps - it's no longer screen tearing, it's more of a herky jerky movement while scrolling now.
Thanks for the pointers though m8

>>385772297
I do feel like I fell for the meme. I mean, when I put it next to my old TN the difference is night and day, TN comparatively is like looking through thick milky fog, but newer TNs are much better, right?

>>385772301
Well, at some point they'll probably figure a way to fix OLEDs. Probably.

>>385772439
For the jerky movement a better monitor would help. Particularly one with a higher refresh rate. Of course that assumes your GPU can easily render at that framerate, though if it's just the desktop I'd hope any GPU made in the last decade would be able to do it.

>>385772172
I know I did. I have a burn in across my entire screen where my browser toolbar usually is. Sucks I couldn't use my gaming monitor for anything but gaming without it going to shit.

>>385772773
What tech? IPS? Wow. How long did you run it like that? I'm the kind of person to alt-tab between stuff often so this probably won't happen to me... hopefully.

>buy busted 1080p LED second-hand monitor for cheap
>works perfect with Vsync on with no tearing nor input lag

OP is an idiot

>>385768156
>Oh no, a fraction of a millisecond. Say it isn't so.
0.15ms is quite a bit of time you imbecile

>>385772856
Its the ROG PG279Q. To be fair, when it started developing I almost exclusively left it on with my browser pulled up. Its much more faint, but a burn in is beginning to develop at the seam of my taskbar as well.

>>385773231
Same panel as mine cheaper AOC. How's your backlight bleed?

>>385773285
Very minimal. There is a tiny bit next to my start button.

File: if i tear you to pieces.jpg (27KB, 320x320px) Image search: [Google]

27KB, 320x320px

>>385760608
What seems to be upsetting you OP?

>>385762337
That's not because capping your frame rate is bad, it's because most games run smoother with less minor hiccups at massive framerates.

>>385773474
Damn, you got lucky then. Mine has quite a lot, though under normal usage I can't see any of it. The silvery IPS glow in the corners is apparent, though. It's kind of funny how one of IPS selling points is viewing angles, but if you move your head just a bit during a darker scene you see that annoying glow.

>>385773607
I know I did. I look at some people's ROGs and all I can say is damn. You just have to ask yourself at what price point does it become unacceptable to have shit like this happening? Why is $700 not sufficient to have a flawless product for at least 2 years?

>>385761535


get a non retadred monitor

144hz here

eat shit

>>385774009
I guess it works because there's hardly any alternative. 144Hz IPS is a relatively new thing, there's like a couple of panels, all made by AU Optronics, and the demand is high so they skimped on Quality Control. I guess it's cheaper for them to pay for the ones returned. I've read a bunch after getting my monitor (should've done it before!) and apparently IPS tech got through a bunch of simplifications before becoming accessible price-wise so those gamer IPS panels aren't quite the same thing as the really high-quality professional ones. But the pro ones don't go above 60 FPS because there's no point for them to, so it's not like they're perfect for gaming either. It's a bit of a shitshow.

How's the IPS glow on yours, though? The silvery one in corners when you shift your view?

>>385774587
144hz can't solve a retarded windows issue.

>>385774947
Much worse than my bleed. If I'm looking at a dark loading screen I can see it in the bottom right and top left corners. Otherwise it doesn't bother me too much.

>>385775727
Yeah well, unlike with bleed it's just a thing that comes with technology, though supposedly some panels have less of it, but not our panels. Goddamn, even though my bleed isn't very good it actually doesn't bother me all that much but the glow kind of does once I've started noticing it. Unlike bleed, which I can see only when the room is dark and the picture is black or really dark, I can see the glow even in something like Quake. But there isn't really to be done about that apart from switching back to TN, I guess. Or I can accept there is no perfect display tech yet and deal with it.

File: 1377030790385.jpg (88KB, 500x667px) Image search: [Google]

88KB, 500x667px

>>385760608
>VSYNC INPUT LAG
>implying you are good enough at anything for that to be a detriment

>>385775991
There are no perfect ones. I really want something with all the memes so if the PG35VQ ever comes out and doesn't suffer like the 279Q I will certainly upgrade. Outside of that model I haven't seen anything that looks like it will be game changing.

>>385776527
Damn, that looks way out of the price range I'm comfortable with. HDR sounds cool, though the fact that Nvidia had to use a SDR monitor with deliberately awful settings to make it looks better is kind of worrying:

https://www.youtube.com/watch?v=cgBzpYTn_8c

>>385763613
Your rig is too weak to generate enough fps to go above your monitor's refresh rate

>>385776687
Tearing is independent of the frame rate.
even if you're at solid 60hz, if you don't flip the buffers during the vsync, you get a tear.