Threaded Mode | Linear Mode

EeK · 08-14-2017, 08:27 PM

(08-13-2017 09:06 PM)ToastyX Wrote: If you're adding lower resolutions and using GPU scaling like in the video, then the timing parameters don't matter because the resolution will be scaled to the native resolution anyway. The "LCD" options are meant for digital flat-panel monitors and TVs, basically any non-CRT.

Hi, ToastyX! Thanks for replying.

I added a couple of lower resolutions, yes. So leaving everything at Manual default settings is just fine? When should I use the "LCD" presets?

***ToastyX*** · 08-15-2017, 07:30 AM

(08-14-2017 08:27 PM)EeK Wrote: I added a couple of lower resolutions, yes. So leaving everything at Manual default settings is just fine? When should I use the "LCD" presets?

The "default" timing parameters are just the standard timing parameters for that particular resolution. Use "LCD standard" to fill in the timing parameters for another resolution.

***ToastyX*** · 08-15-2017, 07:30 AM

(08-14-2017 02:11 AM)uiuc_josh Wrote: Thanks--will try. I'm currently using a windows task that runs on every low power resume event and it runs restart64.exe, but I think that it causes issues because it's running as a non-interactive admin user and there's nobody to click exit. Are there command line options for restart64.exe I can explore?

Rename it to restart-only.exe or pass the -q option.

sevs · (Last edited: 08-15-2017, 08:31 PM by sevs)

Hi. Simple question: do you need two crossfire bridges to be able to use resolutions that are exceeding 300/330mhz pixel clock even though you have disabled crossfire in the driver settings? Or what else could be the reason to why i'm unable to set 1920*1440 at 160hz interlaced? 158hz (fieldrate 79hz) works fine.

