[SirRockALot]

I’d really appreciate this. Acer support (both local & Twitter) is really spectacularly unhelpful and unresponsive:

[sblantipodi]

@ PCM2 I sent you the email.

To sum up what are the main firmware issues on the X32FP?
We can try to create a list and submit it to Acer asking for a review…

1) Adapive dimming is a global setting and does not stick with HDR/SDR.
If you want to use HDR with adaptive dimming and SDR without adaptive dimmining, you need to change the adaptive dimming setting every time you switch between HDR and SDR.

2) PS5 / HDR issues.

… feel free to add….

[PCM2]

Thanks – much appreciated.

[SirRockALot]

Thanks a lot everybody!

Good idea submitting multiple issues at once. I’d add this:

1.) The monitor also does not save settings per-input. The profile feature is useless because it doesn’t save important settings like the local dimming one. The hotkey feature is also mostly useless because again you can’t put important things like local dimming on a hotkey. They really covered all their bases to make sure switching between say gaming and desktop or a console and a computer is as painful as possible and requires manually reconfiguring the monitor.

2.) Rtings has just retested the X32 FP with the PS5 and updated their review with the HDR issue:
https://www.rtings.com/monitor/reviews/acer/predator-x32-fpbmiiiiphuzx#test_9241
Might be useful to have this problem confirmed by a reviewer so it’s not just random people on the internet claiming this

3.) Rtings also says about the X32 FP + Mac: “HDR is very washed out and dark, to the point where it’s unusable. VRR works in the desktop, but games have a lot of flickering, and the screen sometimes goes black. It’s better to disable VRR and HDR altogether with macOS.”

4.) There’s a general buggyness when it comes to multiple devices. When switching between sources and modes I’ve noticed that sometimes the overdrive setting changes without it being reflected in the menu. There’s massive overshoot but it’ll say ‘Normal’. Switching it to ‘Extreme’ and back to ‘Normal’ fixes things. I sometimes have an issue where switching back to my computer that there’s significant white crush. I never found the setting that causes this, but power cycling the monitor fixes it. Not sure if it makes sense to include these issues as I don’t have perfect step-by-step reproduction.

5.) I’m not sure there’s anything a software update could do, but this is not a typical level of image retention for an IPS: https://i.imgur.com/SxAyrgr.jpg

6.) At least by the standards of FALD TVs the local dimming algorithm is quite poor. There’s a setting that has zone smear, two with zone flicker and generally the backlight takes too long to react in any setting. Watch a movie where there are cuts between dark and bright scenes and you can see the backlight quickly light up and dim down after the cut.

In other news, my X32 FP just developed a defect. There’s now a piece of dirt between the LCD and the backlight layer. Why does this kind of thing always happen after the return window? I don’t have high hopes this monitor will last long.

[PCM2]

What refresh rate were you running the monitor at when you observed that image retention and how long did it take running the monitor “normally” for it to disappear? And are you sure that dirt wasn’t always there, but you didn’t notice it? I’m not sure how an issue like that can “form”, unless there was something stuck elsewhere, perhaps beneath the panel border, and was dislodged over time. Either way I’m sorry to see that, definitely not something you want to see!

I’d also add that the backlight generally doesn’t take too long to transition its zones between brightness levels or for the brightness levels to stabilise on the X32 FP. In fact if it did, you wouldn’t see any flickering which is due to very rapid and abrupt brightness changes. Extreme contrast transitions such as those you might observe when changing from a very bright to very dark scene in a movie are indeed slower in comparison, but I didn’t find even those transitions to be abnormally slow for an FALD solution. Or not for an IPS model at least, where the transition is more extreme due to it needing to dim the zones significantly more than a VA would to display dark (but non-black) shades ‘convincingly’. Based on feedback from users this isn’t widely complained about, either – this includes direct feedback I’ve received from those who use the monitor extensively for watching movie content. I’m not sure how much of that particular issue is down to the FALD algorithm and how much would be related to a panel limitation, either.

[SirRockALot]

