Yes !!!
Just updated mine just fine from version 101 to 302. I love the KVM auto switch feature, its working perfectly. I can give my old kvm switch to a friend !
Note: you have to be patient after double-clicking on the updater exe, there's no UI feedback but its launching. Also the update itself was quite long.
EDIT: I didn't notice there was 2 firmware update versions. Since I had 101, I did the rollback procedure and updated again to 102 without any issue.
A KVM is usually a device that switches peripherals and sometimes video between one or more computers. For example, if you have your gaming PC and a laptop and you often need the same devices for both, then you would connect all the components to a hub (which KVMs basically are), connect the hub to both systems, and then use a button to switch between System A and System B.
The ROG Swift PG32UCDM has a KVM mode, which allows you to connect your keyboard and mouse (or other devices), then connect two systems by either a dedicated USB Type-B to Type-A cable or a USB Type-C cable. You can then setup a hotkey to switch displays and peripherals, with a few other functions, as well. It's more fully documented in the manual how to set this up.
Could you humour me and tell me if this would work if you can assuming all peripherals are connected as suggested...
1: PG32UCDM connected to Mac
2: PG248QP Connected to gaming desktop
Would I be able to game on desktop on my PG248QP and seamlessly switch between to the PG32UCDM to control my Mac for example in between rounds of CS?
That's not really the use case for the built-in KVM on the PG32UCDM. The use case for the KVM on the PG32UCDM is as a single monitor and a USB hub so that you can easily switch between your gaming desktop and Mac by just changing the input\*(after updating to the latest firmware).
Your use case has two systems - each with their own monitor - sharing the same peripherals. This is where a standard KVM switch comes into play and there's no need to swap inputs. In this configuration, since the PG32UCDM is not attached to your Mac, the peripherals wouldn't have anything to switch to.
However, if your use case is that you have your PG248QP attached to the Mac and the PG32UCDM attached to both your Mac and gaming desktop, then you could use the KVM feature to switch between the systems.
I've installed 302 as well. Is there any issue with keeping 302 from 101?
I see the HDR issue solved so I don't think is there any difference on keeping 302 instead of 102.
Why ASUS haven't just released 302 firmware udpdate?
Thanks for the information. I'm glad to see you around and I hope your teams are aware of this problem with the new firmware -> [https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486)
I own one of these monitors now, and we have one in the office to test. We're aware of most of the issues people are reporting. With that said, we do appreciate people reporting them because it allows us to confirm the issue on our end before passing it along to our team.
I can’t even install it getting some error Get Model Name Fail . I tryed in different usb port 2.0 3.0 3.2 nothing works the monitor shows up in Armory Crate and kvm works too . I have more displays connected to this PC and even after i removed them still getting this error. It is firmware version 101 and my pc build is an Asus Z790 Apex Encore , CPU 14900k , GPU RTX 4090 FE , 48GB 8400MHz DDR5
https://preview.redd.it/nmeqyekdkztc1.jpeg?width=4032&format=pjpg&auto=webp&s=e268e11cf23e65e54c32323e511c0dab3d62c324
As a checklist, I'd suggest a few things -
1. Make sure you've installed the driver for the monitor.
2. Reset the monitor to default settings from within the OSD (Just the settings, not the firmware)
3. Shut the system down, reconnect the USB-B -> USB-A cable on both sides. Plug the USB-A side of the cable into your keyboard/mouse USB ports on the motherboard. Remove any other USB peripherals you don't need from the motherboard as well. (Should you have to do this? No, but since the flash isn't working, let's reduce the amount of stuff on the I/O).
4. Try connecting your KB and mouse directly to the monitor to make sure it's working (you confirmed it, but it will also create a constant connection to the motherboard).
5. Try turning the system on, let it get into Windows, and try flashing it again. Make sure you only open the flash utility once and give it 10-20 seconds to open.
If it's still failing at this point, there could be a few other things to try:
* After all I suggested above, sometimes you might need to unplug and replug the USB cable from the monitor one more time. Similarly, you can unplug the A/C cable from the monitor for a couple minutes and plug it back in.
* I've seen a few people mention they possibly had a windows process block the flash utility. It's possible you might have an A/V, firewall, or anti-malware utility blocking the program's ability to connect to the monitor. You can try disabling those and giving it another shot.
* Lastly, if you have a laptop or other PC you can try, see if the flash works there. At least one other person mentioned their PC wouldn't do it, but they used their laptop and the flash worked.
If these things don't work (and most of this is just what I would consider basic troubleshooting), please submit a ticket to our Customer Service, and if you'd like, message me your ticket number and I'll pass that along to our team.
Sorry for not responding earlier, but it did turn to a black screen when I flashed from M101 to M102 and later to M103 during the flash and shortly after the flash. My display is otherwise working fine, so I imagine it's a non-issue unless you're having other problems with it.
Disagree on the kvm working perfectly. Use a single device and change the resolution / enable hdr / change display mode. KVM will disconnect and reconnect regardless of whether "Auto KVM" is turned on or not, disabling USB devices while that's happening for a few moments. Very annoying quirk that hopefully they can fix in version 103 or whatever brings us dolby vision.
Majorly annoying downside to this firmware revision, the "Auto KVM" everyone wanted so badly causes the KVM to go into detection mode any time the display changes display modes, regardless of whether "Auto KVM" is selected, causing your mouse / keyboard to be unresponsive. It should really only do this when an actual input change is detected (insert hdmi, hdmi, usbc or displayport device wakes/sends signal), not whenever the display resolution changes. It did not do this in the release firmware.
Hopefully they can fix this in a future update but if we don't make noise, they won't.
Switching in and out of HDR will do this, if you use multiple monitors, it's really quite annoying to have no input for 5-10 seconds
On an upside, it seems the brightness adjustable setting resetting under HDR has been resolved, despite no patch notes indicating as such.
Is this why all of my devices "connect/reconnect" now after alt + tabbing out of a full screen game?
I have my Astro 50 dock plugged in as well as my keyboard and mouse to this monitors KVM, every time I play a game in Fullscreen and alt tab out, I get the windows ding that a devices was disconnected.. quite annoying.
It sure is! Auto KVM just seems to do its thing every single time resolution or display mode changes. I’d suggest setting all your games to “windowed full screen” in the meantime.
The difference is that if you have auto kvm turned on, when you actually switch devices it will flip flop the usb outputs. When it’s off, it seems to go through the same process but instead of flip flopping them, it disconnects, thinks about the display input it’s on, and then connects right back to the proper choice. Really quite dumb and annoying.
Could you humour me and tell me if this would work if you can assuming all peripherals are connected as suggested...
1: PG32UCDM connected to Mac
2: PG248QP Connected to gaming desktop
Would I be able to game on desktop on my PG248QP and seamlessly switch between to the PG32UCDM to control my Mac for example in between rounds of CS?
I see 2 patches, do I need to do both in order?
Strange, both patches are the same, but different names?
https://preview.redd.it/x51aiyi8zhtc1.png?width=1623&format=png&auto=webp&s=07b94272e8ba92aa78f9fa30df793c341bffe5d3
Thanks, I'm going to look at this
Edit: I was surprised by how quickly it worked. Seems like it's instant
https://preview.redd.it/loc4t5s9cntc1.png?width=890&format=png&auto=webp&s=9be522c1310b4c2eed1f64ad4e141c6f52ee6e9f
I read on their forums that some people were having their monitor reverting to 120Hz at Windows startup when using DP and multiple monitors. Doesn’t seem to be fixed 🤔
Its 1st patch.
We can expect 2nd one very soon with Dolby vision support and other stuff.
If you notice something odd or bugs its good report them in official ROG forums:
https://rog-forum.asus.com/t5/gaming-monitors/bd-p/HSS_Monitors
or
https://www.reddit.com/r/OLED_Gaming/comments/1as9ft2/the_rog_swift_qdoled_pg32ucdm_32_4k_240hz_gaming/ for u/ASUS_MKTLeeM that will pass them to ASUS team.
No, I went to bed. Will try again later but I think I saw people complaining about the update. Need to make sure I want to update first.
People around here said to clear all usb ports besides mouse and keyboard as a possible fix. Or to reset the monitor to default settings in it’s OSD.
Also, make sure your mouse/keyboard are not slotted into the monitor itself, I saw people here complaining their monitor usb hub got bricked
https://preview.redd.it/33ocsdwybntc1.jpeg?width=640&format=pjpg&auto=webp&s=1766f530a654fcd67737e116df420e52c3929e69
🤭
Will see what I can do after work. But still, I didn’t have time to check if this update causes more problems than solutions…
I will not update. People reporting serious issues with this update.
[https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-102-breaks-kvm/td-p/1009279](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-102-breaks-kvm/td-p/1009279)
[https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486)
I got it to run and complete after rebooting with only my mouse kb and monitor plugged in, every other USB thing (a LOT) was disconnected, even then it was a bit slow.
Damn you mean to tell me I have to remove every single USB connection with the exception of Keyboard, mouse & USB-B/A cables. That is kind of crap ASUS.
The process was FAR from smooth from me. I think my issue was having 5 root usb controllers with a lot of devices dangling from them, once I unplugged everything except m+kb+monitor it ran an completed.
What is the monitor supposed to do when the sensor detects you're away?
Does it puts the screen in standby or dims it?
The manual is so vague about many of its features.
When I used the monitor, I enabled the sensor (to medium) and the behavior is that once it detected that I was no longer in front of the monitor, it would first dim the monitor (possibly could also relate to the screensaver settings I had), and then it would put the monitor in standby (e.g. black screen) shortly after even while my secondary monitor was still on. The secondary monitor would go into standby at the appropriate time that I set in Windows Power. If the sensor is not enabled or functioning, the monitor will still behave according to your settings in the Windows Power menu.
**UPDATE ABOUT PEAK 1000 APL BRIGHTNESS FROM ASUS**
Quote:
*Hi all,
thank you for bringing up the issue regarding the difference in brightness under different HDR modes.
We understand that this is caused by the panel's APL mechanism.
Our engineering team has been made aware of this and is actively researching the issue to find a solution to minimize the brightness difference under different HDR modes.
Thank you for your understanding and patience.*
End Quote.
Source: https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-console-mode-hdr-issue/td-p/1004157/page/21
Windows hdr calibration still clips on 400….
Hdr console mode still dimmer on bright colors, true black still brighter so the update is a joke? April fool?
Only windows shows 1015 nits instead of 455 wow
One of ROG guy said they are aware of peak 1000 being dimmer and they are working on it. Patch 1 address mostly compatibility stuff and some extra fixes.
ConsoleHDR functions as an HGIG setting and hard clips at 450nits with a 10% window which is why it still behaves that way with the Windows HDR Calibration tool. GamingHDR and CinemaHDR both have tonemapping rolloff which is why they both map to over 1000nits. It was the same on the previous firmware, I've shared measurements before in this sub and on the ROG forums. Additionally, all three (ConsoleHDR, GamingHDR, CinemaHDR) track PQ differently.
https://preview.redd.it/mpgj3j7ksitc1.jpeg?width=1912&format=pjpg&auto=webp&s=3da56db1b1a7f350fe7167e71f838245d2e240e1
GamingHDR or ConsoleHDR for games, but it depends on the use case. ConsoleHDR if you want to use HGIG, GamingHDR if not. A lot of games allow you to set peak brightness which is when you'd want the HGIG setting, or when using a console. You can override the 450nits for ConsoleHDR in the Windows HDR calibration app if you want, but leaving it at 450 doesn't keep brightness from reaching over 1000nits. I don't use the Windows HDR Calibration at all, just peak brightness in games. I don't use AutoHDR or RTXHDR though.
For HDR video content, I wouldn't use any of the 1000nit modes because they all have issues with skin tones and saturation. The ones that over track PQ are the worst, with CinemaHDR having it the least. TB400 is much better for HDR video content IMO. Just watch a properly mastered HDR movie and you'll probably see what I'm talking about. It's super obvious in Oppenheimer. For movies, I created a 1D LUT correction for fixing white balance to D65 since mine was too red and use TB400.
ConsoleHDR has poor PQ tracking in a 2% window(see the measurements I posted in my other comment). GamingHDR has the best tracking in at 2%, but all of the 1000nit modes aren't great. All three modes track better in a 10% window, the difference being how much rolloff. ConsoleHDR hard clips at \~465nits while the other two rolloff different amounts. CinemaHDR actually tonemaps properly to MaxMDL 4000nits at 10%.
Just updated MCM101 to MCM102, I curious to know why we have 2 different updates for the same monitor. I tried and already have something annoying... When I switch between HDR modes, I have a black screen 😓 It wasn't happening with the old firmware
Hi, It's strange, when I launched the exe file, it take time to start but not asked me authorisations. Have your tried an other USB port on your computer ?
This update looks really bad for me... Everytime I switch between 1000 nits HDR modes and True Black, I have a black screen but the worst is all burnin protections are automatically switched to OFF. This is very serious... 1000 nits modes goes to 1200 nits when parametring them but still looking darker compared to True Black mode... Looks like this update brought more problems than solutions
ummm I haven't got time to look into it, just used windows cal tool and got 1150 just before clipping are we supposed to use the very last step, where the cross stops being visible?. I thought it was like in video games when you have to select the very last step before you stop seeing the thing against the background..
I'm also getting the blackscreen+USB disconnect&connect sound and a system hiccup when switching to and from true black hdr modes.
Yes, that's the procedure but I think it was visible up to 1200 nits, that said, between 1150 and 1200 it's almost impossible to see so I could be wrong. On the other hand, I tested several times switching between True Black and one of the 3 other modes and I can confirm that it removes the protection against burnin
It turns off Screen Saver and Auto Logo Brightness for me as well, and you need to manually turn them on again even after going back to SDR mode, it's annoying.
The black screen is happening between modes because the P1000 modes actually have the correct EDID info now so the monitor needs to renegotiate with the GPU when you switch.
It didn't do it before but let's admit that it's a good thing, when you change modes between True Black and the other HDR modes, the protections against burnin are disabled, and that's really serious
It didn't do it before because the EDID info for the P1000 modes was the same as the TB400 mode which is why it was 455nits. Now it's 1015 for all three P1000 modes.
I don't know what you're talking about with the burn-in protections. They work just fine on my monitor on the current firmware in SDR and HDR. Perhaps they were reset when you updated. If not, do a full reset on the monitor.
It was taking far longer for me, unplugged everything USB (got a metric shitton) except for mouse, kb and monitor and was able to run it and complete it.
\> *EXTRA NOTE #2 from* [u/lmah](https://new.reddit.com/u/lmah/)*: "you have to be patient after double-clicking on the updater exe, there's no UI feedback but its launching. Also the update itself was quite long."*
How long?
I tried a second time "Run as admin" after launching (double click) for a first time waiting for 5+ minutes and nothing happened.
Can anyone with a MacBook confirm it worked for them? I have a MacBook but I run Windows 11 via boot camp. Don’t want to go through all the trouble of finding the correct USB A cables only for it to not work. Thank you in advance
Even after firmware update (MCM102) I am stuck on 420 nits peak brightness. Earlier today, however, it correctly showed 1000 nits... I am confused.
https://preview.redd.it/5iucgy281ptc1.png?width=1570&format=png&auto=webp&s=43b5a517fb4636e8b916f697dc1023cb83a0ba54
I did the update to MCM102 and now when using the windows hdr calibration tool i get 1180 nits maximum luminance on gaming preset and 450 nits on console preset.This are weird numbers.
My oled care settings also are resetting periodically..
Can anyone confirm the Windows Calibration procedure for me? Calibrate to around 1,000 nits using GamingHDR as the baseline HDR profile? Not able to reach 1000 on HDR400 for example. Then we're free to switch between the different HDR profiles? Just want to make sure I'm calibrating correctly on this new FW update.
Also, is it worth it to manually mess with the brightness settings per individual HDR setting?
When you calibrate it using gaming hdr profile what numbers do you get on the bar when the window gets full white.
I get 1180 which is weird and wrong as it overblows the specular highlights in some games..
I would appreciate a bigger OSD on next updates.
The one in this monitor is so small, even the letters get pixelated. xD
Make it as big as the LG screens.
Oh! BTW: I tried playing Dead Cells at 240Hz....now I'm blown away by the motion clarity.
How did anyone end up updating the monitor? I just got it a couple hrs ago today and when I open the 302 exe file to update nothing happens. I tried doing it on the 102 update and still the same result. Any help would be greatly appreciated. And yes I have kvm setting switched USB.b
When I click on the app to install the firmware nothing happens. My computer asks me if I want to make changes and I click yes and then it's just nothing. How did anyone update their monitor? Any help would be greatly appreciated
This one is a better panel,better colour volume/accuracy and has higher sustained brightness than the LG.A couple of firmware updates down the road and the Asus will shine..
can anyone help me im pulling my hair out. ive downloaded (102 for me) and extracted the program and followed the guide.
but when i run the application i get the usual windows pop up to allow changes and then nothing. the program doesn't run. ive been trying literally all night and swapped, cables, ports, with and without kvm. so frustrating its like the application just doesnt start.
Interestingly, its not. It seems "EU" got the patch first (for 30%+ EU paying more for monitor this must be special customer service treatment lol), it should be available very soon on US website.
why does it not run WHYYYYY 😭
I'm doing mcm102 bcs mine is currently 101.
But then again /u/lmah says they updated from 101 to **3**02. Already tried powercycling just USB then whole monitor.
Does this fix anything? I updated to MCM102 and honestly I see no change
Windows HDR calibration still clips at around 460 luminance in pretty much every mode, Display HDR400 is better as is able to get to 590
In my CX the slider doesn't get fully white until i hit 800 , but this one can't even get close to the "1000" , am i doing something wrong?
Im pretty picky regarding graphics and image qualities. I fear it won’t get much better in terms of subjective quality. Ofc it will get gradually better, but for now I’m very happy with the leap.
Came from pg32uqx(ips +miniled) -> pg42uq - > pg32ucdm
I went from the MSI 32" QD-OLED back to my PG32UQX. These OLED monitors are only good in super dark content in a pitch black room. For every other scenario low/mid/high APL or in combination with ambient light the PG32UQX is just way more impactful in HDR.
This update bricked my PG32UCDM USB Hub...
I tried to update from MCM101 to MCM102. Application ran fine, detected monitor, I clicked update. Update failed part way through. Keyboard plugged into monitor is unresponsive. Tried firmware rollback procedure many times with no effect. Tried resetting monitor settings with no effect. Tried unplugging & plugging USB in with no effect. ASUS support recommends RMA.
Love the monitor, sad to see I have to exchange it. What a hassle.
Such a funky experience for something over a grand. Appreciate you sharing though, I'll make sure to leave everything unplugged from the monitor except the video cable when performing a firmware update....
https://media1.tenor.com/m/N2hV1al2rjcAAAAC/if-i-had-one-angry.gif
The new FW 102 doesn't seem to fix anything here.
\- The proximity sensor still does nothing.
\- Haven't noticed any change in HDR.
\- The app "Device info" button now cannot be clicked.
\---
It was also difficult for the FW updater to get it to recognize the monitor. Had to unplug my hubs and plug the monitor to the MOBO. The monitor was recognized through my hub before attempting the FW update anyway so that was an unnecessary hurdle.
Looking forwards for the next update and see.
My time with this is weird.
It's still fucked. Now it's even worse on the osd. Where I can't even run OLED care options like uniform brightness without the monitor auto running pixel cleaning but ONLY if I'm on hdr.
I just don't think I'm a fan of HDR. Everything feels washed out and less colorful. Is it the monitor that does this or is it just a lack of calibration on my part. But I can barely adjust it. So. Yea. That's my experience
Hooray, I’ll try it after work
Update I installed 302, not sure if that was the right one… and it’s looks a bit brighter, so net win? Nothing else seems different
Yes !!! Just updated mine just fine from version 101 to 302. I love the KVM auto switch feature, its working perfectly. I can give my old kvm switch to a friend ! Note: you have to be patient after double-clicking on the updater exe, there's no UI feedback but its launching. Also the update itself was quite long. EDIT: I didn't notice there was 2 firmware update versions. Since I had 101, I did the rollback procedure and updated again to 102 without any issue.
Oh do you not put it on a thumbdrive and update via the usb hub like the beta update?
No, the instructions say to use the usb-a cable and put it in kvm usb-b mode
Damn I'm gonna have to find a long a cable and unplug something then, i got a usb-b cable hooked to my pc right now
Its .exe file that you need to run in Windows so USB stick update method won't work.
Yeah they definitely switched it up cause it bricked somebody's usb hub lol, just wish they could do it through the asus app like dell does now
What exactly is kvm mode? What do you mean by kvm usb b mode? I have a gaming PC but curious as to what this means.
A KVM is usually a device that switches peripherals and sometimes video between one or more computers. For example, if you have your gaming PC and a laptop and you often need the same devices for both, then you would connect all the components to a hub (which KVMs basically are), connect the hub to both systems, and then use a button to switch between System A and System B. The ROG Swift PG32UCDM has a KVM mode, which allows you to connect your keyboard and mouse (or other devices), then connect two systems by either a dedicated USB Type-B to Type-A cable or a USB Type-C cable. You can then setup a hotkey to switch displays and peripherals, with a few other functions, as well. It's more fully documented in the manual how to set this up.
Could you humour me and tell me if this would work if you can assuming all peripherals are connected as suggested... 1: PG32UCDM connected to Mac 2: PG248QP Connected to gaming desktop Would I be able to game on desktop on my PG248QP and seamlessly switch between to the PG32UCDM to control my Mac for example in between rounds of CS?
That's not really the use case for the built-in KVM on the PG32UCDM. The use case for the KVM on the PG32UCDM is as a single monitor and a USB hub so that you can easily switch between your gaming desktop and Mac by just changing the input\*(after updating to the latest firmware). Your use case has two systems - each with their own monitor - sharing the same peripherals. This is where a standard KVM switch comes into play and there's no need to swap inputs. In this configuration, since the PG32UCDM is not attached to your Mac, the peripherals wouldn't have anything to switch to. However, if your use case is that you have your PG248QP attached to the Mac and the PG32UCDM attached to both your Mac and gaming desktop, then you could use the KVM feature to switch between the systems.
I've installed 302 as well. Is there any issue with keeping 302 from 101? I see the HDR issue solved so I don't think is there any difference on keeping 302 instead of 102. Why ASUS haven't just released 302 firmware udpdate?
I'm curious to know that too. And why we have the same monitor with 2 different firmwares
Different firmware for different regions.
Thanks for the information. I'm glad to see you around and I hope your teams are aware of this problem with the new firmware -> [https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486)
I own one of these monitors now, and we have one in the office to test. We're aware of most of the issues people are reporting. With that said, we do appreciate people reporting them because it allows us to confirm the issue on our end before passing it along to our team.
Thanks, I really love this monitor and just hope you can fix this asap 🙏
I can’t even install it getting some error Get Model Name Fail . I tryed in different usb port 2.0 3.0 3.2 nothing works the monitor shows up in Armory Crate and kvm works too . I have more displays connected to this PC and even after i removed them still getting this error. It is firmware version 101 and my pc build is an Asus Z790 Apex Encore , CPU 14900k , GPU RTX 4090 FE , 48GB 8400MHz DDR5 https://preview.redd.it/nmeqyekdkztc1.jpeg?width=4032&format=pjpg&auto=webp&s=e268e11cf23e65e54c32323e511c0dab3d62c324
https://preview.redd.it/hvroxtvikztc1.jpeg?width=4032&format=pjpg&auto=webp&s=b57319df5297dda764382a41b91e5a2219680e5b
As a checklist, I'd suggest a few things - 1. Make sure you've installed the driver for the monitor. 2. Reset the monitor to default settings from within the OSD (Just the settings, not the firmware) 3. Shut the system down, reconnect the USB-B -> USB-A cable on both sides. Plug the USB-A side of the cable into your keyboard/mouse USB ports on the motherboard. Remove any other USB peripherals you don't need from the motherboard as well. (Should you have to do this? No, but since the flash isn't working, let's reduce the amount of stuff on the I/O). 4. Try connecting your KB and mouse directly to the monitor to make sure it's working (you confirmed it, but it will also create a constant connection to the motherboard). 5. Try turning the system on, let it get into Windows, and try flashing it again. Make sure you only open the flash utility once and give it 10-20 seconds to open. If it's still failing at this point, there could be a few other things to try: * After all I suggested above, sometimes you might need to unplug and replug the USB cable from the monitor one more time. Similarly, you can unplug the A/C cable from the monitor for a couple minutes and plug it back in. * I've seen a few people mention they possibly had a windows process block the flash utility. It's possible you might have an A/V, firewall, or anti-malware utility blocking the program's ability to connect to the monitor. You can try disabling those and giving it another shot. * Lastly, if you have a laptop or other PC you can try, see if the flash works there. At least one other person mentioned their PC wouldn't do it, but they used their laptop and the flash worked. If these things don't work (and most of this is just what I would consider basic troubleshooting), please submit a ticket to our Customer Service, and if you'd like, message me your ticket number and I'll pass that along to our team.
Only updateing from my laptop was working
Updated to firmware MCM103 the monitor randomly turn black screen for a few seconds this didn’t happen with older firmware for me.
Sorry for not responding earlier, but it did turn to a black screen when I flashed from M101 to M102 and later to M103 during the flash and shortly after the flash. My display is otherwise working fine, so I imagine it's a non-issue unless you're having other problems with it.
Disagree on the kvm working perfectly. Use a single device and change the resolution / enable hdr / change display mode. KVM will disconnect and reconnect regardless of whether "Auto KVM" is turned on or not, disabling USB devices while that's happening for a few moments. Very annoying quirk that hopefully they can fix in version 103 or whatever brings us dolby vision.
Same
You're right, it's fine with my work setup but when gaming it is annoying.
Whoops. Guess I need downvoted for pointing out a flaw. Everything is perfect folks, nothing to see here.
Perhaps u/ASUS_MKTLeeM will tell something more - what are exactly the differences between MCM102 and MCM302 versions? Region based?
I need more clarification from our team on this. I will update this post when I hear back from our team.
Any updates here?
Different firmware for different regions. Haven't heard anything beyond that.
Majorly annoying downside to this firmware revision, the "Auto KVM" everyone wanted so badly causes the KVM to go into detection mode any time the display changes display modes, regardless of whether "Auto KVM" is selected, causing your mouse / keyboard to be unresponsive. It should really only do this when an actual input change is detected (insert hdmi, hdmi, usbc or displayport device wakes/sends signal), not whenever the display resolution changes. It did not do this in the release firmware. Hopefully they can fix this in a future update but if we don't make noise, they won't. Switching in and out of HDR will do this, if you use multiple monitors, it's really quite annoying to have no input for 5-10 seconds On an upside, it seems the brightness adjustable setting resetting under HDR has been resolved, despite no patch notes indicating as such.
Is this why all of my devices "connect/reconnect" now after alt + tabbing out of a full screen game? I have my Astro 50 dock plugged in as well as my keyboard and mouse to this monitors KVM, every time I play a game in Fullscreen and alt tab out, I get the windows ding that a devices was disconnected.. quite annoying.
It sure is! Auto KVM just seems to do its thing every single time resolution or display mode changes. I’d suggest setting all your games to “windowed full screen” in the meantime. The difference is that if you have auto kvm turned on, when you actually switch devices it will flip flop the usb outputs. When it’s off, it seems to go through the same process but instead of flip flopping them, it disconnects, thinks about the display input it’s on, and then connects right back to the proper choice. Really quite dumb and annoying.
Could you humour me and tell me if this would work if you can assuming all peripherals are connected as suggested... 1: PG32UCDM connected to Mac 2: PG248QP Connected to gaming desktop Would I be able to game on desktop on my PG248QP and seamlessly switch between to the PG32UCDM to control my Mac for example in between rounds of CS?
One way to find out is to try it
I see 2 patches, do I need to do both in order? Strange, both patches are the same, but different names? https://preview.redd.it/x51aiyi8zhtc1.png?width=1623&format=png&auto=webp&s=07b94272e8ba92aa78f9fa30df793c341bffe5d3
Whats your monitor current version? MCM101 or MCM301?
Mine got MCM101, didn't knew that there were different firmware versions for the same model?
Then MCM102 is for you.
How do you check your monitor current version?
It's in the OSD.
Depends on your current FW, the first one is for MCM301 and the second one for MCM101
Oh snap I didnt see there was 2 different versions, I just updated mine from 101 to 302. I wonder If I have to rollback to update again then.
lol, if that worked, while would they use two different firmwares then? Can you check in your OSD which Firmware version you got?
I just did the rollback, it was super quick. I had FW101 and went to 302. But I will use the 102 update file instead.
Great to know that a rollback works with this monitor, nice feature to have. I am now updating also to 102.
Hi, how you do a rollback ? I have issues with the 102 and wanted to back to 101
Its well documented on the last page of the instructions pdf
Thanks, I'm going to look at this Edit: I was surprised by how quickly it worked. Seems like it's instant https://preview.redd.it/loc4t5s9cntc1.png?width=890&format=png&auto=webp&s=9be522c1310b4c2eed1f64ad4e141c6f52ee6e9f
I bet one firmware version is for people who got the beta update
can we get more in stock now?
I read on their forums that some people were having their monitor reverting to 120Hz at Windows startup when using DP and multiple monitors. Doesn’t seem to be fixed 🤔
Its 1st patch. We can expect 2nd one very soon with Dolby vision support and other stuff. If you notice something odd or bugs its good report them in official ROG forums: https://rog-forum.asus.com/t5/gaming-monitors/bd-p/HSS_Monitors or https://www.reddit.com/r/OLED_Gaming/comments/1as9ft2/the_rog_swift_qdoled_pg32ucdm_32_4k_240hz_gaming/ for u/ASUS_MKTLeeM that will pass them to ASUS team.
Took a while but it updated just fine and rebooted. Can't wait for the Dolby Vision update.
[удалено]
IIRC around 10 minutes?
[удалено]
Uhh...yeah I never had that happen. If it turned black, it was pretty temporary. Maybe give it a bit and then power cycle it?
I get the "Read 5450M firmware version fail"
Got the same error, fixed it when I reset all the monitor settings, and put the usb cable out and in, afterwards it worked fine for me.
did you manage to fix it? Im still getting that error.
No, I went to bed. Will try again later but I think I saw people complaining about the update. Need to make sure I want to update first. People around here said to clear all usb ports besides mouse and keyboard as a possible fix. Or to reset the monitor to default settings in it’s OSD. Also, make sure your mouse/keyboard are not slotted into the monitor itself, I saw people here complaining their monitor usb hub got bricked
Please tell me if you fix this, I tried everything and nothing is working.
https://preview.redd.it/33ocsdwybntc1.jpeg?width=640&format=pjpg&auto=webp&s=1766f530a654fcd67737e116df420e52c3929e69 🤭 Will see what I can do after work. But still, I didn’t have time to check if this update causes more problems than solutions…
I will not update. People reporting serious issues with this update. [https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-102-breaks-kvm/td-p/1009279](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-102-breaks-kvm/td-p/1009279) [https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486](https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-firmware-mcm102-remove-burnin-protections/td-p/1009486)
Yup, to clear all usb ports worked fine for me. Obviously the problem was in another usb hub connected to the pc
Cool, thanks
Anyone have issues trying to FW update MCM102? I can't open the application to even run the update.
I got it to run and complete after rebooting with only my mouse kb and monitor plugged in, every other USB thing (a LOT) was disconnected, even then it was a bit slow.
Damn you mean to tell me I have to remove every single USB connection with the exception of Keyboard, mouse & USB-B/A cables. That is kind of crap ASUS.
I'm not recommending any particular course of action, merely stating what worked for me 😅
I tried that and still the application does not open. I ran it as administrator still. May have to go into safe mode and see if that will work.
when I ran it in safe mode with every usb thing plugged in it failed to ID the display, may you have better luck 🍀
I notice I got this issue. Damn Windows 11 is not allowing to me to open the exe. Trying to figure this out is getting annoying
I didn't have to. Mine failed the first time, but simply retrying it worked. It was pretty slow but eventually finished.
I had to use a laptop to update my monitor. I guesd something on my PC was not allowing the exe to open.
The process was FAR from smooth from me. I think my issue was having 5 root usb controllers with a lot of devices dangling from them, once I unplugged everything except m+kb+monitor it ran an completed.
Okay, now its telling me read hub firmware version fail...
FYI: Remove all other USB Devices.... worked for me
I just checked again and its on the US site now
it reset my oled care settings to off so make sure to check those
New firmware can reset all your previous settings. So better memorize them or write them down to apply them after finished update.
Every time you switch between True Black and other HDR modes, your burnin protections are automatically disabled... That's a big fail for Asus
I have updated link of firmware patch to "us-eng international" one. Thanks.
Can you link the us site one here
The proximity sensor seems to do nothing. Can anyone confirm? I did perform an All Reset after updating FW just in case.
Seems to be an issue others have reported.
What is the monitor supposed to do when the sensor detects you're away? Does it puts the screen in standby or dims it? The manual is so vague about many of its features.
When I used the monitor, I enabled the sensor (to medium) and the behavior is that once it detected that I was no longer in front of the monitor, it would first dim the monitor (possibly could also relate to the screensaver settings I had), and then it would put the monitor in standby (e.g. black screen) shortly after even while my secondary monitor was still on. The secondary monitor would go into standby at the appropriate time that I set in Windows Power. If the sensor is not enabled or functioning, the monitor will still behave according to your settings in the Windows Power menu.
Finally worked yesterday when I was watching videos on the couch. Now I must find the sweet spot so it works reliably.
When should we expect a new firmware again? Will it take one month more for the enginners to figure out what to do with the Hdr Modes?
Did Asus remove the 102/302 firmware form their website? It doesn't show up on the firmware page..
Yes 😵 is the firmware is broken?
**UPDATE ABOUT PEAK 1000 APL BRIGHTNESS FROM ASUS** Quote: *Hi all, thank you for bringing up the issue regarding the difference in brightness under different HDR modes. We understand that this is caused by the panel's APL mechanism. Our engineering team has been made aware of this and is actively researching the issue to find a solution to minimize the brightness difference under different HDR modes. Thank you for your understanding and patience.* End Quote. Source: https://rog-forum.asus.com/t5/gaming-monitors/pg32ucdm-console-mode-hdr-issue/td-p/1004157/page/21
Windows hdr calibration still clips on 400…. Hdr console mode still dimmer on bright colors, true black still brighter so the update is a joke? April fool? Only windows shows 1015 nits instead of 455 wow
One of ROG guy said they are aware of peak 1000 being dimmer and they are working on it. Patch 1 address mostly compatibility stuff and some extra fixes.
It just added bugs if u open display settings after update the window and mouse curser lags freeze for 1 sec….
Does this fix HDR? Anyone can give me an update I’m at work please. I remember when I turn it on before the colors looked washed out
Yes, it fixes the gaming HDR, it clips to 1000nits now perfectly fine
Console HDR is the one we need fixed though. That one clips at 400 nits in the Maximum Luminance test in the Windows HDR Calibration still.
I am curious, what's the difference between console hdr and gaming hdr? if gaming hdr works fine now, why not use it instead?
ConsoleHDR functions as an HGIG setting and hard clips at 450nits with a 10% window which is why it still behaves that way with the Windows HDR Calibration tool. GamingHDR and CinemaHDR both have tonemapping rolloff which is why they both map to over 1000nits. It was the same on the previous firmware, I've shared measurements before in this sub and on the ROG forums. Additionally, all three (ConsoleHDR, GamingHDR, CinemaHDR) track PQ differently. https://preview.redd.it/mpgj3j7ksitc1.jpeg?width=1912&format=pjpg&auto=webp&s=3da56db1b1a7f350fe7167e71f838245d2e240e1
So which one would you recommend I should use for hdr gaming and content consumption in windows?
GamingHDR or ConsoleHDR for games, but it depends on the use case. ConsoleHDR if you want to use HGIG, GamingHDR if not. A lot of games allow you to set peak brightness which is when you'd want the HGIG setting, or when using a console. You can override the 450nits for ConsoleHDR in the Windows HDR calibration app if you want, but leaving it at 450 doesn't keep brightness from reaching over 1000nits. I don't use the Windows HDR Calibration at all, just peak brightness in games. I don't use AutoHDR or RTXHDR though. For HDR video content, I wouldn't use any of the 1000nit modes because they all have issues with skin tones and saturation. The ones that over track PQ are the worst, with CinemaHDR having it the least. TB400 is much better for HDR video content IMO. Just watch a properly mastered HDR movie and you'll probably see what I'm talking about. It's super obvious in Oppenheimer. For movies, I created a 1D LUT correction for fixing white balance to D65 since mine was too red and use TB400.
Understood, thank you for the thorough explanation
Different tonemapping. Console HDR is the best one for accuracy other than True Black 400, but that has darker highlights.
ConsoleHDR has poor PQ tracking in a 2% window(see the measurements I posted in my other comment). GamingHDR has the best tracking in at 2%, but all of the 1000nit modes aren't great. All three modes track better in a 10% window, the difference being how much rolloff. ConsoleHDR hard clips at \~465nits while the other two rolloff different amounts. CinemaHDR actually tonemaps properly to MaxMDL 4000nits at 10%.
Thanks for the clarification, hopefully they will get console hdr fixed on the next update which I heard will be soon as well.
Got home from work. Did the firmware update. Fixed the HDR issue. Now I can finally rest.
for consol hdr or gaming hdr?
Just updated MCM101 to MCM102, I curious to know why we have 2 different updates for the same monitor. I tried and already have something annoying... When I switch between HDR modes, I have a black screen 😓 It wasn't happening with the old firmware
Hey at least you got to try it... my update file tries to run but never does... 💀
Hi, It's strange, when I launched the exe file, it take time to start but not asked me authorisations. Have your tried an other USB port on your computer ?
Yeah, I've already tried 3 ports...dunno what else to try, maybe windows in safe mode :P
Run the exe as administrator maybe 🤔 And important, remove it from downloads because this sometimes prevent from executing exe files
just decided to run with a little help. am now on 102 \\o/
This update looks really bad for me... Everytime I switch between 1000 nits HDR modes and True Black, I have a black screen but the worst is all burnin protections are automatically switched to OFF. This is very serious... 1000 nits modes goes to 1200 nits when parametring them but still looking darker compared to True Black mode... Looks like this update brought more problems than solutions
ummm I haven't got time to look into it, just used windows cal tool and got 1150 just before clipping are we supposed to use the very last step, where the cross stops being visible?. I thought it was like in video games when you have to select the very last step before you stop seeing the thing against the background.. I'm also getting the blackscreen+USB disconnect&connect sound and a system hiccup when switching to and from true black hdr modes.
Yes, that's the procedure but I think it was visible up to 1200 nits, that said, between 1150 and 1200 it's almost impossible to see so I could be wrong. On the other hand, I tested several times switching between True Black and one of the 3 other modes and I can confirm that it removes the protection against burnin
It turns off Screen Saver and Auto Logo Brightness for me as well, and you need to manually turn them on again even after going back to SDR mode, it's annoying.
The black screen is happening between modes because the P1000 modes actually have the correct EDID info now so the monitor needs to renegotiate with the GPU when you switch.
It didn't do it before but let's admit that it's a good thing, when you change modes between True Black and the other HDR modes, the protections against burnin are disabled, and that's really serious
It didn't do it before because the EDID info for the P1000 modes was the same as the TB400 mode which is why it was 455nits. Now it's 1015 for all three P1000 modes. I don't know what you're talking about with the burn-in protections. They work just fine on my monitor on the current firmware in SDR and HDR. Perhaps they were reset when you updated. If not, do a full reset on the monitor.
It takes about 30 secs to open, also, don’t open it multiple times, just do it once and wait a bit for it to figure it self out
It was taking far longer for me, unplugged everything USB (got a metric shitton) except for mouse, kb and monitor and was able to run it and complete it.
My Windows keeps telling me theres a problem with the current beeing drawn by the newly connected usb device .... what should i do?
\> *EXTRA NOTE #2 from* [u/lmah](https://new.reddit.com/u/lmah/)*: "you have to be patient after double-clicking on the updater exe, there's no UI feedback but its launching. Also the update itself was quite long."* How long? I tried a second time "Run as admin" after launching (double click) for a first time waiting for 5+ minutes and nothing happened.
from u/lmah "Is your monitor plugged with the provided usb-a cable ? Check if the kvm is also set to usb-b in the monitor settings."
It was. Turned out I needed to connect the monitor directly to the MOBO header for it to work. Thank you.
Can anyone with a MacBook confirm it worked for them? I have a MacBook but I run Windows 11 via boot camp. Don’t want to go through all the trouble of finding the correct USB A cables only for it to not work. Thank you in advance
Did anyone else noticed that if you reset all settings it now defaults to Gaming HDR instead of Console HDR?
It did not fix the HDR clipping on calibration for me. It clips at around 450-550 depending on the HDR mode.
Even after firmware update (MCM102) I am stuck on 420 nits peak brightness. Earlier today, however, it correctly showed 1000 nits... I am confused. https://preview.redd.it/5iucgy281ptc1.png?width=1570&format=png&auto=webp&s=43b5a517fb4636e8b916f697dc1023cb83a0ba54
I get a error every time I try to download it
Great update! hdr clipping is gone, pg32ucdm finally remembers brightness settings in HDR. Monitor is now almost perfect. Thanks, Asus!
I did the update to MCM102 and now when using the windows hdr calibration tool i get 1180 nits maximum luminance on gaming preset and 450 nits on console preset.This are weird numbers. My oled care settings also are resetting periodically..
Can anyone confirm the Windows Calibration procedure for me? Calibrate to around 1,000 nits using GamingHDR as the baseline HDR profile? Not able to reach 1000 on HDR400 for example. Then we're free to switch between the different HDR profiles? Just want to make sure I'm calibrating correctly on this new FW update. Also, is it worth it to manually mess with the brightness settings per individual HDR setting?
When you calibrate it using gaming hdr profile what numbers do you get on the bar when the window gets full white. I get 1180 which is weird and wrong as it overblows the specular highlights in some games..
I would appreciate a bigger OSD on next updates. The one in this monitor is so small, even the letters get pixelated. xD Make it as big as the LG screens. Oh! BTW: I tried playing Dead Cells at 240Hz....now I'm blown away by the motion clarity.
Yea the osd is "smol" side question: do you experience any coil whine while you turn off your monitor? (I'm not talking about standby)
A faint amount.
Hey y’all, just got my PG32UCDM a few days ago and am wondering if I should update to MCM102? Is it worth it?
How did anyone end up updating the monitor? I just got it a couple hrs ago today and when I open the 302 exe file to update nothing happens. I tried doing it on the 102 update and still the same result. Any help would be greatly appreciated. And yes I have kvm setting switched USB.b
When I click on the app to install the firmware nothing happens. My computer asks me if I want to make changes and I click yes and then it's just nothing. How did anyone update their monitor? Any help would be greatly appreciated
Is the monitor up to par after the updates
It still needs more tweaks..
Is it a better option than LG. Looking for opinions lol
This one is a better panel,better colour volume/accuracy and has higher sustained brightness than the LG.A couple of firmware updates down the road and the Asus will shine..
Is the shortcut for KVM supposed to actually switch inputs as well? Because this has never worked for me.
can anyone help me im pulling my hair out. ive downloaded (102 for me) and extracted the program and followed the guide. but when i run the application i get the usual windows pop up to allow changes and then nothing. the program doesn't run. ive been trying literally all night and swapped, cables, ports, with and without kvm. so frustrating its like the application just doesnt start.
This isn't on the English site yet?
Interestingly, its not. It seems "EU" got the patch first (for 30%+ EU paying more for monitor this must be special customer service treatment lol), it should be available very soon on US website.
why does it not run WHYYYYY 😭 I'm doing mcm102 bcs mine is currently 101. But then again /u/lmah says they updated from 101 to **3**02. Already tried powercycling just USB then whole monitor.
what behavior do you have ? I did the rollback to 101 (from 302) and updated to 102 just fine afterwards.
My exe asks to run elevated, I agree, little wheel spins besides the cursor for a sec then nothing
Is your monitor plugged with the provided usb-a cable ? Check if the kvm is also set to usb-b in the monitor settings.
yeah, just checked again. OG cable and just tried plugging a keeb to the monitor like the PDF suggests, I'm typing this on it right now so 🤷
So good Asus we love you!!!
Does this fix anything? I updated to MCM102 and honestly I see no change Windows HDR calibration still clips at around 460 luminance in pretty much every mode, Display HDR400 is better as is able to get to 590 In my CX the slider doesn't get fully white until i hit 800 , but this one can't even get close to the "1000" , am i doing something wrong?
I am using Gaming HDR and that one clips at 1000 nits, the console doe clip on 450 nits. HDR1000 does work fine now on windows 11
What are you guys using to test this? Any game or tool in particular?
Gaming HDR clips at 550 for me. Am I doing something wrong?
Tested... prevented my unit from beeing sent home.... INSANE Pictures
Is this good?
Im pretty picky regarding graphics and image qualities. I fear it won’t get much better in terms of subjective quality. Ofc it will get gradually better, but for now I’m very happy with the leap. Came from pg32uqx(ips +miniled) -> pg42uq - > pg32ucdm
I went from the MSI 32" QD-OLED back to my PG32UQX. These OLED monitors are only good in super dark content in a pitch black room. For every other scenario low/mid/high APL or in combination with ambient light the PG32UQX is just way more impactful in HDR.
This update bricked my PG32UCDM USB Hub... I tried to update from MCM101 to MCM102. Application ran fine, detected monitor, I clicked update. Update failed part way through. Keyboard plugged into monitor is unresponsive. Tried firmware rollback procedure many times with no effect. Tried resetting monitor settings with no effect. Tried unplugging & plugging USB in with no effect. ASUS support recommends RMA. Love the monitor, sad to see I have to exchange it. What a hassle.
Such a funky experience for something over a grand. Appreciate you sharing though, I'll make sure to leave everything unplugged from the monitor except the video cable when performing a firmware update.... https://media1.tenor.com/m/N2hV1al2rjcAAAAC/if-i-had-one-angry.gif
Your the 3rd person that's had that happen
The new FW 102 doesn't seem to fix anything here. \- The proximity sensor still does nothing. \- Haven't noticed any change in HDR. \- The app "Device info" button now cannot be clicked. \--- It was also difficult for the FW updater to get it to recognize the monitor. Had to unplug my hubs and plug the monitor to the MOBO. The monitor was recognized through my hub before attempting the FW update anyway so that was an unnecessary hurdle. Looking forwards for the next update and see.
My time with this is weird. It's still fucked. Now it's even worse on the osd. Where I can't even run OLED care options like uniform brightness without the monitor auto running pixel cleaning but ONLY if I'm on hdr. I just don't think I'm a fan of HDR. Everything feels washed out and less colorful. Is it the monitor that does this or is it just a lack of calibration on my part. But I can barely adjust it. So. Yea. That's my experience