Blur Busters Forums

It works fine at 144 hz. you just can't use vertical total tweaks (to increase the dotclock) and speed up the pixel transitions (to lower the crosstalk field size of the strobe pulse area)

Thanks for the reply, Falkentyne. So you'd suggest setting it at 120hz and then setting the VT for crosstalk settings? I'm new to the PC gaming world and so completely new to all this technology. In fairness, I've seen your name a lot on this site and other sites offering help and so I greatly appreciate the advice from someone who obviously knows what they're talking about. I've only just received the monitor today and haven't even set up the space for the desk and set up the PC yet, but I'd be grateful if you could recommend me some starting settings for the XL2430T for when I get started. Thanks very much for the advice so far

Up to you. The only issue if you do use the VT tweaks is you can't use the display mode aspect resizings in any mode that is a downsampled 1920x1080 (the monitor using the 60hz backlight pulse widths cause it to act strangely on that menu, e.g. the 'aspect' field becomes selectable in 1920x1080 (it shouldn't, as that's the native resolution, there is no aspect; without VT tweaks its grayed out and only the screen sizes are selectable) and the image gets shrunk and looks strange, and the screen size selections wind up being based on the shrunk aspect field instead of scaling from fullscreen first. You can get around that by using a VT for let's say, 100hz, but not for 120hz, then switch to 120hz if you ever intend to use the resizing features (but you have to switch back to 'fullscreen' later because the aspect setting will get saved, and I'm not sure if it gets stored in gamer profiles or not).

You can use CRU to make a custom standard resolution and refresh rate that will always use standard timings instead of your VT Tweaks but that only seems to work perfectly for DX9 games. Dx11 games may need a detailed resolution setting instead of standard resolution, as they seem to ignore the refresh rate you set in CRU for some reason. I haven't determined yet if this is an AMD 'feature' or if the same behavior happens on Nvidia cards or not. There's a thread where someone tried creating a 1600x900@100hz custom resolution, but the game used 1920x1080 downsampled to 1600x900 instead of recognizing 1600x900@100 independently, like the windows desktop accepted.

I've read that a 1.3 displayport cable should eliminate screen tearing, offer 144hz and give more clarity. For one thing, this almost seems to cancel out the need for g-sync? Would any monitor with a displayport support 1.3? I'm also wondering if 1.3 would solve some blurring issues?

There are no displayport 1.3 ports (yet). Sounds like you read something related to AMD's freesync (which won't be proprietary like Gsync is...it will actually be a Vesa stanadard). Gsync is good, when it works, but there are just WAYY Too many problems with the Asus Rog swift...and it seems like its more about the Nvidia drivers doing something to the monitor firmware but some of the panels have some issues also.

DP 1.3 was announced in September and standardized by VESA but there isn't a single monitor that uses that port. I'm expecting them with the Freesync monitors.

Oh, ok. Thanks for clearing that up for me, Falkentyne. You really are incredibly informative and helpful in the advice/info you give I would still guess the 1.2 displayport is better than DVI?

daveyfunk wrote:Oh, ok. Thanks for clearing that up for me, Falkentyne. You really are incredibly informative and helpful in the advice/info you give I would still guess the 1.2 displayport is better than DVI?

It's the same at 1080p. But I don't know if you still need the USB3.0 cable + the built in USB HUB if you use DisplayPort. Can someone confirm?

I don't have a DP 1.2 cable here.