Monitor Tests Forum

My screen started to fail since I increased the HZ. The screen is flickering and it overlaps:



https://www.youtube.com/watch?v=XjcZFI5-Yok

Help!

---

That happens even in the BIOS. Now I am using 60 HZ, and it doesn't work .

(07-09-2021 08:12 PM)ToastyX Wrote: [ -> ]

(07-09-2021 03:54 PM)orangpelupa Wrote: [ -> ]i copied the H rate and pixel clock from a tutorial someone posted on reddit, for a completely different monitor.

is my issue due to incorrect pixel clock and h rate? how to find the right values?

The range limits is not the FreeSync range unless it's DisplayPort, in which case it would already be filled in. Use the HDMI method: add a CTA-861 extension block and add a FreeSync data block. You will also need a 40 Hz detailed resolution.

I've added the freesync range (hdmi method) and it's still won't change the range.

Maybe because the screen is using eDP?

As the methods I've read are for DP and HDMI, but I can't find any for eDP

Edit: on a different laptop, someone managed to fiddle with freesync with a bin file it seems https://www.reddit.com/r/Amd/comments/a9...nt/ecj3714 but they didn't say anything what the bin file changes

Hi Toasty I have a question about LFC behavior on a gsync-compatible monitor.

I am working on my own diy strobed vrr solution for my VG279QM and the major barrier for single strobed vrr is LFC kicking in and sticking when i don't want it to.

for stable 60fps content LFC will remain off. but other times LFC will kick in and double frame it is very sticky and will not change back to 60hz easily.

I can set my v rate limit to 0 and disable LFC but my monitor will blankout at 24hz
only way I have been able to limit lfc sticking is with custom resolutions with lower refreshrates where LFC can't double frame.

Is LFC behavior controlled by the monitor or nvidia?

do you know of any means to control max LFC range without limiting max refresh? rate ideally i want lfc to only kick in to save the monitor from a blank out so 24hz min V rate double frame to 48hz. turn off as soon as framerate rises above 48fps.

no matter what v-rate max i use it doesn't effect LFC behavior as soon as you have a framerate dip in a loading screen for example double framing, triple framing and quad framing will occur and it is very sticky. often have to reset the resolution to get it to stop.

with LFC completely disabled vrr strobing works well but loading screens and other random things can cause monitor to blank outs.. not ideal.

here's my vrr single strobe in action

I'm willing to do anything to try and quell this lfc behavior im open to any ideas. I'm thinking hardware LFC disabled and software LFC might be the only way.

(07-11-2021 04:18 AM)elexor Wrote: [ -> ]Is LFC behavior controlled by the monitor or nvidia?

do you know of any means to control max LFC range without limiting max refresh?

It's controlled by NVIDIA, and there's no way to disable it as far as I know.

(07-10-2021 01:57 AM)orangpelupa Wrote: [ -> ]Edit: on a different laptop, someone managed to fiddle with freesync with a bin file it seems https://www.reddit.com/r/Amd/comments/a9...nt/ecj3714 but they didn't say anything what the bin file changes

He did what I said to do, so if that doesn't work, then I don't know what will.

(07-09-2021 09:08 PM)Dannypa Wrote: [ -> ]My screen started to fail since I increased the HZ. The screen is flickering and it overlaps:

How long ago did you increase the Hz?

I've got a (admittedly relatively small) 1280x1024 monitor that I like to use in summer due to it's low power consumption (~10w) and therefore low heat output that always throws up a "out of range" warning message and then subsequently puts the monitor into standby if the refresh rate is set to anything other than 60Hz or 75Hz.

But AFAICT, any refresh rate from 47Hz up to 75Hz actually works fine as something like 50Hz and 72Hz actually does show a perfectly fine looking image despite the stupid "out of range" message and subsequent standby.

Interestingly I found that, on Linux, I can take the xrandr cvt modeline for 60Hz and manually change two of the values to create a 50Hz output that doesn't result in the monitor throwing up the infamous "out of range" message and does in fact keep the monitor awake, and the same similarly worked for manually turning the xrandr cvt modeline for 75Hz to create a working 72Hz and 71.92Hz output (I've also confirmed that it's not skipping frames or the like with my custom 50Hz output).

...yet in CRU, manually tuning a detailed resolution of 50Hz to use the same timings as 60Hz or 75Hz still results in the aforementioned "out of range" message.


So yeah, how would one go about getting this to work in CRU? For reference, these are the following custom xrandr modelines that I've created:

I want to set up impossible screen modes solely to be used by windowed games spanning monitors.

I have 3 naff 1280x1024 monitors off a 1080Ti, for triplehead gaming.

Games with resizable or custom windowed sizes obviously span all 3 screens without issue..

..however many games will only offer window sizes that match the available screen mode resolutions.. in this case the standard resolutions up to 1280x1024.

So, i want to set up 3840x1024, even though i have no intention of trying to switch to it as a screen mode; - it will purely exist so that the above games will offer it as an available windowed resolution, thus to span all 3 monitors just like games with custom or resizable window resolutions.

Obviously, i'm having trouble setting up these impossible modes - the numbers get coloured red and the mode cannot be set..

Is there a workaround for this?

I found one already - simply connect a Matrox TH2G unit, and the 3840x1024 values are accepted.. except now the whole trick's redundant as the TH2G can provide such modes out of the box... obvs tho, in principle this extra hardware's entirely unnecessary if i only want a 'spoofed' standard res for spanning windowed modes.. see what i mean? I wanna be able to run without all the extra cabling and power consumption of this essentially-redundant extra peripheral..!? I already have viable triplehead hardware for spanning windowed modes!

(07-08-2021 02:32 AM)ToastyX Wrote: [ -> ]CRU only creates a description of what the monitor can do. It doesn't implement any of the functions, so that has to be a driver bug. Use the "Export..." button to save a file and attach it here so I can see if there's anything unusual about the monitor.

Sorry, had some net issues...

[attachment=767]

It's an older 1080p Sanyo TV. Very uncooperative with CRU. It seems that making any change at all and leaving it eventually causes some sort of failure, usually starting with disabling the sound over HDMI. It's not a random shutdown, I can play for hours without issue, but if I power off and on or enter and exit sleep it causes more and more problems until I need to use Reset All. Importing doesn't fix it.

I can play Luminous Avenger iX properly by deleting the default extension block and touching nothing else, as that wipes out most framerate modes in windows, including the offending 24fps one. Everything works fine, until the issues crop up.

EDIT: I'm not potentially on an "older" Intel iGPU, am I? I'm using an Intel Core i5 1035G7, and running the normal release of CRU. I don't need to do any weird extra stuff, right?

(07-11-2021 07:57 PM)ToastyX Wrote: [ -> ]

(07-09-2021 09:08 PM)Dannypa Wrote: [ -> ]My screen started to fail since I increased the HZ. The screen is flickering and it overlaps:

How long ago did you increase the Hz?

80 HZ. It was working fine, and suddenly it started doing that. I set it back to 60 hertz, but it is still there. The monitor appears to be faulty, or it has been damaged.

---

For one month, everything worked perfectly/flawlessly.