Threaded Mode | Linear Mode

***ToastyX*** · 01-02-2018, 07:23 AM

(01-02-2018 07:01 AM)NexusP Wrote: I'm not using DSR. Does it behave the same regardless? When I use it with VorpX, it is an improved difference. The resolutions take hold with no out of range warning which I get with a higher refresh, and the desktop looks obviously bigger in 3840x2160@75. it's not that CRU isn't working with 1920x1080@75, it's shifted over a few pixels to the right. Is there no way to make adjustments conducive to that resolution?

Look at the active pixels. You are sending 1600x900 to the monitor. There's no way to send 3840x2160 @ 75 Hz with DVI. Check the monitor's OSD to see what resolution it's really receiving. CRU doesn't deal with positioning. That's up to the monitor. Sometimes the timing parameters can affect positioning, but that depends on the monitor, so you'll have to figure that out yourself. Also, if you're exceeding 165 MHz pixel clock with DVI, you probably need the pixel clock patch: https://www.monitortests.com/forum/Threa...ck-Patcher

NexusP · (Last edited: 01-02-2018, 03:39 PM by NexusP)

(01-02-2018 07:23 AM)ToastyX Wrote:
(01-02-2018 07:01 AM)NexusP Wrote: I'm not using DSR. Does it behave the same regardless? When I use it with VorpX, it is an improved difference. The resolutions take hold with no out of range warning which I get with a higher refresh, and the desktop looks obviously bigger in 3840x2160@75. it's not that CRU isn't working with 1920x1080@75, it's shifted over a few pixels to the right. Is there no way to make adjustments conducive to that resolution?
Look at the active pixels. You are sending 1600x900 to the monitor. There's no way to send 3840x2160 @ 75 Hz with DVI. Check the monitor's OSD to see what resolution it's really receiving. CRU doesn't deal with positioning. That's up to the monitor. Sometimes the timing parameters can affect positioning, but that depends on the monitor, so you'll have to figure that out yourself. Also, if you're exceeding 165 MHz pixel clock with DVI, you probably need the pixel clock patch: https://www.monitortests.com/forum/Threa...ck-Patcher

Thanks for the info. I'm actually using pixel clock patcher. I can't get anything above 77hz. 75hz serves my needs (using a Oculus Dk2 with VorpX). I deleted 1920x1080@75 and added 1600x900@75 to CRU. That still exposes all of my custom Nvidia resolutions in Spheck up to 3840x2160@75. I can use 1920x1080@75 on my desktop via Nvidia without the alignment issues.

Moirae · 01-02-2018, 09:20 PM

Hello, I have a question. Wondering if it's possible to create a custom 4:2:0 resolution with CRU or NVCP. I'm trying to add 3840x1620 as a res and I'm having no luck.

***ToastyX*** · 01-03-2018, 08:07 AM

(01-02-2018 09:20 PM)Moirae Wrote: Hello, I have a question. Wondering if it's possible to create a custom 4:2:0 resolution with CRU or NVCP. I'm trying to add 3840x1620 as a res and I'm having no luck.

No, there isn't a way to define non-TV resolutions as 4:2:0.

IanL · (Last edited: 01-04-2018, 02:45 PM by IanL)

I use CRU to match my ATI Graphics card to a LG 42" plasma TV over DVI. The 1920 x 1080 nominal resolution results in overscanning, and 1910x1060 has done the job.

I have just updated to Win 10 (Creators) and CRU 2.6 has no effect at all. The resolution appears for selection in the Win 10 Display Resolution selector, but it does nothing when selected.

I updated CRU to 3.0, but it seems to crash something; the TV reports Invalid Signal. I recovered with Safe Mode and used CRU reset and a reboot of the PC to get the display back.

Is it possible that the latest Win 10 is storing resolution parameters in a different place?

***ToastyX*** · 01-04-2018, 08:42 PM

(01-04-2018 02:45 PM)IanL Wrote: I use CRU to match my ATI Graphics card to a LG 42" plasma TV over DVI. The 1920 x 1080 nominal resolution results in overscanning, and 1910x1060 has done the job.

I have just updated to Win 10 (Creators) and CRU 2.6 has no effect at all. The resolution appears for selection in the Win 10 Display Resolution selector, but it does nothing when selected.

I don't see how that's possible unless there's a problem with the graphics driver. What specific card do you have?

(01-04-2018 02:45 PM)IanL Wrote: I updated CRU to 3.0, but it seems to crash something; the TV reports Invalid Signal. I recovered with Safe Mode and used CRU reset and a reboot of the PC to get the display back.

Is it possible that the latest Win 10 is storing resolution parameters in a different place?

There's nothing different about the way Windows 10 handles EDID overrides. The same settings should work the same way unless the graphics driver handles something differently with Windows 10. Simply changing the default 1920x1080 to 1910x1060 should behave the same with both CRU 1.2.6 and 1.3.1 on Windows 7-10.

