View Issue Details

IDProjectCategoryView StatusLast Update
00306312.x IDE BugsGeneralPublic2019-08-21 15:23
ReporterDanAssigned ToCoreTech 
PriorityLowSeverityC - GeneralReproducibilityUnable To Reproduce
Status AssignedResolutionOpen 
Platform-OSWindows 10OS VersionPro x64
Product Version2.2.1 
Target VersionFixed in Version 
Summary0030631: General: Corsair K55 RGB keyboard causes increasing delay starting the runner at the end of builds
DescriptionWe do not have this keyboard yet, but we have a handful of reports that the Corsair K55 RGB keyboard causes an increasing delay starting the runner at the end of builds. The delay before the runner starts builds up over each project build, until it can be minutes between the output window saying the game is starting and the game actually appearing.

Simply unplugging the keyboard, waiting a second or two, and then plugging it back in has been confirmed to "reset" the issue. Rebooting the PC will do the same.
Steps To Reproduce1. Have one of these keyboards.
2. Build a project in GMS2, stop the game, build again, repeat.
3. Observe the delay between the output window saying the game is launching and the game actually launching starts to grow.
Additional Informationhttps://www.currys.co.uk/gbuk/computing-accessories/computer-accessories/mice-and-keyboards/keyboards/corsair-k55-rgb-gaming-keyboard-10158187-pdt.html
TagsGM2KI, GMKI
2.x IDE Found In2.2.1.375
2.x Runtime Found In2.2.1.287
2.x IDE Verified In
2.x Runtime Verified In

Activities

Dan

2019-03-19 14:02

Adminstrator   ~0063528

Going back in our tickets, we actually have a ticket from last August which I believe to be the same issue. In that one, the user's DXDiag contained a number of crashes in CorsairLink4.Service.exe, which I had Googled at the time and found a number of irate threads about this service causing CPU drains and other instability problems for a variety of other software programs.

For anyone with this issue now, please see if you have the same crash messages for CorsairLink4.Service.exe in a DXDiag report or Windows Event Viewer.

This may not be fixable by us.

Dan

2019-03-19 14:14

Adminstrator   ~0063529

One of our new tickets has a Corsair Service crash in it also:

+++ WER4 +++:
Fault bucket 1296645125711721986, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Corsair.Service.exe
P2: 3.11.0.28
P3: 5c18ea7c
P4: System.Management
P5: 4.7.3056.0
P6: 5a8e5a11
P7: 8a
P8: 51
P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
P10: