Arctis Pro Wireless OLED problems about gamesense-sdk

[JHunz]

We're aware of this issue. It's something that occurs occasionally when writing image data to the OLED screen, and unfortunately our firmware vendor was unable to provide us with a fix. I wish I had a more useful response.

[adamscybot]

It is sadly broken on all of them out of the box and this is admitted in this thread. In most countries you therefore have grounds for a full refund.

…

________________________________ From: Corey Deli <[email protected]> Sent: Wednesday, February 3, 2021 10:27:14 PM To: SteelSeries/gamesense-sdk <[email protected]> Cc: Adam Thomas <[email protected]>; Comment <[email protected]> Subject: Re: [SteelSeries/gamesense-sdk] Arctis Pro Wireless OLED problems (#66) @JHunz<https://github.com/JHunz> Any update at all???? This is insane! This is a $329 product and it cant handle multiple requests. Mine started to happen when I bought my Apex Pro keyboard. This issue NEEDS to be resolved as I would wager this would affect sales once more and more people have this problem. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#66 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJHTIJR76WV55RALBNYMYLS5HEUFANCNFSM4HVQSX5Q>.

[LofhJann]

This MIGHT be fixed with SSE 3.15.0, at least haven't noticed problems yet after installing 3.15.0, enabling Discord and running some test messages through

[LofhJann]

Nope... Not completely fixed, after re-login it happened once again. Haven't seen it since so at least seems like it's gotten better after last patch

[adamscybot]

Also seeing this. The discord app alone seems enough to trigger the issue. Looks to be a widespread issue but sadly, no response from steelseries.

Might be worth raising a support request with steelseries and reference this issue. I'm unsure if they are even aware.

[LofhJann]

Any update on this issue? Is firmware update still coming up or is it "working as intended" ?

[aph3rson]

@JHunz any updates on this? This is still an issue with SSE 3.18.2, firmware 2.3.0.0.

[coreydeli]

@JHunz Any update at all???? This is insane! This is a $329 product and it cant handle multiple requests. Mine started to happen when I bought my Apex Pro keyboard. This issue NEEDS to be resolved as I would wager this would affect sales once more and more people have this problem.

[snigel]

We're aware of this issue. It's something that occurs occasionally when writing image data to the OLED screen, and unfortunately our firmware vendor was unable to provide us with a fix. I wish I had a more useful response.

It would be nice to know why your vendor is unable to fix this. Is it because it's an unfixable hardware issue? Is it because it's expensive to fix? Is it a question of who is going to pay for it?

If your vendor won't fix their broken code, have you considered taking ownership of the firmware source code?
Then you would have the possibility to let someone fix it or outsource it to the FOSS community.

[Ruffio]

I just 'lost' my display in OLED display. The only plugin I use is for CSGO.
Rebooting the computer or pushing the buttons doesn't solve it. However I read that if I disconnected and reconnected the USB-cable, then I would work again, and it does :-)

I think my issue occured right after swapping batteries, so it could be a hardware issue, since this issue has been active for two years now.

[thebradler]

We're aware of this issue. It's something that occurs occasionally when writing image data to the OLED screen, and unfortunately our firmware vendor was unable to provide us with a fix. I wish I had a more useful response.

Who is the firmware vendor? And what is the reason they can't provide a fix? They don't know the issue? How about instead of just dropping the issue you outsource it to the community or look to other resources for help?

[Zenger]

Sorry to dig up an old thread, but is there a list which report descriptor belong to which devices? So far I'm trying to find the right devices to get battery status, I know that Arctis 7 2019 and Arctis 7 2017 both respond to {0x06, 0x18} if I target devices that have usage page > 1, but this does not work for Arctis 7+ or Arctis Nova Pro Wireless the only other devices I have access to test on. I've never worked with HID devices before so its all new to me.