Threaded Mode | Linear Mode

***ToastyX*** · 11-13-2022, 01:30 AM

(11-13-2022 12:39 AM)DeathLord1969 Wrote: I have tried EDID 2.0 before with no luck.
Ran that patch, was able to set 1920x1440. Then tried 2560x1440 with no luck.

Don't use the patch. You don't need the patch. Did you set the max TMDS clock to 340 MHz? Did you add the HDMI 2.0 data block?

The EDID you posted is not correct for a 3840x2160 display. It's a generic EDID for the MStar scaler, which is why the name says "MStar Demo." I don't know if the factory somehow forgot to write the correct EDID, or if they intentionally limited the HDMI 1.4 EDID to 1920x1080 and didn't change the name. HDMI 1.4 can only do 3840x2160 @ 30 Hz or 60 Hz with YCbCr 4:2:0. The HDMI 2.0 EDID is supposed to have what's needed without any changes.

I want to see what the EDID is for both the 1.4 and 2.0 options. To make this easier so I can see the original EDID without any CRU changes, use this: https://www.monitortests.com/forum/Threa...yID-Writer

Set the EDID to 1.4 and reconnect the display or restart. Then run EDWriter, click the "Read EDID" button, and click the "Save EDID..." button to save the EDID to a file. Then close EDWriter. Then set the EDID to 2.0 and reconnect the display or restart. Then run EDWriter and do the same as above. Then post both files here.

DeathLord1969 · (Last edited: 11-13-2022, 02:07 AM by DeathLord1969)

(11-13-2022 01:30 AM)ToastyX Wrote:
(11-13-2022 12:39 AM)DeathLord1969 Wrote: I have tried EDID 2.0 before with no luck.
Ran that patch, was able to set 1920x1440. Then tried 2560x1440 with no luck.
Don't use the patch. You don't need the patch. Did you set the max TMDS clock to 340 MHz? Did you add the HDMI 2.0 data block?

The EDID you posted is not correct for a 3840x2160 display. It's a generic EDID for the MStar scaler, which is why the name says "MStar Demo." I don't know if the factory somehow forgot to write the correct EDID, or if they intentionally limited the HDMI 1.4 EDID to 1920x1080 and didn't change the name. HDMI 1.4 can only do 3840x2160 @ 30 Hz or 60 Hz with YCbCr 4:2:0. The HDMI 2.0 EDID is supposed to have what's needed without any changes.

I want to see what the EDID is for both the 1.4 and 2.0 options. To make this easier so I can see the original EDID without any CRU changes, use this: https://www.monitortests.com/forum/Threa...yID-Writer

Set the EDID to 1.4 and reconnect the display or restart. Then run EDWriter, click the "Read EDID" button, and click the "Save EDID..." button to save the EDID to a file. Then close EDWriter. Then set the EDID to 2.0 and reconnect the display or restart. Then run EDWriter and do the same as above. Then post both files here.

I am missing something as I can't find where to set TMDS.
EDIT: I messed something up as MW2 is now grainy as hell.

***ToastyX*** · 11-13-2022, 02:07 AM

(11-13-2022 01:48 AM)DeathLord1969 Wrote: I am missing something as I can't find where to set TMDS.

It's in the HDMI data block, but something weird is going on. The two EDIDs you just posted don't match what you sent me before. These two have the correct resolutions and data blocks. What was the EDID option set to before? Leave it at 2.0. Then run reset-all.exe and reboot so it uses the new EDID instead of the one you're editing.

DeathLord1969 · (Last edited: 11-13-2022, 02:15 AM by DeathLord1969)

(11-13-2022 02:07 AM)ToastyX Wrote:
(11-13-2022 01:48 AM)DeathLord1969 Wrote: I am missing something as I can't find where to set TMDS.
It's in the HDMI data block, but something weird is going on. The two EDIDs you just posted don't match what you sent me before. These two have the correct resolutions and data blocks. What was the EDID option set to before? Leave it at 2.0. Then run reset-all.exe and reboot so it uses the new EDID instead of the one you're editing.

I am now running at 3840x2160.
There is now all the reses from 800 to 4xxx.

***ToastyX*** · 11-13-2022, 02:29 AM

(11-13-2022 02:12 AM)DeathLord1969 Wrote: I am now running at 3840x2160.
There is now all the reses from 800 to 4xxx.

Whatever the TV was set to before was sending a bogus EDID. That was the actual problem.

You can get rid of 4096x2160 by editing the HDMI and TV resolutions data blocks in the CTA-861 extension block.

DeathLord1969 · 11-13-2022, 02:42 AM

(11-13-2022 02:29 AM)ToastyX Wrote:
(11-13-2022 02:12 AM)DeathLord1969 Wrote: I am now running at 3840x2160.
There is now all the reses from 800 to 4xxx.
Whatever the TV was set to before was sending a bogus EDID. That was the actual problem.

