Crash when enabling "Color Feedback" (LED)

[Mehmet bey]

@racemodder Thanks a lot for testing this out and confirming! It's great to know the exact cause is the compatibility issue between the 1.60 update and the SDK.

Honestly, it's ridiculous that they haven't fixed this after three months. I reported this issue a month before going on vacation, spent two months away, just got back yesterday, and it's still not fixed! I really appreciate your update, though.

[racemodder]

00:00:13.577 : [color_feedback] Detected 2 ASUS AURA devices.
00:00:13.577 : [color_feedback] Detected ASUS AURA device 'Mouse' of type mouse (589824) with grid 1x1.
00:00:13.577 : [color_feedback] Detected ASUS AURA device 'WindowsLighting_LED' of type keyboard (524288) with grid 19x6.
00:00:13.623 : <ERROR> d:\buildbot\slaves\win_slave\final_build_ats_161_windows_bin_steam_x64\build\prism\src\p3core\collections\arrays\arrays_base_impl.h(573): ??A?$array_t@V?$array_dyn_t@V?$vec_t@M$02@prism@@@prism@@@prism@@QEAAAEAV?$array_dyn_t@V?$vec_t@M$02@prism@@@1@_K@Z: Index outside array boundaries: 225 >= 6




yes check new update 1.61 Ats but same problem

[Mehmet bey]

racemodder Thanks for sharing the crash log! That ⁠Index outside array boundaries: 225 >= 6⁠ clearly shows it's an out-of-bounds array exception in the game's prism engine core.

Since the keyboard grid is 19 \times 6, trying to access index 225 naturally crashes the game. This confirms it's a coding bug on SCS's side when handling the Aura SDK matrix. Hopefully, an SCS developer sees this log and fixes the boundary check in a future patch.

[Madkine]

@Mehmet bey If you think it's a bug, make a bug report in the bug forums.

You can find guidance on how to prepare a complete and helpful report in our bug reporting rules.
For this report, the following information is especially important:

Full game log file

These details help us locate the issue and understand the exact game setup used.
The game log file contains key information for troubleshooting, including game version, active mods, map, system specifications, launch parameters, DirectX/OpenGL mode, game settings, and GPU driver version.

With these details, we will be able to reproduce the issue more easily and look into it further.
We appreciate your cooperation.