Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Alternatively create profiles in the native Windows, and use them.
The DPI is also working in the internal memory, for each profile, you can save three DPI value.
It is necessary to set the value for the G-key DPI up / down
In Poiner Settings to create three values 'DPI Sensitivity Leves'
Linux means only the value of G-key can be changed via xinput
hLZ, how do you change DPI for internal memory settings? As soon as I switch the Windows software to internal memory, the pointer settings page cannot be accessed, and the DPI immediately switches back to default, and the DPI up/down buttons stop working.
Do you have a G600 that you have successfully changed the DPI on?
I've heard of locomo before, but I think it's much older than the G600. I searched for it anyway, but couldn't find it.
EDIT: Ah, I see on Logitech's support pages that the pointer settings page SHOULD work for the on-board internal memory mode, but it isn't for me. When I click the pointer settings icon I just get the home page. Anyone else experienced this?
Can't say if it still works for G600 though.
Some how-to in any case: https://wiki.archlinux.org/index.php/Lomoco
The problem exists for version 8.75.30 and 8.74.xx, but when I went back to version 8.58.183 it worked perfectly, and could then access the pointer settings page while in on-board memory mode.
For anyone reading this now, the latest version of LGS seems to have fixed this again (works for me with 8.81.15 on windows 10).