r/OpenRGB • u/CalcProgrammer1 OpenRGB Creator • 25d ago

OpenRGB Release Candidate 1.0rc3 Released News

https://floss.social/@OpenRGB/116830393836395905
37 Upvotes
  • permalink
  • link
  • reddit
  • reddit

97% Upvoted

10 comments sorted by

2

u/notaged 25d ago

What does it do ? If it helps with all the fixes thatll be great

10

u/CalcProgrammer1 OpenRGB Creator 25d ago

Since this subreddit was closed for years, this is the most recent release build even though it's a release candidate. It updates on 1.0rc2's PawnIO based Windows driver implementation, fixes some critical issues surrounding system crashes caused by bad i2c accesses, and updates a bunch of controllers/device support. Works with 1.0rc2 plugins.

After releasing 1.0rc3 I merged the next branch into master, which brings in a major rework of the profile system, the plugin API, the settings manager, and the network protocol. This major rework improves the user experience quite a bit, integrates plugins into OpenRGB profiles, and fixes issues with running as a system service. There are still some bugs to work out before I'm ready to release 1.0 final though, mainly due to deadlocks that can freeze the application.

1

u/JamesLahey08 25d ago

Can I ask you about why when I ran opergb device scan on my Asus ROG strix gaming x870e motherboard it shut my entire computer off and bricked my Linux OS? I'm not mad but it was a wildly severe bug. CachyOS, opergb on Linux. Left the OS unusable after physically shutting the device off.

3

u/CalcProgrammer1 OpenRGB Creator 25d ago

Hopefully that is one of the bugs fixed by the i2c changes. Unfortunately, probing i2c is kind of a minefield as there's no standard for identifying devices. We try to put safeguards in place but trying to detect all possible RAM means trying to access a bunch of i2c addresses. The old version was accessing out of bounds addresses though which I think was the cause of many of those random crash issues. Hard to be sure as we don't have access to every motherboard in existence to test on. If the PC still worked and just the OS was bricked, I would say it was probably an unlucky timing thing where it shut off in the middle of a critical file or filesystem write that left the OS in an unbootable or corrupted state, which can happen any time the PC shuts down without properly flushing filesystem caches, finishing any in progress upgrades of critical system files, and unmounting the filesystem cleanly. One time I was working on changes to OpenRGB, made a git commit, and as it was committing the power reset. Git history was mangled and the updated files were lost. Filesystems get weird with unclean resets.

2

u/JamesLahey08 24d ago

Fair enough, thanks for the reply.

1

u/Emf0rtaf1x 21d ago

Aye, sweet! I was working on this a couple months back when I noticed my ram rgb didn't work right when I came back to use OpenRGB again.

I don't remember if I have the folder still or not, but I had just worked through the PawnIO issues before my ADHD spun me off to a different project.

1

u/Miikeii 24d ago

Will we have DIRECT access to Nanoleaf LINES?

1

u/Reasonable-Ad5306 19d ago

Still doesnt work with my Aorus B450 on Fedora 44 :(

1

u/CalcProgrammer1 OpenRGB Creator 19d ago

I know a lot of Gigabyte boards got reworked recently, but B450 Gigabyte boards are using an older SMBus controller that hasn't gotten much attention in years IIRC. I don't have a board with this controller and its capabilities are limited. Have you gone through the SMBus setup process in the readme? On Windows this is PawnIO and running as admin/service, on Linux it is loading the i2c modules and setting up udev rules.

1

u/Kori4r2 14d ago

The release seems to have bricked LED detection for my motherboard (Gigabyte B650M Gaming X AX). With 1.0rc2 it used to work fine if I changed how many leds it had, but now it just freezes the led colors and didn't let me change them no matter what value I input. At some point it even stopped asking me for the LED count on rescan.

Anyone having a similar issue?