You can get rid of 4096x2160 by editing the HDMI and TV resolutions data blocks in the CTA-861 extension block.

I appreciate the help in solving this. Been driving me nuts for awhile.

Setrern · 11-13-2022, 08:59 AM

Hi Toasty I really appreciate all the help. I’m using Nreal Air glasses. In Linux with xrandr I’m able to increase the pixel clock up to 286.5.

However in windows with CRU I can only increase the pixel clock up 216MHz. Anything higher than this, the refresh rate doesn’t show for me in Windows.

Is there anyway for me to raise the pixelclock to 286.5 using Windows?

mbsbobo · (Last edited: 11-14-2022, 05:25 PM by mbsbobo)

(11-07-2022 08:01 PM)ToastyX Wrote:
(11-06-2022 05:54 PM)mbsbobo Wrote: Quite correct but it did flicker with mouse in both these apps. The monitor isn't the problem as I have no issues in Win10Pro. The issue is with the way the driver side in Windows 11 with the new added graphics portions which can be found here
The monitor is absolutely the problem. It can't handle large changes in refresh rate without flickering. Disabling VRR or increasing the low end of the range defeats the purpose of having VRR in the first place.

Hi Toasty,

Further troubleshooting steps prove to be useful and finding results.
This may be helpful for those who have this same problem.

For:
Nvidia Control Panel settings.
for 'Set up G-SYNC'
1 Apply Following changes.
Enable G-SYNC, G-SYNC Compatible
Enable for full screen mode
Enable for windowed and full screen mode

2 Select the display you would like to change
Image of a Display icon w/nomenclature model

3 Display Specific settings.
Enable settings for the selected display model

!This monitor is not validated as G-SYNC Compatible.

Description:
G-SYNC, G-SYNC Compatible allows your enabled monitor to stay in sync with your games render rate, increasing smoothness and reducing latency.

Typical usage scenarios:
Most useful for games that have variable render rates below the peak refresh rates of your monitor.

The Settings Selected:
For Number 1 Option in the Menu
By setting #1 to 'Enable for full screen mode' -> the flickering ceases.
By setting #1 to 'Enable for windowed mode and full screen mode' -> flickering begins.

The problem is either the Nvidia driver or Windows side. The monitor itself is like a dummy that obeys its master. Once it is set it does what it is made for.
No apps in full screen mode should flicker regardless. Should default to the highest refresh rate and stay there in Desktop mode.

Remember that the Nvidia settings are centric to 3D modes --gaming graphics.
Windows apps along with Windows itself should retain any refresh the graphics card and monitor agree on. Handshake if that's the case in coexisting master slave.

The problem occurs on certain apps when using such as Notepad, OneNote and a few others.

I did return the V Hz to 48hz.

The drivers and windows should recognize the difference and make it so. But this is not happening on certain apps in Windows on 2D mode.

Thus either the apps themselves should be made and the need to have set in them some setting --if not already-- and the ability to run at the highest refresh rate without bobbling up and down on the scale. Windows in actuality should make this distinction and run accordingly. The apps are not 3D games.

It may also correlate to the Settings app for Windows Gaming Mode set to 'Gaming mode' while in non-gaming mode.

Maybe you could influence this problem to those who can think and act?
Perhaps you may have some influence with your rocking and rolling CRU app that is really sweet.

Also I really like your app and your candor along with continued support.

Have a wonderful week Heart

***ToastyX*** · 11-15-2022, 02:44 AM

(11-14-2022 05:10 PM)mbsbobo Wrote: The Settings Selected:
For Number 1 Option in the Menu
By setting #1 to 'Enable for full screen mode' -> the flickering ceases.
By setting #1 to 'Enable for windowed mode and full screen mode' -> flickering begins.

The problem is either the Nvidia driver or Windows side. The monitor itself is like a dummy that obeys its master. Once it is set it does what it is made for.
No apps in full screen mode should flicker regardless. Should default to the highest refresh rate and stay there in Desktop mode.

I don't know why you're defending a broken monitor. Return the monitor and get a different model that isn't broken. Doing all these tricks just hides the problem and doesn't actually solve the problem.

***ToastyX*** · 11-15-2022, 02:44 AM

(11-13-2022 08:59 AM)Setrern Wrote: Hi Toasty I really appreciate all the help. I’m using Nreal Air glasses. In Linux with xrandr I’m able to increase the pixel clock up to 286.5.

However in windows with CRU I can only increase the pixel clock up 216MHz. Anything higher than this, the refresh rate doesn’t show for me in Windows.

Is there anyway for me to raise the pixelclock to 286.5 using Windows?

216 MHz is the limit for 4-lane DisplayPort in Reduced Bit Rate (RBR) mode with 8 bpc color, so you're probably getting 6 bpc color in Linux, which would allow up to 288 MHz. You'll have to change the color depth to 6 bpc using your GPU's control panel.