#APEX setting for 240hz?
1 messages · Page 1 of 1 (latest)
Profile code: 5da6da8ac7e578f5ac3f3bcd70a7fe62e723
Planning to make a indepth guide to proper FPS game keyboard configurations with rapid trigger
Aiming at games like Apex/Valorant/CS:GO
Also some tips on people that are yet to adjust to analog gaming keyboards, or alternative configurations if they are too attuned with their previous digital keyboards and how they can get that 'feeling' back
@visual canyon if you want, I wrote on this topic in the Valorant channel #1047723220662485044 message
the whole discussion there may be relevant to you as well if you want to read through it
Any reason to use continuous rapid trigger in that profile when you advised against it in the valorant thread?
I recommend continues mode if you have a deep actuation point (as the apex profile has on a few keys (spacebar,C,Q)
On deep actuations where it is far deeper than the rapid trigger sensitivity I'd argue it can be more beneficial as you will still get rapid trigger properties on the full keystroke after you initially pressed the key
fast release + can still jitter at any part of the keystroke instead of only beyond 1.0mm
and if you only use >1.0mm on a few keys, you can keep the same feeling/behaviour across all your keys
It should also have no negative and no positive effects to have it enabled on very sensitive actuation points such as 0.1mm~0.4mm. So if all your keys are at that actuation point, just disable the setting.
If your actuation point is between roughly 0.4mm~8.0mm (depending on your rapid trigger sensitivity) I'd say continuous has no positive effect and may make the inputs feel more random as the behaviour is less consistent with your actuation point
The apex profile uses a mix of 0.2mm and >1.0mm actuation points, so it is fine within my theories & testing to have it enabled
tldr:
if you have/prefer an actuation point roughly around 0.4mm~8.0mm on your important keys, disable the setting entirely
Thanks for the thorough explanation. I also use 1.0+ activation point on certain keys. So I will keep it on. 👍
I hope that an alternative configuration with a guide and digital feel will come out soon. To express analog, it feels like adjusting the aiming sensitivity with the keyboard rather than the mouse.
The long answer can likely be theorised on from that discussion in the Valorant channel (link)
Short answer is you have muscle memory/rerouting/whatever you want to call it that isn't ideal for analog/depth-sensitive switches yet
Either adjust the keyboard settings to behave slightly more closely to your old keyboard or take your time to relearn the keyboard
Learning it can take slightly more than 11 days from my experience, but I've had friends who had no problems at all and were flawless within a few days of even hours..
So there are likely two kinds of groups there (or a spectrum with more data)
Best thing about the Wooting keyboard is that you can configure it to your settings and sensitivity. But what those are will likely be a quest that I can only give tips on
yes. This may be because I am not accustomed to fast keystrokes. Unfortunately, it's been two months since I've been using the keyboard, not days.
Although I have already adapted to 0.3mm, I have adapted to the sensitivity to movement, but I do not seem to be able to adapt to the same aiming sensitivity as before, so I am returning to the previous keyboard.
One thing I want to ask is, in the case of a general hot swap switch, if pre travel 1.2mm, total travel 3.4mm
Set actuation point 3.4mm in wootility, input individual key 1.2mm trigger, set actuation point about 0.4mm for pre travel
Are they similar? I'm wondering if I'm getting this right. If I'm understanding it properly, I think it's right to shorten it from here.
"..One thing I want to ask is, in the case of a general hot swap switch, if pre travel 1.2mm, total travel 3.4mm.."
If you were using a switch with 1.2mm actuation and 3.4mm pre-travel (which sounds like silvers), you should set the actuation point to 1.2mm
And in theory you can indeed set the rapid trigger sensitivity to 2.2mm upstroke (something very small like 0.3mm down-stroke) to replicate the same amount of upwards travel to the reset point on the silver switches, with continuous mode disabled.
test profile code:
f87e0cea079629caad14f37b4ee617fc092c
If you have any, you could also install o-rings into the keycaps to physically block out key-travel range so it is the same travel as a silver switch, and then disable rapid trigger to entirely copy the properties of your previous keyboard
^^
This is however something I would not advice as an ideal profile for rapid trigger
I would still recommend it if it is your settings that works for you. You do not need Rapid Trigger to play apex. The keyboard's "true 1000hz" scanning rate <1ms debounce is already a huge upgrade to alternative switches
In my experience, Rapid Trigger gives a ton of speed benefits for Apex specifically, I would seek the most you can get out of the technology
Instead I'd balance your deeper actuation point with rapid trigger in continuous mode, and possibly reduce the default sensitivity of rapid trigger to something more in your style
test profile code:
a29dd075067a1a5191b2d50455d93887ab67
I couldn't copy the test profile code, but I understood👍🏽
I must have been on the dev version of wootility, my bad
Here they are up to date:
1: 475df58d9725306d904d19a5388bb7d8fcef
2: 84dc8606ffd812593a60d25b2e8a61488576
It is similar to the existing feeling and profile silver.
Can you test one thing? The profile I've been using for two months is somewhat adapted to me, but if the trigger and tachyon mode are turned on. If you input individual key values to unused keys such as L-WIN or ESC, the feeling changes when you increase or decrease the key input value, unlike when tachyon mode is turned off. If the movement is correct, the aim is not correct, and if the aim is correct, the rotation movement is different. Adding or removing triggers also changes the feel. There is no such feeling when tachyon mode is turned off.
Please see the feeling while increasing or decreasing the value of L-win 3.7. Or release some keys in the trigger or see an extra feel.
edc121a71c0905965029616050efd0b39ec5
In tachyon mode, the phenomenon seems to be a RAM over problem. After lowering the memory clock for the stabilization test and testing the stability again, there seems to be no problem when turning on the tachyon.😂
That'd be very odd. If you want to look further into this, can you create a support ticket in #1019755933959733258 ?
You can reference this conversation by typing #1090980693921767465
The symptom reappeared, so I checked a few things, but it seems that there is a bug on the app software side. I proceed with initialization + recovery and continue to operate keys only on the Wootility Web, but there are no symptoms.