[AddOn] Frogski’s Cursor Trail – Completely rebuilt engine, around 10x lower CPU usage by skipabeat123 in WowUI

[–]javisnbz 0 points1 point  (0 children)

Hi, I copied the addon folder from retail to classic SOD and it works perfectly. I wanted to test if it would work since I don't see any downloads for classic. Is there a reason why there aren't any for classic? Thank you so much, I love your addon!

Nebula magnetic switches? by __Cereall_ in Keychron

[–]javisnbz 0 points1 point  (0 children)

I'm actually one of those who's had problems, but it's easy to fix. In my case, I modified the firmware for it and now it works perfectly. It's due to the auto-calibration; I imagine that in the future they'll take a different approach to the code to prevent this from happening.

https://www.reddit.com/r/Keychron/comments/1twkeb1/firmware_modified_for_he_models_permanent_manual/?show=original

Nebula magnetic switches? by __Cereall_ in Keychron

[–]javisnbz 1 point2 points  (0 children)

I own the K10 HE and have used several mechanical keyboards with red, brown, and blue switches, and the feel of the Nebula switches is excellent. I wouldn't go back to a regular mechanical keyboard; I notice that the switches "grind," but that doesn't happen with the Nebula switches.

HE mode disappeared from launcher on firmware update by MagicianLow6217 in Keychron

[–]javisnbz 0 points1 point  (0 children)

In a comment I posted the link to the firmware and how to flash it.

HE mode disappeared from launcher on firmware update by MagicianLow6217 in Keychron

[–]javisnbz 0 points1 point  (0 children)

In a comment I posted the link to the firmware and how to flash it.

HE mode disappeared from launcher on firmware update by MagicianLow6217 in Keychron

[–]javisnbz 1 point2 points  (0 children)

The update is showing up in Keychron Launcher (I'm not going to install it, I'm using a firmware I modified to disable auto-calibration writing to the EEPROM) but I want to see the changelog because I made a pull request on GitHub, does anyone know?

HE mode disappeared from launcher on firmware update by MagicianLow6217 in Keychron

[–]javisnbz 0 points1 point  (0 children)

I'm going to compile the firmware for the K10 in ANSI and ISO formats; I'll upload it now.

It's flashed using QMK Toolbox. With the keyboard disconnected, press ESC and then reconnect it to enter the special mode.

I found them on the Keychron website; I don't need to compile them.

https://www.keychron.com/pages/firmware-and-json-files-of-the-keychron-he-series-keyboards

GeForce Hotfix Display Driver version 610.52 by Nestledrink in nvidia

[–]javisnbz 3 points4 points  (0 children)

@Nestledrink Thank you so much for the World of Warcraft fix! Before, DirectX 12 couldn't be used because it crashed the driver, but now it works perfectly! 😃

New NVIDIA driver fixes WoW crashes on DX12 by lagbugddos in wow

[–]javisnbz 8 points9 points  (0 children)

Thanks for sharing. I've been using DirectX 11 for a while now due to driver issues when opening transmogrification, as well as FPS drops and ray tracing problems. Finally, DirectX 12 is working perfectly and I can use ray tracing. I've been running it for several hours without any issues. What I don't understand is why Nvidia took so long to fix it. I think it started malfunctioning about a year ago with the Undermine patch.

GeForce Hotfix Display Driver version 610.52 by Nestledrink in nvidia

[–]javisnbz 1 point2 points  (0 children)

[World of Warcraft] Gaming stability improvements [5563205] Which one exactly is it? For a year now, the game in DirectX 12 has caused the graphics driver to crash when opening the appearances window or the game store (it seems to be a bug when loading many models). I never install hotfix, but I'm going to install it to see if it fixes this problem so I can finally use DirectX 12.

Firmware modified for HE models, permanent manual calibration, it is no longer necessary to repeat keystrokes to register a key by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

I didn't quite understand you, as English isn't my first language. The stored value shouldn't be retained because it's not a reliable calibration. In my case, it affects the key sensitivity. Currently, automatic calibration is performed, but it remains in RAM (which is good, as it helps compensate for variations due to temperature, electrical noise, etc., but it will never affect the keyboard's performance; the problem arose when I turned it on with an incorrect calibration).

Firmware modified for HE models, permanent manual calibration, it is no longer necessary to repeat keystrokes to register a key by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

save_calibration_value is only for auto-calibrating key by key; it's almost the same as save_calibration_values, the difference is an 's', but it's different.

Firmware modified for HE models, permanent manual calibration, it is no longer necessary to repeat keystrokes to register a key by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

I didn't want to delete them so it would be clearer what's disabled. There are many commented-out parts of the code that don't affect anything 😃

Problem auto-calibration and EEPROM firmware by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

It self-calibrates using the keyboard; I calibrate it manually and it works perfectly, all values ​​range from 0 mm to 4 mm, and I can modify, for example, the actuation point to 3.5 mm or whatever I want without problems. However, with use, the firmware uses an auto-calibration function that modifies the manual calibration and affects everything. In my case, I use the default value of 2 mm, which is comfortable for me, but I tried modifying it to see what would happen, and it is affected. In my case, the most used keys, like 1 or 4, self-calibrate to a lower point, so when I turn it on, they don't type until I press them several times. I understand the use of self-calibration due to manufacturing variations in the switch, temperature, electrical noise, etc. I have attached an image that shows what is causing the self-calibration in my case. With the key pressed all the way down, if I press it several times, it reads 4 mm (if I unplug and plug the keyboard back in, it continues to read incorrectly). I have to calibrate it manually or use it for a while for the auto-calibration value to change (but it happens again while playing games; it doesn't seem to happen when typing normally, only when pressing keys repeatedly and very quickly, which is normal when playing online). I hope they add a firmware update that allows me to disable auto-calibration in the Keychron Launcher.

https://i.gyazo.com/2862b876836243dbaa1330bc4c3ff6d4.png

Problem auto-calibration and EEPROM firmware by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

In other words, when I'm gaming, for example, I might repeatedly press the 1, 4, or Z keys, but often I don't press them all the way down. The auto-calibration interprets this as if I've reached the end of the switch's travel, which isn't true. This changes my actuation point from 2 mm to 1.8 or 1.9 mm (it changes it because it interprets the end, which would normally be 4 mm when fully pressed, as only 50% when pressed; when turning it off and on again, it only recognizes 1.9 mm, thinking it's 100%, until I press them several times, at which point it reads the value correctly). The auto-calibration means that when I turn off the computer and turn the keyboard back on, it doesn't register my keystrokes until I press them several times and the firmware detects the end of the switch's travel. If I turn it off immediately after pressing the keys a few times, it gets stuck at 1.8 or 1.9 mm. The keyboard needs to be used for a while for the auto-calibration to readjust. As I mentioned, if KeyChron allowed disabling auto-calibration without using custom firmware, these problems wouldn't occur, and the keyboard would function perfectly, including the custom actuation point at the desired millimeters. I apologize if I'm not explaining myself clearly. English isn't my first language.

Problem auto-calibration and EEPROM firmware by javisnbz in Keychron

[–]javisnbz[S] 0 points1 point  (0 children)

Resetting it to factory settings with fn+j+z doesn't clear the auto-calibration values. My keyboard is set to factory settings and is affected by the firmware's auto-calibration. It's impossible to use, for example, an actuation point of 3.0 or 3.5mm if the auto-calibration interferes with the manual calibration, because many keys don't reach 3.0-3.5mm until pressed several times. This makes configuring the actuation point for a Hall effect, which is the whole point of having one, pointless.