Samsung odyssey G7 CRU Hz issue
|
08-27-2020, 06:04 AM
Post: #1
|
|||
|
|||
Samsung odyssey G7 CRU Hz issue
I am new to using cru and am having some issues. I currently have the Samsung odyssey g7 32 which runs up to 240hz at 1440. I have gone through windows and changed the settings to 240...however cru is showing that I'm running 1440 at 59hz. The monitor is also set to 240hz. Now when I change the settings on the monitor to any other hz - 60/120/144 it changes in cru accordingly. But as soon as I change the monitor to 240, cru drops back to 59hz. When I try to change it, cru only lets me change to 144hz max...and will not allow me to enter 240. What can I do about this? Why won't it let me change my Hz to 240? Thanks in advance
|
|||
08-27-2020, 02:15 PM
Post: #2
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
CRU doesn't show the current resolution. It shows what's in the EDID. It's not possible to define 2560x1440 @ 240 Hz with an EDID detailed resolution because the pixel clock is limited to 655.35 MHz. 240 Hz is probably in the second extension block, which should be a DisplayID extension block. DisplayID detailed resolutions have higher limits. If you have an NVIDIA card, CRU can't read the second extension block because the driver won't provide it for some reason. AMD cards should be fine. If you want to make any changes with NVIDIA, you'll have to delete any default extension blocks and add a DisplayID extension block manually. Then you can add 2560x1440 @ 240 Hz in there.
|
|||
08-27-2020, 04:32 PM
Post: #3
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(08-27-2020 02:15 PM)ToastyX Wrote: CRU doesn't show the current resolution. It shows what's in the EDID. It's not possible to define 2560x1440 @ 240 Hz with an EDID detailed resolution because the pixel clock is limited to 655.35 MHz. 240 Hz is probably in the second extension block, which should be a DisplayID extension block. DisplayID detailed resolutions have higher limits. If you have an NVIDIA card, CRU can't read the second extension block because the driver won't provide it for some reason. AMD cards should be fine. If you want to make any changes with NVIDIA, you'll have to delete any default extension blocks and add a DisplayID extension block manually. Then you can add 2560x1440 @ 240 Hz in there. Awesome thank you! So even though it shows 144hz is should actually be running at 240? |
|||
08-27-2020, 08:30 PM
Post: #4
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(08-27-2020 04:32 PM)Styles 2420 Wrote: Awesome thank you! So even though it shows 144hz is should actually be running at 240?It should be running at whatever you have set in the Windows display settings. Try this: https://www.displayhz.com/ |
|||
08-28-2020, 05:55 AM
Post: #5
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(08-27-2020 08:30 PM)ToastyX Wrote:(08-27-2020 04:32 PM)Styles 2420 Wrote: Awesome thank you! So even though it shows 144hz is should actually be running at 240?It should be running at whatever you have set in the Windows display settings. Try this: https://www.displayhz.com/ Awesome! Thanks for the info |
|||
01-01-2021, 12:07 PM
(Last edited: 01-01-2021, 12:27 PM by TheSuspect83)
Post: #6
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(08-27-2020 02:15 PM)ToastyX Wrote: CRU doesn't show the current resolution. It shows what's in the EDID. It's not possible to define 2560x1440 @ 240 Hz with an EDID detailed resolution because the pixel clock is limited to 655.35 MHz. 240 Hz is probably in the second extension block, which should be a DisplayID extension block. DisplayID detailed resolutions have higher limits. If you have an NVIDIA card, CRU can't read the second extension block because the driver won't provide it for some reason. AMD cards should be fine. If you want to make any changes with NVIDIA, you'll have to delete any default extension blocks and add a DisplayID extension block manually. Then you can add 2560x1440 @ 240 Hz in there. Happy New Year All @ToastyX so i added the DisplayID extension Block in CRU. Is that correct what i have done in cru what you see on my attachments? So if i finish this settings i cant add 2560x1440p @240hz Resolution in Top of Detailed Resolution, to use Display Scaling (Im on RTX 3080@460.79). So if DisplayID is added the Monitor will now work @240hz @Displayscaling? or do i have to do more edit on the settings to run this Monitor in 1440p with Display Scaling? Other thing, you say with AMD cards should be fine? so if i bought a AMD Card, CRU will correctly let me set under Detailed Resolution @2560x1440p @240hz @Display Scaling? I appriciate your Repost my Man |
|||
01-01-2021, 05:41 PM
Post: #7
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(01-01-2021 12:07 PM)TheSuspect83 Wrote: so i added the DisplayID extension Block in CRU. Is that correct what i have done in cru what you see on my attachments? So if i finish this settings i cant add 2560x1440p @240hz Resolution in Top of Detailed Resolution, to use Display Scaling (Im on RTX 3080@460.79). So if DisplayID is added the Monitor will now work @240hz @Displayscaling? or do i have to do more edit on the settings to run this Monitor in 1440p with Display Scaling?Did you try it? Display scaling just means the resolution is sent to the monitor. Any resolution you add with CRU should be sent to the monitor if GPU scaling is disabled. It doesn't have to be the first detailed resolution. AMD can read the second extension block, but that doesn't change the way resolutions are added. |
|||
01-01-2021, 09:52 PM
(Last edited: 01-01-2021, 10:15 PM by TheSuspect83)
Post: #8
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(01-01-2021 05:41 PM)ToastyX Wrote:(01-01-2021 12:07 PM)TheSuspect83 Wrote: so i added the DisplayID extension Block in CRU. Is that correct what i have done in cru what you see on my attachments? So if i finish this settings i cant add 2560x1440p @240hz Resolution in Top of Detailed Resolution, to use Display Scaling (Im on RTX 3080@460.79). So if DisplayID is added the Monitor will now work @240hz @Displayscaling? or do i have to do more edit on the settings to run this Monitor in 1440p with Display Scaling?Did you try it? Display scaling just means the resolution is sent to the monitor. Any resolution you add with CRU should be sent to the monitor if GPU scaling is disabled. It doesn't have to be the first detailed resolution. AMD can read the second extension block, but that doesn't change the way resolutions are added. so after DisplayID extension block is added i dont have to add 2560x1440p under Detailed Resolution (attached File Red Marked)? I mean after restart64.exe its the Same thing that i only could set 144hz and not 240hz at 2560x1440 under Detailed Resolution. -> Maybe someone knows exactly what to do? My previous Monitor was an AOC 251Fz, and on this model you where able to change under detailed resolution the correct native resolution with 240hz. its a bit confusing on this G7. |
|||
01-01-2021, 10:21 PM
Post: #9
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(01-01-2021 09:52 PM)TheSuspect83 Wrote: so after DisplayID extension block is added i dont have to add 2560x1440p under Detailed Resolution (attached File Red Marked)? I mean after restart64.exe its the Same thing that i only could set 144hz and not 240hz at 2560x1440 under Detailed Resolution.You already added it as a detailed resolution in the DisplayID extension block. You don't need to add it in multiple places. You won't be able to add it as the first detailed resolution because of EDID limitations, but that shouldn't affect display scaling. |
|||
01-01-2021, 10:27 PM
Post: #10
|
|||
|
|||
RE: Samsung odyssey G7 CRU Hz issue
(01-01-2021 10:21 PM)ToastyX Wrote:(01-01-2021 09:52 PM)TheSuspect83 Wrote: so after DisplayID extension block is added i dont have to add 2560x1440p under Detailed Resolution (attached File Red Marked)? I mean after restart64.exe its the Same thing that i only could set 144hz and not 240hz at 2560x1440 under Detailed Resolution.You already added it as a detailed resolution in the DisplayID extension block. You don't need to add it in multiple places. You won't be able to add it as the first detailed resolution because of EDID limitations, but that shouldn't affect display scaling. ok thank you my man |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)