antonpup / Aurora

Unified lighting effects across multiple brands and various games.
http://www.project-aurora.com/
MIT License
1.83k stars 368 forks source link

Razer Chroma wrapper lighting stuck to QWERTY layout #1286

Open Speedy-VonGofast opened 6 years ago

Speedy-VonGofast commented 6 years ago

Expected behavior:

Adapting keyboard lighting to AZERTY layout

Actual behavior:

Keyboard lighting stuck to QWERTY layout

How often does this problem occur?

This problem occurs every time

Please describe the steps to reproduce this issue:

The issue can be reproduced by doing following steps:

  1. Just play a game using Razer Chroma wrapper with an AZERTY keyboard

What is the version of Aurora you are experiencing this issue with?

My version is beta v0.6.3

Does the previous version of Aurora have this issue?

I didn't check this

Please include any logs, screenshots, or files that are related to this issue:

https://imgur.com/a/xjfKVHK

Wibble199 commented 6 years ago

Have you got the correct layout selected in the Settings > Devices & Wrappers menu? image

Speedy-VonGofast commented 6 years ago

Of course it is, you can see it on the screenshot I posted. The problem is not Aurora's layout, it's the Razer Chroma games that send lighting like a QWERTY layout.

And by Razer Chroma games, I'm talking about Diablo 3, Quake Champions, A Hat In Time and other games that uses the Razer Chroma wrapper.

simon-wh commented 5 years ago

The issue is that Razer is sending the keys with the "Label" i.e. a,z,e,r,t and Aurora uses a system where all the keys are for their location rather than what it says on them. So when it receives "a,z,e,r,t" it lights up the positions for "a,z,e,r,t" in the standard layout rather than the ones labelled "a,z,e,r,t". Well, that's my initial observation at least

Speedy-VonGofast commented 4 years ago

I tried to fix my issue with the Key Color Cloning and I made another observation. The cloning keys are in QWERTY layout as well (choosing the A will affect the W key)

In the meantime I found a temporary fix by inverting the concerned keys with the Key Color Cloning. I still hope it's getting fixed someday...

image