EBYRWA Posted Friday at 02:37 PM Posted Friday at 02:37 PM 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: 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? Can that layout use a static background image plus dynamic text, gauges, and state images bound to ImportValues? Will AIDA64 automatically refresh the RYUJIN when those registry values change, without reapplying the layout? Are ROG LCD updates through ROGAIOSDK.dll volatile buffer updates, with no image/profile/flash-storage writes? Is Armoury Crate display control simply required to remain OFF while AIDA64 owns the LCD? What refresh interval do you recommend for this device? I intend to use no more than 1 update per second and suppress unchanged values. 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? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.