view the rest of the comments
Steam Hardware
A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to Steam Hardware or Steam OS in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
From a very surface level look at the code it looks like the module disconnects the data coming from steam while OpenRGB is active. But i dont really do C so i might be totally off here.
It does not, but Steam isn't constantly writing to the LEDs. The Customization tab in game mode just lets you pick from the built in hardware effects so it's not continuously writing. That means it generally is not fighting OpenRGB. The only time it does seem to write to the LEDs repeatedly is during downloads when it uses the LEDs as a progress bar. Also, in desktop mode (on SteamOS or on other distros) it does not seem that Steam touches LEDs at all.
Oh okay cool. Thanks for actually checking.