Flaimbot

joined 2 years ago
[–] Flaimbot@lemmy.ml 0 points 1 year ago (4 children)

i dont disagree with it being in a decent state. i'm just annoyed by the marketting around it, which is deceiving, if not flatout lies.

[–] Flaimbot@lemmy.ml 0 points 1 year ago (6 children)

the problem imo is that it's advertised absolutely incorrectly. they make it sound like the tech makes the game run faster. it doesn't. it leverages the free resources due to the cpu bottleneck in order to interpolate frames, like those 2010's tvs with their "9000hz motion" interpolation. it's okay for smoothing out jerky frame movement in solo third person rpgs and stuff like that, but absolutely disgusting and unusable for first person shooters. yet, following the gaming subs on reddit, people are gushing over it like it's free real performance increases out of thin air.

2
submitted 1 year ago* (last edited 1 year ago) by Flaimbot@lemmy.ml to c/openrgb@lemmy.ml
 

after having some issues with my igpu (7800X3D), i decided to disable it in uefi.
i'm running win10 (22h2, 19045.4651).

as for the description what i was seeing:

  • i disabled the igpu in uefi
  • reboot
  • crash of OpenRGB upon starting up/scanning devices
  • i deleted %appdata%/OpenRGB
  • i ran the .exe as admin
  • as soon as the scan went over the gpu (gigabyte gtx1080 ti aorus master) the programm CTD'd again
  • disabling all detectors in OpenRGB.json allowed me to launch the app again
  • in the settings i was able to reenable the mobo detection without issues and passed rescanning the devices
  • in the settings reenabling all gigabyte device detections triggered the CTD upon rescanning again

at least it was able to log something to that point:

https://pastebin.com/fhnEddij

what i noticed in the logs is the following weird message:
for some reason my mobo (an ASUS TUF GAMING X670E-PLUS WIFI) is being identified under gigabyte:

7325 |Debug: [Gigabyte RGB Fusion 2 SMBus] FAILED - 'TUF GAMING X670E-PLUS WIFI' was not found in the JSON list. Do NOT enable if this is a USB based board.

to me it seems that disabling the igpu somehow has messed up the enumeration of the devices/ids/slots, which led to the mobo being somehow wrongfully pushed up to the gpu slot, or something along the lines.

edit: before any questions arise, i'm running version 0.8, but upgrading to version 0.9 yielded no change in behaviour, which is why i downgraded again.