Search found 30 matches
- 11 Jul 2020, 04:53
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
Thanks, jorimt. It was just bothering me if my PC's behaviour is normal.
- 10 Jul 2020, 19:24
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
You're fine there, especially for CS:GO then. Turns out I forgot to enable XMP after updating BIOS. Now I set RAM frequency to 3000MHz. I can't tell for sure but it appears that there are much less tearlines at 120fps after enabling XMP (but they still persist). That's because scanline sync adheres...
- 10 Jul 2020, 16:43
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
Th IPS version? Yes. I can't remember, but I don't think you ever shared your specs, which can make a difference for how severe (or not severe) tearing is in this scenario. - Intel Core i7-8700K - Nvidia GeForce GTX 1080 - Gigabyte Z370M D3H-CF - Samsung SSD 850 EVO 500GB - 16 GB RAM <s>2133MHz</s>...
- 10 Jul 2020, 15:11
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
Acer XB271HU
I'm not using capture, linked footage is a phone recording. Go to 0:09 and press ">" to view video frame by frame.
UPD: actually, tearing starts even at 0:05
- 10 Jul 2020, 14:42
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
But doesn't bottom tear imply that there is too much of a frametime variance? Consider 120fps fixed with RTSS at 144hz G-Sync monitor. In order for tearline to appear the last two scanouts should happen in 1-2ms less than 1/144 seconds. That means frametime of around 5 ms where perfect frametime sh...
- 01 Jun 2020, 16:33
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
A screen-wide "flash" (due to color change, etc) would have done nothing for this method. You need horizontal movement to spot the very beginning of the first on-screen reaction across the entirety of the vertical axis. But how would flash differ from horizontal movement? If there would be flash in...
- 01 Jun 2020, 16:03
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
A single "sample" with the "first on-screen reaction" method is considered the "first" discernible movement of the "first" frame update that appears at the given vertical position screen-wide due directly to the last user input. The remaining duration of that frame update (and/or any further frame ...
- 01 Jun 2020, 15:44
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
Getting back to this question: Also, one person I know has a 165hz/1440p monitor with G-Sync (Dell S2417DG). I linked this thread to him and he decided to test his monitor with 960fps camera on his phone and he measured that when he enabled 60hz mode the panel scanout time was 10-11ms (in 60hz G-Syn...
- 01 Jun 2020, 13:57
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
I thought that "sample" meant time at which frame was updated with global reaction. But you meant by "sample" that the reaction was only at that vertical position of the frame, right? If so, than I understand what you both were talking about. If the change happens only in tiny portion of a frame tha...
- 01 Jun 2020, 11:20
- Forum: G-SYNC
- Topic: Blur Buster's G-SYNC 101 Series Discussion
- Replies: 645
- Views: 615662
Re: Blur Buster's G-SYNC 101 Series Discussion
Because I'm pretty sure it would then look something like this: pic While a single 60Hz scanout now occurs across four 240Hz scanout cycles, and is thus lower lag than compressing it into a single 240Hz scanout per (every four), it still takes a total of 16.6ms to complete; you would only get simil...