PC Corsair RGB on Other Peripherals

[Zandodak]

I'm wondering why my PC tower goes dark when I boot up Terraria, as the game's SDK should take advantage of my other RGB peripherals. I've gone into my configs and turned all Corsair RGB options to "True". Specs are below, labelled if they're working. Appreciate the help as I can't seem to find anything online in regards to this.

Specs:
Corsair K95 RGB Platinum (SDK Works)
Corsair Scimitar Pro RGB (SDK Works)
Corsair MM700 RGB (SDK Works)
Corsair LL120 RGB Fans
Corsair Vengeance RGB PRO SL
ASUS Motherboard

As an aside, I've contacted Corsair support to see if it's an issue with the hardware, and apparently the integration doesn't exist on their end.

 

[Kazzymodus]

Hey @Zandodak, I'm sorry to hear you're having issues with your RGB peripherals.

I would like to get some more information on what is happening internally. Could you please follow these steps?

1. In your Steam Library, right click Terraria and click Properties....
2. Under the General tab, add the following to the Launch Options field: -logerrors -logfile.
   
3. Close the window, then launch Terraria as usual.
4. When the main menu has fully loaded, exit the game.
5. Close Terraria, then go to Documents/My Games/Terraria/Logs. Please upload the most recent log to this thread so I can take a look.

 

[Zandodak]

@Kazzymodus I've attached the log file to the thread.

Appreciate your time and patience!

 

[Kazzymodus]

@Kazzymodus I've attached the log file to the thread.

Appreciate your time and patience!

Going by your log, I think there's an issue with your config file. Would you mind uploading it to this thread?

 

[Zandodak]

It should be worth noting that I use both base and tModLoader.

The one that's 3.6 KB is my base game, the one that's 6.2 is my tModLoader. Both instances have the same issue.

 

[Kazzymodus]

It should be worth noting that I use both base and tModLoader.

The one that's 3.6 KB is my base game, the one that's 6.2 is my tModLoader. Both instances have the same issue.

Okay, that's strange - your config file seems to be fine, it shouldn't be generating the error in your log.

As a sanity check, could you run Terraria again and upload the newest log? Also, when you launch Terraria, does it ask you to choose your language?

 

[Zandodak]

Latest one!

If nothing else I can check the integrity of the cache on Steam.

 

[Kazzymodus]

Latest one!

If nothing else I can check the integrity of the cache on Steam.

Thank you! As I expected, the error in your previous log is gone, so that's one mystery solved.

I've done some more investigating, and I believe I understand what's going on, however as of this moment I'm not sure if there is something we can do about it - it may be a limitation of the integration itself. I will raise this internally for further investigation and we'll see if we can do something about this. My apologies for the inconvenience.

 

[MegaBytesMe]

Hi, I've done some testing myself. This is my Corsair setup:
1) 4x Vengeance RGB PRO (RAM)
2) K100 RGB (keyboard)
3) DARK CORE PRO SE (mouse)
4) 3x LIGHTNING NODE PRO (controls lighting for fans, strips etc)
5) MM800 RGB POLARIS (mouse mat)
6) MM700 RGB (big mouse mat)

Whenever I have the mouse (DARK CORE PRO SE) enabled in the iCue SDK settings, the Terraria log shows this:

Error Logging Enabled.
Resolution changed to: 800x600.
================
12/23/2024 12:49:27 AM: First-Chance Exception
Thread: 1 [Main Thread]
Culture: en-US
Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at ReLogic.Peripherals.RGB.Fragment.CreateCanvasPositions(Point[] gridPositions)
HResult: -2146233080
================

Corsair RGB not supported: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at ReLogic.Peripherals.RGB.Fragment.CreateCanvasPositions(Point[] gridPositions)
   at ReLogic.Peripherals.RGB.Fragment.FromGrid(Rectangle grid)
   at ReLogic.Peripherals.RGB.Corsair.CorsairMouse.Create(Int32 deviceIndex, CorsairDeviceInfo deviceInfo, DeviceColorProfile colorProfile)
   at ReLogic.Peripherals.RGB.Corsair.CorsairDeviceGroup.AddDeviceIfSupported(Int32 deviceIndex, CorsairDeviceInfo deviceInfo)
   at ReLogic.Peripherals.RGB.Corsair.CorsairDeviceGroup.Initialize()
Corsair RGB unitialized.
Corsair RGB unitialized.
================
23/12/2024 00:49:41: First-Chance Exception
Thread: 4 []
Culture: en-GB
Exception: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort()
HResult: -2146233040
================

When I disable the SDK control in iCue SDK settings for the mouse (DARK CORE PRO SE), the other peripherals function and no error is shown in the log! So that works for me (at least partially)...

