Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
https://chromasdk.io:54236/razer/chromasdk
https://support.razer.com/
If they are not responsive, please do let me know.
https://pastebin.com/NKA70fui
Started getting error ChromaInt failed: 1062. Can't find anything on this error
1. Turn off Wallpaper Engine completely (!!!).
2. Uninstall your complete Razer software suite (Razer Synapse and all of that).
3. Download the latest version of Razer Synapse 3 and install it from scratch.
4. Restart your system and try again.
Just for future reference, code 1062 means "service not active" according to Razer: https://assets.razerzone.com/dev_portal/REST/html/_rz_errors_8h.html
This is an error from Razer so we can only guess. But it sounds like your Synapse installation is faulty. So if you reinstall it like Tim explained (and also install the Chroma module) then hopefully that fixes it.
I was having issues, found this thread, and these steps worked for me. Thank you.
Except after this very Chroma update (yesterday), this issue should hopefully finally be solved, we will have to wait and see what happens next time. It will only be solved for people who are using this latest version, however, since Chroma must have received this fix of course.
It will use the version you had running while activating the automatic start, so that's how you can switch it.
I just wanted to say I also ran into this problem and after looking through it for about an hour I found that having a dual monitor set up could possibly be a problem with this because I figured out that my razor devices were actually trying to connect to my second monitor which had a background which wasn't LED enabled so after I switched the second monitor to something different which had the enable LED option it started working perfectly also so far I haven't really found a way to switch it to my main monitor but I'm working with what I have so its fine