Has the PG27AQDM been abandoned?

[markob53]

There's still some ongoing issues with this monitor that have yet to be addressed, mostly to do with the stability of the monitor rather than the color replication.

Please see the following threads posted by me and other users.

Standby Bug

https://rog-forum.asus.com/t5/gaming-monitors/pg27aqdm-stand-by-bug-in-mcm107-still-persists/td-p/10...

General instability with many examples

https://rog-forum.asus.com/t5/gaming-monitors/pg27aqdm-unstable-since-mcm106/td-p/1024805

Base LED not working

https://rog-forum.asus.com/t5/gaming-monitors/pg27aqdm-base-led-doesn-t-turn-on-since-mcm107/td-p/10...

Update screen problem

https://rog-forum.asus.com/t5/gaming-monitors/oled-pg27aqdm-firmware-update-mcm107-screen-problem/td...

The above is a bug that has happened everytime i've updated to MCM107 and can be resolved by resetting everything but it just highlights that there is something wrong, i recently tried to update again hoping the newest BIOS/Driver would have a different result but no luck, there was also a flicker across the screen which required a combination of several reboots/factory resets.

If it's not the firmware (i find it hard to believe has everything works perfectly on MCM105) then i haven't been provided with any solutions to the problem.

Some of these issues are fixed when the refresh rate is set to 120hz.

Please advise if a new firmware is being worked on to address these problems.

[Alpine_Alex]

The OSD simply needs resetting once post flash for that distortion issue, so is easily circumvented.

I'm on MC107 and loving it - haven't experienced any of the above issues (although admittedly I use a monitor arm so no base). Some of those threads are prior to that update, too.

[markob53]

That's the problem, because so many seem to use a monitor arm it hides the fact the base LED does not come on after one or two reboots, which isn't an excuse for them not fixing it, not everyone wants or needs a third party accessory.

But that fact it breaks along with the screen glitches and flickers still highlights to me that there is an underlying issue with the firmware and i don't feel confident using it, along with all the other issues highlighted.

The other issues in my threads seem to only appear when a second screen is connected or the refresh of the main screen is set to 240hz, the delay when switching to HDR does not happen when only monitor is connected or the refresh is set to 120hz and like i say, everything works perfectly on MCM105 (apart from the color).

One thing for certain though is the base LED does break on MCM107 and although it's a minor issue that doesn't effect the monitor, it's still an advertised feature, so can they really advertise it if it stops working on the latest firmware?

Getting colors right sounds like a more difficult task than fixing the issues highlighted here, this shouldn't be a problem for them and i really want to use MCM107, if there's anything i can do then i'm all ears.

[markob53]

Update:

I think i worked out what was causing the base LED to go off and not come back on in some cases.

I had always set the USB hub to power down during standby to save power, on MCM105 when i did this the base LED would not be effected, on MCM107 the base LED goes off and eventually after enough reboots it doesn't return.

This may still be a bug that needs addressing but i realise that it only effects people who toggle the USB setting.

I did however find that in testing DLDSR in Final Fantasy 16 i get similar behaviour seen Alan Wake 2 in my other thread, in this case when i enable it the game sort of goes into a Window mode despite Full Screen being selected in the options, i also witnessed a crash when first trying to enable it.

Again, no such issues with DLDSR in MCM105. 

I even went into the registry and removed all instances of both monitors, uninstalled both from the device manager and installed the latest driver.

[markob53]

