ROG Ryujin II LCD: custom ImportValues layout and volatile updates?

[EBYRWA]

I’m building a personal, normal-user Windows hardware-status application for an ASUS ROG RYUJIN II, USB VID 0B05 / PID 1988, with its 320×240 display.

I’d prefer to keep AIDA64 as the sole display owner. My application would publish telemetry through the documented registry interface:

HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues

using Str1–Str10 and DW1–DW10. I would configure the LCD layout once in AIDA64, then let AIDA64 automatically render updated values to the RYUJIN.

Could you please confirm:

1. Does the ROG RYUJIN II LCD module support a fully customized LCD Items layout containing imported registry values, or is it limited to the four ROG preset layouts?
2. Can that layout use a static background image plus dynamic text, gauges, and state images bound to ImportValues?
3. Will AIDA64 automatically refresh the RYUJIN when those registry values change, without reapplying the layout?
4. Are ROG LCD updates through ROGAIOSDK.dll volatile buffer updates, with no image/profile/flash-storage writes?
5. Is Armoury Crate display control simply required to remain OFF while AIDA64 owns the LCD?
6. What refresh interval do you recommend for this device? I intend to use no more than 1 update per second and suppress unchanged values.
7. Does normal ROG LCD operation require administrator rights or any AIDA64 feature beyond an ordinary AIDA64 Extreme license?

My application will not access the cooler HID interface or expose pump, fan, firmware, lighting, or other control operations.

If imported values are not supported by the ROG LCD module, is there an officially supported way for a personal third-party application to use the display-only ROGAIOSDK.dll buffer API without redistributing the DLL?

[EBYRWA]

Just writing to bump this post. Hoping to get some useful response

Thanks in advance for reading.

[Fiery]

On 7/31/2026 at 4:37 PM, EBYRWA said:

I’m building a personal, normal-user Windows hardware-status application for an ASUS ROG RYUJIN II, USB VID 0B05 / PID 1988, with its 320×240 display.

I’d prefer to keep AIDA64 as the sole display owner. My application would publish telemetry through the documented registry interface:

HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues

using Str1–Str10 and DW1–DW10. I would configure the LCD layout once in AIDA64, then let AIDA64 automatically render updated values to the RYUJIN.

Could you please confirm:

1. Does the ROG RYUJIN II LCD module support a fully customized LCD Items layout containing imported registry values, or is it limited to the four ROG preset layouts?
2. Can that layout use a static background image plus dynamic text, gauges, and state images bound to ImportValues?
3. Will AIDA64 automatically refresh the RYUJIN when those registry values change, without reapplying the layout?
4. Are ROG LCD updates through ROGAIOSDK.dll volatile buffer updates, with no image/profile/flash-storage writes?
5. Is Armoury Crate display control simply required to remain OFF while AIDA64 owns the LCD?
6. What refresh interval do you recommend for this device? I intend to use no more than 1 update per second and suppress unchanged values.
7. Does normal ROG LCD operation require administrator rights or any AIDA64 feature beyond an ordinary AIDA64 Extreme license?

My application will not access the cooler HID interface or expose pump, fan, firmware, lighting, or other control operations.

If imported values are not supported by the ROG LCD module, is there an officially supported way for a personal third-party application to use the display-only ROGAIOSDK.dll buffer API without redistributing the DLL?

1) Yes, you're not limited to using the pre-supplied ROG layouts, you can also build your own from scratch or use an existing LCD layout made by someone else.

2) Yes.

3) No, AIDA64 will refresh the whole screen periodically.  AIDA64 is not watching whether the Registry values change, but simply read the actual values out periodically and use those values to render the LCD layout.

4) It depends on how Asus handles their own hardware using their own SDK (ROGAIOSDK.dll).  But I'm sure they are sensible enough not to ruin the flash memory of the LCD device by unnecessarily updating it at each image transfer.

5) It is once again depends on how Asus handles concurrent access to their hardware via their own SDK (ROGAIOSDK.dll).

6) Last time we measured it, a full image update took 125 millisec on a 320x240 ROG AIO screen. Hence you can freely choose a frequent update rate without overwhelming the system, e.g. half a second would be perfect.

7) Administrator privileges are required by AIDA64 in order to poll sensor values like temperatures and voltages.  It's not tied to the ROG AIO LCD module, but rather is a general requirement.