Hey guys, I have a XL2411z monitor and am using the strobe utility but when i try set up a custom resolution in the nvidia control panel and press test the it adds black bars to the screen and I can't get them off without restarting my pc.
anyone got any ideas?
also if anyone would like to add the best settings for cs:go that would be cool
Cheers guys
edit: after messing about with it for a while I've found out that for some reason it only happens when I set the vertical pixels to anything over the number 1211
VT1500 tweek not working(causing black bars)
-
Falkentyne
- Posts: 2795
- Joined: 26 Mar 2014, 07:23
Re: VT1500 tweek not working(causing black bars)
Vertical *pixels*?
There's no vertical pixels field. It's Horizontal pixels and vertical lines
and then "Active horizontal pixels and vertical lines"
I don't use an Nvidia card. I just use ToastyX CRU.
But if you are making VT Tweaks do NOT change the active resolution at the bottom.
Keep that 1920x1080.
The only thing you should be changing are the manual timings.
Front porch should be 48 pixels and 3 lines (88 pixels and 4 lines is only for 60hz)
Sync width should be 32 pixels and 5 lines (44 pixels and 4 lines is only for 60hz)
Horizontal total should be 2080. (2200 HT is only for 60hz)
Vertical total should be in the range of 1340-1370 for "Low" VT tweaks (this avoids any 2d image degradation from scanlines, but strobe crosstalk is only reduced by about 12%), or VT 1497-VT 1502 (for high VT tweaks; this reduces crosstalk by 25%, although a faint scanlines effect similar to what is seen in "Lightboost" mode may be seen; all VTs in this range have the exact same effect so use whichever one does not cause frameskipping).
If you are still getting black bars at 1920x1080, then go into "Display mode" and set the image size to "FULL"
If it's set to "Aspect", then that's your problem. Sometimes, "Aspect" becomes checked" if you were playing around with low resolutions and chose "aspect" then switched back. This is because "Aspect" should be greyed out and not available at 1920x1080 as that is the native res. But when you use a VT tweak, the monitor scaler internally thinks the vertical width resolution is 1440p (this is why aspect improperly becomes available when it shouldn't) but the OSD still knows the resolution is 1920x1080 (which is why the 1:1 option is STILL greyed out). Sort of complicated but that's the problem, I think.
There's no vertical pixels field. It's Horizontal pixels and vertical lines
and then "Active horizontal pixels and vertical lines"
I don't use an Nvidia card. I just use ToastyX CRU.
But if you are making VT Tweaks do NOT change the active resolution at the bottom.
Keep that 1920x1080.
The only thing you should be changing are the manual timings.
Front porch should be 48 pixels and 3 lines (88 pixels and 4 lines is only for 60hz)
Sync width should be 32 pixels and 5 lines (44 pixels and 4 lines is only for 60hz)
Horizontal total should be 2080. (2200 HT is only for 60hz)
Vertical total should be in the range of 1340-1370 for "Low" VT tweaks (this avoids any 2d image degradation from scanlines, but strobe crosstalk is only reduced by about 12%), or VT 1497-VT 1502 (for high VT tweaks; this reduces crosstalk by 25%, although a faint scanlines effect similar to what is seen in "Lightboost" mode may be seen; all VTs in this range have the exact same effect so use whichever one does not cause frameskipping).
If you are still getting black bars at 1920x1080, then go into "Display mode" and set the image size to "FULL"
If it's set to "Aspect", then that's your problem. Sometimes, "Aspect" becomes checked" if you were playing around with low resolutions and chose "aspect" then switched back. This is because "Aspect" should be greyed out and not available at 1920x1080 as that is the native res. But when you use a VT tweak, the monitor scaler internally thinks the vertical width resolution is 1440p (this is why aspect improperly becomes available when it shouldn't) but the OSD still knows the resolution is 1920x1080 (which is why the 1:1 option is STILL greyed out). Sort of complicated but that's the problem, I think.