60Hz and it takes 5-10min for that kind of retention to disappear. Generally the image retention on this screen is very noticeable. I was just looking at a schematic and I can still read it on a dark grey background.

I’m 100% sure this dirt or whatever it is wasn’t there before. I checked the monitor very carefully when I received it and then checked it again with all the usual solid color backgrounds the day before the return window closed :/ I have a TV that has the exact same issue, some kind of dark dot on a layer deeper into the monitor. But that TV got it after >10 years, not one month.

[Weissrolf]

I tried to replicate the image retention by leaving this forum untouched for 15 minutes (including the black on white”PC Monitors” avatar), but haven’t been able to. For that I specifically used 60 Hz, because it was mentioned and that refresh-rate seems to be problematic. I am getting vertical “scanlines” at 60 Hz on my X32.

> In fact if it did, you wouldn’t see any flickering which is due to very rapid and abrupt brightness changes.

One problem of current local dimming algorithms is that they seemingly tend to switch a new zone to higher brightness first and then have it dim down again. This is obvious in those white moving square on black background tests. The X32 flickers less the lower you set its LD and on all levels flickers less than the more aggressive/bright biased Asus PG32UQXR.

Concerning dark HDR: I wasn’t able to enable HDR on a connected Macbook Pro (other than via bootcamped Windows 10). But overall the X32 benefits considerably from running Windows 11′ HDR calibration tool (needs to be downloaded via MS Store). I also noticed a bug concerning HDR brightness: when you set Brightness to 97-100 in HDR mode then the X32 decreases brightness over the course of a few seconds, often unnoticed due to its slow ramping down. If this happens and you decrease (!) its brightness setting to 96 then it suddenly jumps back up again. So it gets considerably dimmer than 96 when it happens. Sometimes those jumps up and down seem to happen on their own. Currently I consider setting Brightness below 97 (up to including 96) to fix that behavior.

[PCM2]

Thanks for sharing your feedback, Weissrolf (and also your contribution to this thread via YouTube comments). I didn’t personally find the Windows 11 calibration tool all that useful as it’s really far too limited in its adjustments (using a single patch size plus full screen) and for obvious reasons unable to overcome the algorithmic behaviour of the monitor and its propensity to dark bias. Then again, it is absolutely worth trying and depending on HDR implementation in a game and how limited the in-game calibration options could certainly still be beneficial in some cases, giving a bit of an uplift.

The brightness bug you mention is very interesting. I didn’t notice this myself, but that’s not to say it wasn’t happening on my unit. If it did happen it would be very content-dependent as it certainly didn’t trigger when HDR brightness tests were performed, which included similar peak behaviour and sustained behaviour even when measured after 30 seconds or longer. If others with the monitor could make some observations in game and see if setting the brightness to ’96’ seems brighter than ‘100’ at times, that would be helpful. 🙂

[Weissrolf]

Concerning the HDR Calibration tool: From what I observed the clipping points (bright sliders) in the tool do make a difference. It affects both the brightness of lower to medium mids and the clipping of highlights. If you set the slider higher than the clipping point then highlights will clip more, but everything else will pop more (less dull).

Crank the saturation slider in the tool also affects SDR content, so this is something to be aware of (and I prefer more saturation over dull sRGB).

The Brightness behavior happens regardless of content, even just enabling HDR for the desktop or showing a fullscreen SDR white (255) or black (0) image. Just set Brightness to 97(-100), wait a few seconds and then set it to 96, that produces an instant increase (!) in brightness with the step to 96. This only seems to happen in HDR mode, though.

If it is specific to my unit then maybe the vertical scanlines (more pronounced when combining 60 Hz with HDR) and VRR blackouts (reported by at least one other user) may also be connected. I have to return the Asus and Corsair first and deal with the Acer afterwards (as I prefer it to the other offers).

The AOC PD32M (Porsche design) would be a viable alternative in the price-range of the Asus, but it is reported to produce coil whine (including from the LTT reviewer currently having one in house). My Acer X32 is dead silent with all modes and settings from what I can tell yet.

[PCM2]