Using Windows 7 x64, latest amd drivers, latest pixel clock patcher (maybe it's not compatible with the latest drivers (yet)?), dual 280x, two monitors connected, one to each gpu via dvi-bnc cables (VGA/RGBHV) (so no edid coming from monitors). Monitors are Eizo F931 and Eizo T960. I want to use 2048*1536i at 160hz on the F931 and try to see if 3840*2880i at 75hz or 80hz works on both of them.

I changed the monitor drivers in device manager from non-pnp to pnp, otherwise i would get crashes where the screens would continuously turn off and on and the only thing you could do was to hold power button/cut power. I think i resolved this issue now, but i'll test to make sure later.

I am using the custom resolution tool in the amd drivers because using cru turned on gpu scaling with no option to turn it off, and the custom resolution would not be displayed in the windows list all modes window, even though the khz rate etc on the monitor matched the resolution i had set in CRU. So basically the monitor reported for example 1920*1440 at 150hz interlaced, and the Windows CP would say 1600*1200 at 60hz progressive. The picture would be unsharp and obviously upscaled.

Also i have another issue where enabling Crossfire enables the output on my lower GPU instead of the upper one. Why does AMD radeon control panel identify my left monitor that is connected to the upper GPU as number 2 and the right monitor connected to my lower GPU as number 1, while the windows CP shows the opposite? Is it possible to swap primary and secondary GPU? I know i couldj ust swap the cables but my top GPU has a waterblock on it so i'd prefer for it to be the primary GPU. It wasn't like this before. This happened after reinstalling Windows and drivers.

I tried downgrading gpu drivers to resolve some of my issues, but didn't try 17.4.1 (the one matching the latest pixel clock patch version) yet. (edit: sorry, misread the post, lastest patcher should be compatible with the 17.7.2 drivers which i am using)

***ToastyX*** · 08-16-2017, 12:16 AM

(08-15-2017 10:30 AM)sevs Wrote: Hi. Simple question: do you need two crossfire bridges to be able to use resolutions that are exceeding 300/330mhz pixel clock even though you have disabled crossfire in the driver settings? Or what else could be the reason to why i'm unable to set 1920*1440 at 160hz interlaced? 158hz (fieldrate 79hz) works fine.

Using Windows 7 x64, latest amd drivers, latest pixel clock patcher (maybe it's not compatible with the latest drivers (yet)?), dual 280x, two monitors connected, one to each gpu via dvi-bnc cables (VGA/RGBHV) (so no edid coming from monitors). Monitors are Eizo F931 and Eizo T960. I want to use 2048*1536i at 160hz on the F931 and try to see if 3840*2880i at 75hz or 80hz works on both of them.

What do you mean when you say you're unable to set the resolution? What happens? You only need two CrossFire bridges if CrossFire is enabled; otherwise, some games will not load correctly, but the resolution should still be available. This is separate from the 330 MHz dual-link DVI limit. VGA supports up to 400 MHz without the patch. You shouldn't need the patch for 2048x1536i @ 160 Hz, and I don't know if the video card can even output 3840x2880i @ 75 Hz because the pixel clock would be almost 600 MHz.

(08-15-2017 10:30 AM)sevs Wrote: I changed the monitor drivers in device manager from non-pnp to pnp, otherwise i would get crashes where the screens would continuously turn off and on and the only thing you could do was to hold power button/cut power. I think i resolved this issue now, but i'll test to make sure later.

This is an AMD driver bug that affects monitors without an EDID. The driver isn't really crashing. It's getting stuck in a loop trying to detect a monitor without an EDID. Running restart.exe can break the loop if you can manage to run it, but opening Radeon Settings seems to trigger the problem again. Are you saying using the "Generic PnP Monitor" driver works around the problem?

(08-15-2017 10:30 AM)sevs Wrote: I am using the custom resolution tool in the amd drivers because using cru turned on gpu scaling with no option to turn it off, and the custom resolution would not be displayed in the windows list all modes window, even though the khz rate etc on the monitor matched the resolution i had set in CRU. So basically the monitor reported for example 1920*1440 at 150hz interlaced, and the Windows CP would say 1600*1200 at 60hz progressive. The picture would be unsharp and obviously upscaled.

AMD's driver has (or had) an option to either use the EDID or to manually set the maximum resolution and refresh rate for VGA monitors. You might need to enable that option if you're using CRU since it creates EDID overrides. I don't know if that option is still available with the latest driver because they got rid of Radeon Additional Settings. The last version with Radeon Additional Settings is 17.7.1.

Also keep in mind when adding an interlaced resolution with CRU, you need to make sure the vertical resolution is halved, so 1920x1440i would be 1920x720 and 3840x2880i would be 3840x1440. CRU automatically does this for you if you enter the resolution first before enabling the interlaced checkbox. I don't know if the vertical resolution needs to be halved with AMD's custom resolutions.

(08-15-2017 10:30 AM)sevs Wrote: Also i have another issue where enabling Crossfire enables the output on my lower GPU instead of the upper one. Why does AMD radeon control panel identify my left monitor that is connected to the upper GPU as number 2 and the right monitor connected to my lower GPU as number 1, while the windows CP shows the opposite? Is it possible to swap primary and secondary GPU? I know i couldj ust swap the cables but my top GPU has a waterblock on it so i'd prefer for it to be the primary GPU. It wasn't like this before. This happened after reinstalling Windows and drivers.

I don't use CrossFire, so I'm not sure how this works. If the driver doesn't provide a way to set the primary GPU, then I don't know if you can change it. I would assume the GPU that shows the BIOS/UEFI screen would be the primary GPU, which is usually the first PCIe x16 slot by default. The order of the monitors in the Windows display settings shouldn't matter.

EeK · 08-16-2017, 05:54 PM

(08-15-2017 07:30 AM)ToastyX Wrote: The "default" timing parameters are just the standard timing parameters for that particular resolution. Use "LCD standard" to fill in the timing parameters for another resolution.

Hello again,

Please forgive my ignorance, but I'm not sure if I follow. My display is a 4K OLED TV with a native resolution of 3840x2160. I added two (lower) detailed resolutions, for games that I can't run in native 4K at constant 60fps.

I decided for 3456x1944 (90% of 4K) and 3200x1800 (80% of 4K). I left Timing at Manual and didn't change any other settings.

This is what the detailed resolution window looks like for those resolutions:

3840x2160
3456x1944
3200x1800

Should I update the Timing to "Automatic - LCD standard" for all of the above?

Chrismartin76 · 08-16-2017, 06:12 PM

Thanks!
Under Device Manager, I have Intel HD Graphics 630 and NVIDIA GeForce GTX 1050. Both are currently enabled. I have Windows 10. The first detailed resolution is the same resolution (2560x1404) but 59.002 Hz. I also installed the HDMI extension block and the first detailed resolution there is 2560x1440 @ 59.950 Hz. When I installed the extension block, I kept the default settings because I don't understand what exactly the extension block does.

I just changed the refresh rate on both to 60.000 Hz and did a quick test. The monitor was OK after waking up. I'll post again if the problem recurs, but please let me know if I should do anything about the switchable graphics. Thanks!

Chris

(08-10-2017 10:42 PM)ToastyX Wrote:
(08-09-2017 12:07 PM)Chrismartin76 Wrote: I've got CRU working fine, but the resolution doesn't always stick. If I wake my laptop up after a period of sleep, it may or may not reset to the poorer resolution. When this happens, I run restart.exe or restart64.exe, and then set the better resolution. This resetting also happens if I disconnect my laptop from my monitor for a while or I restart my computer. I have a Dell XPS 15 and the external monitor is a Dell U2711. I've got the detailed resolution set to 2560x1440 @ 60Hz. When it resets it goes back to 1920x1080. I'm using an HDMI cable to connect the two. Can anyone help with this issue? Thanks.
That sounds like a driver bug. Does the laptop have switchable graphics (Intel+NVIDIA GPU) or does it only have the NVIDIA GPU? Are you using Windows 7? Did you make 2560x1440 @ 60 Hz the first detailed resolution?

***ToastyX*** · 08-17-2017, 06:36 AM

(08-16-2017 11:29 PM)paulobmarcos Wrote: Hey! Recently bought a 4K TV (Sony X900E) and for some strange reason (by doing a test with https://www.vsynctester.com) it seems to run at 3840x2160 59.94hz even though I select it to be 60hz. (Using a HDMI 2.0 cable in the right ports [2 or 3])

An odd thing is, sometimes, if I change between the 60hz option to 59hz and again to 60hz, the test will show that my monitor is now running at 60.00+hz.

If I restart my pc it returns back to 59.94hz. I also made a test where I have a 60fps video with a white bar going horizontally on the screen. In 59.94hz there is a slight "stutter" from time to time. But when I am lucky to actually output in 60hz, no "stutter" is visible.

I tried to mess around with CRU but nothing I do seems to make it 60hz at all cost...

Is this a Windows bug or something of some sort?

What video card do you have? Microsoft decided TV resolutions should have both 59/60 Hz available, but it's up to the graphics driver to implement this.

***ToastyX*** · 08-17-2017, 06:37 AM

(08-16-2017 06:12 PM)Chrismartin76 Wrote: Thanks!
Under Device Manager, I have Intel HD Graphics 630 and NVIDIA GeForce GTX 1050. Both are currently enabled. I have Windows 10. The first detailed resolution is the same resolution (2560x1404) but 59.002 Hz. I also installed the HDMI extension block and the first detailed resolution there is 2560x1440 @ 59.950 Hz. When I installed the extension block, I kept the default settings because I don't understand what exactly the extension block does.

I just changed the refresh rate on both to 60.000 Hz and did a quick test. The monitor was OK after waking up. I'll post again if the problem recurs, but please let me know if I should do anything about the switchable graphics. Thanks!

I asked mainly because I was trying to find out what driver was responsible. This sounds like an Intel driver bug. I'm not familiar with Intel GPUs, so I don't know if there's a workaround. You shouldn't need to define the same resolution twice. Just having it as the first detailed resolution in the main window should be enough.

Usually the default extension block already includes HDMI support, but CRU can't read the extension blocks with Intel GPUs. If the default doesn't work, I was going to suggest importing hdmi-audio.dat, but it seems you're already trying a custom extension block.

***ToastyX*** · 08-17-2017, 06:38 AM

(08-16-2017 05:54 PM)EeK Wrote: Should I update the Timing to "Automatic - LCD standard" for all of the above?

If you're using GPU scaling, then it doesn't matter. If you're not using GPU scaling, then it depends on what the TV will accept. The timing parameters you posted match the CEA-861 standard for 3840x2160 @ 30/60 Hz. That might work for other resolutions, but it wouldn't match any particular standard. "LCD standard" will use the CVT-RB standard for non-TV resolutions, but there's no guarantee any particular timing parameters will work because TVs are mainly designed to handle certain TV resolutions. Usually they can scale non-TV resolutions like monitors can. In that case, use whatever works.