IanL · 01-04-2018, 10:22 PM

(01-04-2018 08:42 PM)ToastyX Wrote:
(01-04-2018 02:45 PM)IanL Wrote: I use CRU to match my ATI Graphics card to a LG 42" plasma TV over DVI. The 1920 x 1080 nominal resolution results in overscanning, and 1910x1060 has done the job.

I have just updated to Win 10 (Creators) and CRU 2.6 has no effect at all. The resolution appears for selection in the Win 10 Display Resolution selector, but it does nothing when selected.
I don't see how that's possible unless there's a problem with the graphics driver. What specific card do you have?

(01-04-2018 02:45 PM)IanL Wrote: I updated CRU to 3.0, but it seems to crash something; the TV reports Invalid Signal. I recovered with Safe Mode and used CRU reset and a reboot of the PC to get the display back.

Is it possible that the latest Win 10 is storing resolution parameters in a different place?
There's nothing different about the way Windows 10 handles EDID overrides. The same settings should work the same way unless the graphics driver handles something differently with Windows 10. Simply changing the default 1920x1080 to 1910x1060 should behave the same with both CRU 1.2.6 and 1.3.1 on Windows 7-10.

Thanks for your reply. The graphics card is ATI Radeon HD 3450, Hardware ID PCI/VEN_1002&DEV_95C5&SUBSYS_E670174B&REV_00. It was working well on Win 10 Version before 1709, and the problem arose straight after the update to V1709. The driver is 8.970.100.9001 dated 13/1/2015. I've tried "Update Driver", but Windows reports the best driver is installed.

The reboot after reset resulted in 1770x1000, which is an underscan. Trying something else, using CRU to insert 1780x1010 and running CRU reset results in "Invalid Format". Rebooting takes the setting back to 1920x1080 or 1770x1000 (it varies). Selecting 1780x1010 in PC Settings/Display results in Invalid Format.

It looks like Version 1709 is responding differently to CRU.

***ToastyX*** · 01-05-2018, 08:00 AM

(01-04-2018 10:22 PM)IanL Wrote: Thanks for your reply. The graphics card is ATI Radeon HD 3450, Hardware ID PCI/VEN_1002&DEV_95C5&SUBSYS_E670174B&REV_00. It was working well on Win 10 Version before 1709, and the problem arose straight after the update to V1709. The driver is 8.970.100.9001 dated 13/1/2015. I've tried "Update Driver", but Windows reports the best driver is installed.

The reboot after reset resulted in 1770x1000, which is an underscan. Trying something else, using CRU to insert 1780x1010 and running CRU reset results in "Invalid Format". Rebooting takes the setting back to 1920x1080 or 1770x1000 (it varies). Selecting 1780x1010 in PC Settings/Display results in Invalid Format.

It looks like Version 1709 is responding differently to CRU.

It's more like the driver doesn't fully support the latest version of Windows 10. That card is too old and not even officially supported in Windows 10 by AMD, so the available driver might not have all the functions. The driver that Windows installs doesn't even have the control panel, so you can't control things like underscan. You really need a new video card, at least 7000-series or newer for the latest version of Windows 10.

IanL · 01-05-2018, 04:30 PM

(01-05-2018 08:00 AM)ToastyX Wrote:
(01-04-2018 10:22 PM)IanL Wrote: It looks like Version 1709 is responding differently to CRU.
It's more like the driver doesn't fully support the latest version of Windows 10. That card is too old and not even officially supported in Windows 10 by AMD, so the available driver might not have all the functions. The driver that Windows installs doesn't even have the control panel, so you can't control things like underscan. You really need a new video card, at least 7000-series or newer for the latest version of Windows 10.

Many thanks for that tip. I found an unused 6450 on a dusty bookshelf (no recollection of buying it!) and saw from the AMD website that it supports all but DirectX 12 in Win 10. So I gave it a try, downloaded the Catalyst Drivers and it's all good. Overscan adjusted out and all well Wink

Coloneltreavy · 01-07-2018, 11:07 PM

Hi there,

I have a HP envy sleekbook 4 and just recently bought a lenovo l27q which supports resolution of 1440p@60 Hz. However, I can not get the resolution higher than 1920x1200. Tried everything pretty much and later got to learn about CRU. My laptop has hdmi 1.4b and the user manual states that the resolution is at 1920x1200 max.

So I first ran the patcher for the driver, rebooted my laptop and ran CRU app. The default it has in detailed resolutions is 2560x1440 @ 60 Hz (241.7 MHz) and then I tried restart.exe and also restart64.exe since the former didn't work. However, even that didn't bring in the custom resolution of 1440p so I tried the extension block but yet again, to no avail. The resolution it shows is 1920x1200.

Maybe I am not setting up the CRU correctly. Could someone guide me through what I did wrong>