What you’re describing with the HDR Calibration Tool is dragging up and over-brightening content so that shades are sufficiently bright to avoid triggering dark biasing from the algorithmic dimming. That may be an acceptable compromise for some people I suppose, but I found if I set things up like that it adversely affected the image not just by clipping highlights but by significant over-brightening of shades across a broad range. I didn’t find this an attractive compromise, but it’s again something I’d recommend people experiment with and judge for themselves. Definitely worth playing around with for Windows 11 users.

The scanlines (or dynamic ‘interlace pattern artifacts’) were also something I observed and others have mentioned in this thread, I doubt they vary between units. As for the AOC PD32M, the local dimming solution is unresponsive and leaves significant ‘laggy’ haloing in some scenes. This has been reported even with the latest firmware, which improves the situation somewhat but in no way brings it up to the level of something like the X32 FP.

[Weissrolf]

I don’t recommend going overboard, though. Using Gamma is another possible workaround for the X32 getting too dark (2.2 down to 2.0 via OSD in SDR, or 1.0 up to 1.1 via Nvidia driver in SDR/HDR).

These changes are small enough to not clip highlights visibly. And while they hardly make any difference to the dark biased dimming algorithm they allow more of the dimmed light to go through at least without affecting peak brightness (contrary to the brightness setting).

I sent a detailed (and lengthy) report/request to Acer support concerning the various hardware/firmware problems I encountered with my X32 FP. Since I definitively prefer the Acer over the Asus PG32UQXR I hope that some of these might be fixable via firmware updates (which Acer has provided multiple of in the past) or replacement of my unit. Let’s see how responsive their German support turns out to be.

Problems reported:
Massive VRR dropouts (up to the panel turning off intermittently), vertical lines at lower refresh-rates, massive backlight bleeding on my particular panel unit (more areas and stronger than the same panel on the Asus).

Feature requests added:
Allow Acer software to change brightness in HDR mode and to change LD levels, an intermediate OD step between “Off” and “Normal”, an additional “Fastest” LD level that is less dark biased at the cost of more blooming, ability to turn of the power LED via OSD, allowing to use the Gamma setting in HDR mode.

[Weissrolf]

The VRR dropouts and vertical “scanlines” situation lead me to run games at fixed refresh-rate via VSync + Reflex for the time being. VRR issues can be worked around by disabling DSC and manually making 120 Hz at full RGB 8-bit work. But the vertical lines are even visible at 120 Hz, which may fit the aesthetics of something like Starfield, but still is a nuisance.

[Weissrolf]

For those having problems with the PS5 (or Mac OS HDR):

What I noticed is that when the monitor gets Brightness changes sent via DDC/CI then it switches to User mode and drops considerably in brightness. Unfortunately I own no PS5 to test this myself, but maybe the PS5 sends brightness commands to the monitor via DDC/CI and thus makes it switch to User mode and drop down to SDR brightness despite still claiming to be in HDR range.

Anyone experiencing this should check if the monitor changes into “User” mode instead of “HDR”. If so then try to turn it off and on again and watch if stays in HDR then or switched back to User after some time. Alternatively try switching Picture -> HDR between “Off” and “Auto” to make it jump back into HDR mode.

On Windows you can also fix this via Acer’s own software tool by switching back to HDR mode via that software. Unfortunately this does not work via OSD for “Modes”, so that one is a Windows only solution. On the other hand you cannot change Brightness via Acer’s Windows tool in HDR mode while the OSD allows to do just that. So changing brightness via DDC/CI seems to mess up that whole part of the system. DDC/CI can also be disabled via OSD, so that could rule out any problems of that kind.

[PCM2]

Appreciate the investigation and also possible solutions there, that’s very useful information. 🙂 Do you notice the ‘spontaneous HDR dimming issue’ if you have Acer Display Widget closed (and perhaps uninstalled), or is it not related to that being accessible by the monitor? And to double-check, is this issue only observed on your MacBook (Bootcamped) or did you confirm this bug on a Windows PC?

[Weissrolf]

