[PCM2]

Glad you’re enjoying it. It’s always nice to find a title that is really enhanced by HDR on a monitor that can put it to good use. 🙂

[sblantipodi]

New firmware has been released. The changelog is not that clear to me.
https://www.acer.com/us-en/support/product-support/X32FP/downloads

1.fix ADW customer complaint issue
2.change OD to be adjustable when freesync is on
3.change HDR behavior
4. fix customer complaint issue, fuzzy screen of PC game Witcher3

I am trying to understand what they fixed in point 1,
point 2, OD was already adjustable when freesync is on, so don’t understand this pount,
point 3, I see no change in HDR but will try to understand it,
point 4 is pretty self explanatory even if I had no problem in TW3.

[sblantipodi]

Ok, I found some photos from the old firmware update in june 2023 and it’s V02.00.015,
I flashed the firmware that I downloaded today from Acer website that reports a new release date 2024/01/04
but it’s the same version, V02.00.015.

I think that they only updated the release date on the website but the firmware is the same. -_-

[PCM2]

Yeah, I thought those release notes sounded extremely familiar.

[Weissrolf]

The PDF manuals for firmware updates were added to the .015 files, whereas before they were only found in the .010 archive.

[sblantipodi]

I have a small issue on my X32FP, once every 10 boot, more or less,
Windows starts as if the monitor is ultra wide, I can see only half of the desktop (in full screen stretched) and I need to reboot the PC to return to normality.

is there someone else ever experienced on this monitor?
using an RTX4090…

[Rakni]

Yes, the same thing happened with my x32. It was the first time and I simply had to power off and on the monitor. I didn’t investigate much but in the display settings nothing was out of the ordinary. The only thing I changed recently, was installing NVIDIA app to try out RTX HDR. Maybe it has something to do with that.

[Rakni]

AW3225QF came in and replaced the X32. I played 2 days with the aw and got no eye strain like with the 3423dwf. Brightness is enough but of course lacks the fullscreen brightness of the X32. I thought I would hate the lack of brightness but I didn’t even think about it after an hour with the AW3225QF, because everything else is so much better. Better motion clarity, better colours and no more dark biasing which destroyed so many dark details and light sources surrounded by dark shades. All in all I think it is a great display and I would buy it every time over the X32. Even if they where the same price ( the x32 is about 300 euro more here in Germany). Now I have to wait and see what’s up with burn in, because I use my monitor for work. If you want to know more I’m happy to answer your questions.

[PCM2]

Thanks for sharing your thoughts on the AW3225QF, Rakni. I’m glad you’re enjoying the experience so far. 🙂

[PCM2]

Some posts have been moved over to a new thread.

[Weissrolf]

For about 3 months I am trying to communicate with Dell/AW that the “Fast Wakeup” standby power usage of 11 W seems too high. Even more so because the feature cannot properly be disabled. Even when you disable it via OSD it stays active until you completely shutdown the PC or disconnect the monitor.

On bright days with daylight in the room I sometimes use SDR in HDR mode, combined with a Autohotkey script that sets gamma to 2.2 (adjustable via shortcuts) and allows me to change SDR brightness via shortcuts (instead of the convoluted Windows Display settings). Works quite well.

[sblantipodi]

After 1.5 years my X32FP deviated from the “original calibration”,
I can see a small greenish tint with naked eye.

With my very old Xrite i1 Color Display PRO colorimeter I can measure this error,
with stock settings DeltaE of the white temperature is now 8.

I can easily calibrate the monitor to return to better deltae errors value but after all this time I noticed a weird behaviour that force me to disable the overdrive once and for all.

This is the result of the calibration using DisplayCAL.
https://we.tl/t-IuyYaesyKR
If I open this file and I scroll it fast up and down, the black text has a red ghosting if overdrive is on, it disappears if overdrive is off.

In past I tought that this ghosting effect was exxagerated by the ICC profile in use but it’s not.
The ghosting effect is caused by changing the RGB Gain for white temperature calibration.

From the stock R=50, G=50, B=50 I used R=49, G=43, B=46

this setting causes the ghosting effect, some other settings may reduce the ghosting effect.

is this something weird or did you experienced this behaviour in past with other monitors?
does monitor calibration (RGB Gain) affects the overdrive in other monitors?

On X32FP does.

I need an upgrade, can’t wait to “the next improved MiniLED” if we will ever see it 😀

[PCM2]

It’s normal for the white point and green channel balance to drift over time, yes. The phosphors (or in this case Quantum Dots) degrade slightly and so can the diodes, all of which shifts colour temperature. Also note that QD LED backlights are very temperature sensitive with their colour temperature and you can expect quite a shift as they warm up. Try displaying a white screen for at least 30 minutes with the monitor at full brightness, then carry out the calibration. This will reflect the truly warmed up state.

If you change the colour channels then you’re changing a given transition. You might find an increase in overshoot (or change in response time behaviour) for certain transitions as a result, but a decrease in overshoot or different change in response time behaviour elsewhere.

[sblantipodi]

when you test for response time or overshoot, did you do the test with stock settings with RGB Gains at default or do you test the monitors after the calibraton?
differences here are pretty wild.

let’s say that when I work, I don’t need a fast monitor but I prefer a better calibrated one,
when I play I use an uncalibrated HDR profile, so this problem should not that big 🙂

[PCM2]

The ‘Test Settings’ are used for testing (hence the name 😉 ). It’s a shame the X32 FP doesn’t have a response time setting between “Normal” and “Fast”, because that could potentially solve the issue which is related to a triggering of strong overshoot. Without you having to go to the slowest “Normal” overdrive setting.

[Author]

Posts