The INNOCN 32M2V sports a 144 Hz refresh rate IPS panel, supporting the adaptive synchronization technology from both AMD and NVIDIA graphics cards. The adaptive synchronization range is 48–144 Hz, so that's the framerate range your PC should be able to achieve at 4K resolution to experience buttery smooth, screen-tear-free gameplay.
The monitor offers AMD FreeSync Premium support, which means it supports the Low Framerate Compensation (LFC) technology. If the game runs at fewer frames per second than the bottom limit of the FreeSync operating range (48 FPS in this case), the LFC technology displays frames multiple times to stay above the lower limit of FreeSync and maintain the full fluidity of the action. Of course, this "multiplication of frames" is completely invisible to the human eye. Thanks to this approach, the bottom limit of the required number of frames per second become irrelevant and should not be thought about. Of course, for the best possible gaming experience, a high framerate remains something you should strive for.
Response Time and Overdrive
The response time of the INNOCN 32M2V is specified as 12 ms GtG. The panel uses overdrive technology to make the pixel transitions faster, and you will find the option under Game Settings > Response Time in the OSD. Overdrive has four settings: Off, Normal, Fast and Ultrafast.
I tested the response time with the Open Source Response Time Tool Pro (OSRTT Pro), developed by Andrew McDonald of TechTeamGB. It's a nifty tool that, combined with the OSRTT Launcher app, measures panel response times and presents them through detailed graphs and easy-to-read heatmaps. You can find everything you might want to know about the OSRTT in its
technical documentation and on the
official website, where you can order your unit, too. The OSRTT Launcher gives us three interesting heat maps to observe.
Perceived Response Time tells us how much time the panel took to transition from one color to another. This measurement is expressed in milliseconds and includes overshoot. In other words, if the panel exceeded the target value, the perceived response time also includes the time it took for the transition to recover from overshoot and stabilize on the target value. I'm running my tests with recommended settings, so with a fixed RGB 5 tolerance level and with gamma-corrected RGB values.
RGB Overshoot tells us how much a specific transition missed the target value. For example, if the panel was transitioning from RGB 51 to RGB 204, and it initially landed on RGB 212, the overshoot RGB value is 8. Overshoot can be both positive and negative, and it commonly occurs at extreme overdrive settings when pixels are driven by high voltage. In practice, an overshoot manifests as an afterimage or a halo around a moving object. It can be easily spotted even when doing something as basic as scrolling through a webpage.
Visual Response Rating is the most abstract heatmap generated by the OSRTT Launcher; in essence, it's an ever-evolving scoring system. To quote OSRTT's technical documentation, it is a finite score rather than a direct measurement. The calculation is pretty simple; it's: "100 – (Initial Response Time + Perceived Response Time)". Since both metrics use the same tolerance level, if a display doesn't overshoot, both times will be identical. This essentially rewards displays that are fast with a small amount of overshoot over displays that aren't as fast even if they don't overshoot at all – while still overall preferring ultra-fast, accurate monitors.
Here's how the INNOCN 32M2V fares in the pixel response time test at 144 Hz refresh rate with all four overdrive options applied.
The average perceived pixel response varies from 8.88 to 6 ms, depending on the overdrive setting. There's virtually no overshoot to report at any overdrive level, which means you can safely opt for the one that offers the fastest pixel transition times: Ultrafast. It proved to be the best option even at refresh rates as low as 60 Hz.
To measure the input lag of a monitor, I switched from using the LDAT V2 (Latency Display Analysis Tool), which I've covered extensively in my
NVIDIA Reflex review, to the OSRTT Pro Tool. The OSRTT Pro Tool and the accompanying software include a DirectX code developed by Andrew McDonald of TechTeamGB, which allows the OSRTT Launcher to track the events and capture the frame time, making it possible to isolate the monitor latency from other factors that come into play when using the click-to-photon testing methodology, namely the USB polling rate and game render time. For a deeper insight, I suggest you watch an
excellent overview video made by Andy himself.
While I used a consistent methodology in all my previous LDAT-based monitor reviews and kept everything the same, switching to the OSRTT-based approach isolates me from potential issues, such as game engine updates (I based my tests on Overwatch, which transformed into Overwatch 2), and allows me to move on to a different testing system at will. I have to admit it was becoming increasingly annoying having to keep my old Core i9-9900K/RTX 2080 SUPER test system around for nothing but monitor input lag testing. Thanks to Andy for his tireless work on the OSRTT Tool and the OSRTT Launcher software!
Here's how the INNOCN 32M2V holds up in terms of input lag after doing 100 iterations of the input lag test.
The INNOCN 32M2V shows an average input lag of 3.4 milliseconds, which is an excellent result for a gaming monitor. Such low input lag can't be picked up even by the most hardcore gamers.