This is all on a Windows desktop PC using a NVidia 2070 Super, as MacOS doesn’t even offer HDR when the X32 is connected to my 2017 Intel Macbook Pro via either TB-HDMI or TB-USBC cable.

1. The Acer Display Widget does *not* allow to change brightness when HDR mode is enabled. The option is grayed out.
2. Changing brightness via OSD works as expected, except for brightness levels 97-100 gradually getting dimmer after some seconds. Using 96 or lower fixes the latter.
3. Using third party applications (like Twinkle Tray) to change brightness via DDC/CI while the X32 is in HDR mode causes the monitor to switch to (SDR) “User” mode and drop brightness *considerably* even at level 100. This can be fixed by turning the monitor off -> on, switching HDR back and forth to off -> Auto or clicking the HDR mode button in Acer Display Widget (despite it claiming to already be in HDR).

If the HDR brightness issues reported by PS5 users is DDC/CI based (PS5 sending brightness commands) then turning off DDC/CI via OSD should be a viable workaround.

Sorry, I forgot: uninstalling the Acer Display Widget makes no difference for this.

And a warning: when you switch HDR back and forth between OFF and Auto via OSD then not only does the brightness get reset to 100, but “Super Sharpness” gets activated. So turning the monitor off and on again is the better workaround (also helps when switching DSC off/on gets the GPU driver confused and likely in other situations).

[Weissrolf]

Since Amazon does only offers refunds and repair, but not replacement, I ordered a second X32 FP unit (new, but B stock, for 1050 EUR). Acer did not answer my support request yet that I asked on September 8th, they only informed me that they forwarded the case.

Today had had a case where the whole screen was flickering with the combination of VRR game in the background and non fullscreen windowed Discord in the foreground. Once that started it also kept happening for fullscreen Edge windows. Once I disabled Freesync it stopped and then didn’t return again, but it’s something to keep an eye on, especially because turning the monitor off and on again did not fix it.

Worth mentioning that I am currently using tight manual timings/blanking to push 120 Hz at full RGB 8-bit without DSC to workaround the DSC induced VRR dropouts. So that may contribute to the flickering phenomena I experienced today.

[Rakni]

Hi all,

I have the X32 FP since last Friday and so far I like it. I followed all the discussions around the various forums and Reddit and just wanted to give information about my model. I updated the firmware to the newest after the monitor arrived and connected it with DP to my 4090. I tried to replicate all the problems I have read about but couldn’t replicate them.

– drop outs with VRR do not appear currently. I tried various games with different performance profiles and the Nvidia pendulum demo but couldn’t bring my monitor to drop the signal

– Dimming the brightness at or above 97 brightness does not happen with my model, I tried it in SDR and HDR but it never dimmed or brightened up when I changed the brightness to 96. I tried it with the HDR brightness test used in the review and in the game A Plague Tale: Requiem.

I had the PG32UQXR here but it was a total dud because it was loud as hell the moment you activated HDR and it flickered like crazy when dark content had strong light sources like lamps visible.

Now I’m trying to decide which to keep. Aw3423dwf which I have here and really liked as long as ABL didn’t kick in. Or the X32 which didn’t “pop” as much in dark content but does not really have a problem with sustained brightness.
Furthermore it feels like, that the X32 has much more potential with firmware updates compared to the AW3423DWF, but I’m not sure about this because I don’t know if it is possible to simply change the dark biasing and such with software only.

[PCM2]

Thanks very much for sharing your experiences with those monitors Rakni and also confirming that you couldn’t replicate those bugs on the X32 FP. Much appreciated. 🙂

[Weissrolf]

My second X32 FP hopefully arrives this week already, so I can try to replicate the VRR and HDR brightness issues on that one. VRR + DSC massively dropping out (I don’t have to try hard) may also be connected to using the 2070 Super. The same did not happen with the PG32uqxR connected to the same card, though, so trying a second X32 unit hopefully will clarify that part.

It would be great if someone with a PS5 could test disabling DDC/CI for the low HDR brightness issues with the PS5 (or check if the monitor goes into User mode then).

[Rakni]

I can connect my Ps5 later today and report back !

[Author]

Posts