(02-27-2019 04:50 PM)victorvvddvv01 Wrote: [ -> ]reset all worked. I checked the monitor and it's running in displayport 1.2. Sadly, the 4K 30hz issue is still present. I tried the same monitor with another system that has a nvidia 1060 - no issues there with 4K 60hz. I feel so sad.
This has to be a driver bug then, possibly caused by having that HDMI data block, so the driver is limiting the connection to HDMI 1.x speeds. Try adding an HDMI 2.0 data block (and leave the HDMI data block there). If that doesn't work, export a file and attach it here so I can look at it.
(02-27-2019 05:50 PM)victorvvddvv01 Wrote: [ -> ]I added the hdmi 2.0 - i'm getting the same nerfed 30hz resolution.
Don't add it in a separate extension block. It should be in the first extension block.
(02-27-2019 06:02 PM)ToastyX Wrote: [ -> ] (02-27-2019 05:50 PM)victorvvddvv01 Wrote: [ -> ]I added the hdmi 2.0 - i'm getting the same nerfed 30hz resolution.
Don't add it in a separate extension block. It should be in the first extension block.
Sorry about that - i added hdmi 2.0 to the extension block. I still cant get past 30hz. Please see config bellow:
https://www.sendspace.com/file/bzux0u
(02-27-2019 06:31 PM)victorvvddvv01 Wrote: [ -> ]Sorry about that - i added hdmi 2.0 to the extension block. I still cant get past 30hz.
I checked the EDID, and it's already set to the correct information for DisplayPort other than that HDMI data block. The RX 480 is capable of 4K @ 60 Hz with DisplayPort 1.2. If the monitor is set to DisplayPort 1.2 and the cable is capable, then it should work. Either the monitor is not negotiating the required HBR2 data rate for some reason, or it's a driver bug. If it's a driver bug, I'm thinking maybe the HDMI data block is what's triggering the bug and causing the driver to limit the pixel clock, but EDID overrides without that data block don't seem to be working around the problem. Perhaps try the pixel clock patch. It shouldn't do anything for DisplayPort, but maybe it will help if the driver is treating it as HDMI:
https://www.monitortests.com/forum/Threa...ck-Patcher
(02-27-2019 04:18 PM)ameoir Wrote: [ -> ]https://drive.google.com/open?id=163KzOU...DRiCHUXKjp
https://drive.google.com/open?id=1IBOCj8...xohngFbypj
exported in .bin and .txt
Try deleting 1920x1080 @ 60 Hz from standard resolutions since it's already there as a detailed resolution. Other than that, I don't see anything wrong with the EDID. I can't think of a reason why the same timing parameters wouldn't work with CRU. I was thinking maybe the monitor couldn't handle the resolution and you had GPU scaling enabled before, but that doesn't explain why the same timing parameters work with the NVIDIA control panel. Check the monitor's OSD to see what resolution it's receiving. When you test the custom resolution with the NVIDIA control panel, does the monitor report that it's receiving the custom resolution or does it report a different resolution?
Thanks - I tried it but, as you said, it didnt do anything. It seems that AMD has become truly retarded. I wish i hadnt been so poorly inspired back in 2015 when i bought this "flagship". Guess that all that i can do right now is buy a nvidia. It's really sad because i could not care less about the number of frames - yet, i cant work in 30hz - it feels more like swimming lol.
(02-27-2019 08:54 PM)ToastyX Wrote: [ -> ] (02-27-2019 04:18 PM)ameoir Wrote: [ -> ]https://drive.google.com/open?id=163KzOU...DRiCHUXKjp
https://drive.google.com/open?id=1IBOCj8...xohngFbypj
exported in .bin and .txt
Try deleting 1920x1080 @ 60 Hz from standard resolutions since it's already there as a detailed resolution. Other than that, I don't see anything wrong with the EDID. I can't think of a reason why the same timing parameters wouldn't work with CRU. I was thinking maybe the monitor couldn't handle the resolution and you had GPU scaling enabled before, but that doesn't explain why the same timing parameters work with the NVIDIA control panel. Check the monitor's OSD to see what resolution it's receiving. When you test the custom resolution with the NVIDIA control panel, does the monitor report that it's receiving the custom resolution or does it report a different resolution?
I put 1444x1080 and it works through nvidia control panel and it is 1444x1080. My monitor settings menu is really bad... when it goes out of range it just says to "set to supported resolution 1920x1080@60hz" Maybe nvidia is doing GPU scaling where CRU is doing monitor scaling or something else? Im very bad when it comes to to this topic. It used to work in CRU with 1444x1080. I will remove 1920x1080 from standard resolution and will play with scaling when I get home
(02-27-2019 09:22 PM)ameoir Wrote: [ -> ] (02-27-2019 08:54 PM)ToastyX Wrote: [ -> ] (02-27-2019 04:18 PM)ameoir Wrote: [ -> ]https://drive.google.com/open?id=163KzOU...DRiCHUXKjp
https://drive.google.com/open?id=1IBOCj8...xohngFbypj
exported in .bin and .txt
Try deleting 1920x1080 @ 60 Hz from standard resolutions since it's already there as a detailed resolution. Other than that, I don't see anything wrong with the EDID. I can't think of a reason why the same timing parameters wouldn't work with CRU. I was thinking maybe the monitor couldn't handle the resolution and you had GPU scaling enabled before, but that doesn't explain why the same timing parameters work with the NVIDIA control panel. Check the monitor's OSD to see what resolution it's receiving. When you test the custom resolution with the NVIDIA control panel, does the monitor report that it's receiving the custom resolution or does it report a different resolution?
I put 1444x1080 and it works through nvidia control panel and it is 1444x1080. My monitor settings menu is really bad... when it goes out of range it just says to "set to supported resolution 1920x1080@60hz" Maybe nvidia is doing GPU scaling where CRU is doing monitor scaling or something else? Im very bad when it comes to to this topic. It used to work in CRU with 1444x1080. I will remove 1920x1080 from standard resolution and will play with scaling when I get home
It seems that I fixed it..? I put same timings as 1920x1080 but 1444x1080 and it works...weird?
Changing refresh rate to anything other than 60 in CRU makes it go out of range...zzzz so many issues.
Not a big concern because my monitor won't go above 67hz so I'll be just using 60hz. But yes I got 1444x1080 work with 1920x1080 timings in CRU