Hello everyone, back with another update (i'm sure everyone is paying attention).

Anyways...

I decided to see if it was a Windows issue and went ahead and did a fresh install of Windows 11 on a different partition, nothing else installed except driver and MCM107.

Nothing changed, here's a video of what occurred.

This is me simply toggling the HDR on/off, it's actually much worse than in the previous videos i've posted, you can see signal being lost during the toggle process, you can also see that after toggling Windows thinks my second monitor is my main monitor and i have to change it to then get the option to toggle HDR back.

I am open to the idea that my second monitor may be somehow conflicting with this new firmware, but as i've said on numerous occasions, everything works on MCM105 and if i set the refresh rate to 120hz none of this behaviour happens (even DLDSR works as intended). I'm using the cables that came with the monitor and have even purchased a new cable with no luck.

I've provided so much information regarding these issues it would be nice to have some feedback from anyone, someone with a second monitor just has to toggle HDR and report back the behaviour, or try DLDSR in Alan Wake 2 or FF16 and tell me if it works or even someone from Asus acknowledging that there either is or isn't a problem based on internal testing.

Most people wont see it as an issue if there's a delay between toggling HDR if everything works as intended, anyone without a second display wont notice it and anyone who doesn't use DLDSR in specific games wont notice it so to 99% of people the firmware will be flawless, but shows otherwise.

[Aureliannn_ROG]

Hi @markob53 ,

Thank you for providing the video. We've received your report about the display losing signal when switching HDR after upgrading the firmware to MCM107.

To help our engineering team analyze the issue more accurately, could you please provide the video in MP4 format? 

Additionally, please send us the following information via private message:

1. Display product serial number: This number will help us quickly look up your product information.
2. Other device models: Including your computer, graphics card, etc.
3. Driver versions: The versions of the drivers for all devices.
4. Operating system: The version of your operating system.

We will submit this information to our engineering team for further analysis. 

Thank you for your patience and cooperation!

[PWN3D_]

I don't know if abandoned is the right term, but they are very slow to fix issues that's for sure and the communication is really not existent, even on newer model like the PG34WCDM ( @Aureliannn_ROG still waiting for an update on my thread, its been two months now!!!!)

Anyway, an other issue I have with the PG27AQDM is that it doesn't seems to do it clean pixel process when I turn it off:
As per the FAQ provided by Asus here [LCD Monitor] ROG OLED Gaming Monitor Pixel cleaning process. | Official Support | ASUS Global

I quote " When the user manually turns off the monitor without removing the power cord, the monitor will automatically initiate pixel cleaning, taking approximately 6 minutes."

When I turn of my PG27AQDM, by double pressing on the Power on button, or by Pressing one time an selecting "turn off" on the OSD menu, the day after, I have a OSD message saying that I should do a pixel cleaning, that's saying that it did NOT do a pixel cleaning when it's turned off.

Only when the monitor enter stanby mode, I can see the led flashing and the clean pixel pixel works correctly. But I can't let it in standby because of the LOUD high frequency sound that came from the back of it. It's only happen on Standard mode and not on Eco mode. It's like a high pitch, like  a coil whine noise. I'm not the only one with this noise so I don't think that getting a replacement is worth it ... for now

[markob53]

Interesting about the Pixel Cleaning, especially the coil whine issue.

I've had mixed experiences with the automatic pixel cleaning too, i'm not sure if it's doing it or not, sometimes i see a very brief flash after i shut my PC down then nothing else.

However, i've not had any issues related to that, i find that whatever it is doing (if anything) is enough along with me running a pixel clean every couple of weeks, i've not witnessed an issue with the picture approaching it this way, the coil whine sounds like a defect though, i've not had any noise come out of mine.

[PWN3D_]

Yeah that's sound is really only noticable on a quiet room and it might not be heard to everyone since it's a really high pitch noise. I have it in a bedroom and with the PC on I can't hear it. it's only audible just after entering standby  for a few minutes with the orange light with the back panel RGB and stand light turned to off.
It's getting quiet during the 6 minutes pixel refresh and then it's getting loud again. It sould be audible when you tend your hear at the back of the monitor, near all the ports but like you said, it's maybe a defect, I just saw a lot of people with that kind of noise, on the PG27AQDM and the PG32UCDM, even though with the 32inch version, it seems that the noise is audible when the monitor is turned off and not on standby.

To be fair, i'm also on a streak of 4 PG34WCDM and they call came with some coil whine, but this time it can be only heard when it's on and it's getting louder on bright images.

3 differents models, 3 kind of noise.

Though for the PG27AQDM t's still under guarentee but I'm really worry to do a replacement and end on an worse unit that this one, so for now I'm waiting and see how it evolve.

[markob53]

I just had a listen to mine when i turned the PC off (monitor in standby, all lights on) and honestly couldn't hear a thing.

But the fact you've had it happen on so many monitors might imply it's not a defect because that would be insanely unlucky.

I'm not an expert at all but i wonder if it's something to do with the current going into the monitor from the the sockets in the house, it's the only consistent thing that's been ever present in all your tests.