The same thing even happens after updating the outdated iCue SDK version to the latest (non-breaking change) iCue SDK, v3.0.464 (the one bundled with Terraria is outdated, using v2.10.91). I'm not sure why the bundled SDK is so old, considering the latest v3 SDK works out of the box with no changes, and the v4 SDK would have further support (although has a breaking change from v3).

Also, only the mouse, keyboard and mouse mat seemingly has support - None of the other peripherals do. I'm not sure why the devs opted to show nothing over showing something like a base colour instead using the SDK (as a dev myself I can confirm it isn't hard to select all the other peripherals and set them to a select colour using the SDK).

Hope that helps!

 

[Kazzymodus]

Hi, I've done some testing myself. This is my Corsair setup:
1) 4x Vengeance RGB PRO (RAM)
2) K100 RGB (keyboard)
3) DARK CORE PRO SE (mouse)
4) 3x LIGHTNING NODE PRO (controls lighting for fans, strips etc)
5) MM800 RGB POLARIS (mouse mat)
6) MM700 RGB (big mouse mat)

Whenever I have the mouse (DARK CORE PRO SE) enabled in the iCue SDK settings, the Terraria log shows this:

Error Logging Enabled.
Resolution changed to: 800x600.
================
12/23/2024 12:49:27 AM: First-Chance Exception
Thread: 1 [Main Thread]
Culture: en-US
Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at ReLogic.Peripherals.RGB.Fragment.CreateCanvasPositions(Point[] gridPositions)
HResult: -2146233080
================

Corsair RGB not supported: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at ReLogic.Peripherals.RGB.Fragment.CreateCanvasPositions(Point[] gridPositions)
   at ReLogic.Peripherals.RGB.Fragment.FromGrid(Rectangle grid)
   at ReLogic.Peripherals.RGB.Corsair.CorsairMouse.Create(Int32 deviceIndex, CorsairDeviceInfo deviceInfo, DeviceColorProfile colorProfile)
   at ReLogic.Peripherals.RGB.Corsair.CorsairDeviceGroup.AddDeviceIfSupported(Int32 deviceIndex, CorsairDeviceInfo deviceInfo)
   at ReLogic.Peripherals.RGB.Corsair.CorsairDeviceGroup.Initialize()
Corsair RGB unitialized.
Corsair RGB unitialized.
================
23/12/2024 00:49:41: First-Chance Exception
Thread: 4 []
Culture: en-GB
Exception: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort()
HResult: -2146233040
================

When I disable the SDK control in iCue SDK settings for the mouse (DARK CORE PRO SE), the other peripherals function and no error is shown in the log! So that works for me (at least partially)...

The same thing even happens after updating the outdated iCue SDK version to the latest (non-breaking change) iCue SDK, v3.0.464 (the one bundled with Terraria is outdated, using v2.10.91). I'm not sure why the bundled SDK is so old, considering the latest v3 SDK works out of the box with no changes, and the v4 SDK would have further support (although has a breaking change from v3).

Also, only the mouse, keyboard and mouse mat seemingly has support - None of the other peripherals do. I'm not sure why the devs opted to show nothing over showing something like a base colour instead using the SDK (as a dev myself I can confirm it isn't hard to select all the other peripherals and set them to a select colour using the SDK).

Hope that helps!

This is a distinct issue with the Corsair Dark Core RGB Pro SE, which is caused by an issue on our end. In practice this means we unfortunately don't support this mouse as the time, but we're hoping to have a fix for this in the next update.

 

[ErikVergani]

Hey everyone, I came across this post and wanted to share my experience.

Some time ago, everything was working fine in iCUE, but then, out of nowhere, it stopped. Today, I went back to gaming and felt frustrated because the device integration still wasn’t working.

After doing some research, I checked the config.json file and noticed that UseCorsairRGB was set to false, so I changed it to true. As soon as I launched the game, the SDK was recognized by iCUE 5 (it worked fine in iCUE 4 but stopped after I upgraded to 5). I approved the usage, but the integration still wasn’t applying the colors.

I couldn't find any information on this until I came across this thread. While checking Zandodak’s configuration files, I noticed that my file wasn’t generating the CorsairColorProfile entries. I copied and pasted the relevant section, and the integration worked 100%! I have a K95 Platinum XT, Corsair Nightsword, and HS80 Wireless, and everything integrated perfectly.

I’d like to report that this piece of code and the integration should work natively. I’m happy I managed to fix it, but it’s frustrating to see that some settings aren’t being generated automatically when launching the game.

Attached, I’ve included the file "error without ...", which is the log generated when running the game before adding the missing configuration. The other file was generated after manually adding the missing section—there are no errors logged, and everything works perfectly.