Selecting "RGB Support" in Linux leads to logs swelling to a few GB in a matter of seconds

What went wrong?
Selecting this option in the Linux version does not work well:

  1. The button does react (event is sent), but is visually unresponsive (display not updated)
  2. It seems you programmed a simple loop to load the Logitech DLL (which does not exists on Linux) and the continuous failure to load the DLL pollutes the log, swelling to megabytes of useless data that constantly repeat (millions of times).

Expected behaviour:

  1. The button does not turn on (if already off), remains disabled
  2. The button turns off (if the logitech error occurs)
  3. The failure to load the library happens only once (no forever loop)
  4. The user is expected to click again on the button if the library failed to load the first time
  5. (optionally) a toaster message shows the library failed to load onscreen
DllNotFoundException: Unable to load DLL 'LogitechLedEnginesWrapper': The specified module could not be found.
  at EHG.RGB.Integrations.LogitechIntegration.SetLightingFromBitmap (System.Byte[] bitmap) [0x00000] in <00000000000000000000000000000000>:0 
  at LE.Integrations.RGB.EpochRGB.Update () [0x00000] in <00000000000000000000000000000000>:0
(Filename: currently not available on il2cpp Line: -1)

Version: 0.8.5f linux native
The logs below have been clamped to the first 100KB and compressed: (6.8 KB)


Known problem and RGB Support should not be enabled on LInux…

The game doesnt “gracefully” disable the Logitech feature on Linux - it should but it doesnt… and this does exactly what you found… it will even cause crashes on some systems…

In some cases you even have to edit the configuration manually to disable the RGB feature.

Indeed. Providing here what I mentioned in the other thread to disable by editing config: Random crash on Linux (console output attached) - #15 by amidelapoesie

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.