You can run OpenRGB.exe with --nodetect to skip detection IIRC, then disable all devices in the settings menu. You can then enable them one by one to track down the offending detector. The Gigabyte thing looks to just be a debug message where that controller sees your motherboard is (rightfully) not on its list, so I don't think that is the problem.
narrowed it down to the "Gigabyte GTX1080ti 11G" detector. all except that one can be left enabled. as soon as i add that one for my graphics card into the mix, openrgb crashes.
the confusing part here is that only after disabling the igpu this happens. if i reenable the igpu, things are back to normal with all detectors being able to correctly identify all their components.
any idea why that might be?
this post was submitted on 22 Jul 2024
7 points (100.0% liked)
OpenRGB
433 readers
1 users here now
The official Lemmy community for the OpenRGB project.
Official website: https://openrgb.org
GitLab: https://gitlab.com/CalcProgrammer1/OpenRGB
founded 3 years ago
MODERATORS