#Fortnite editing
1 messages · Page 1 of 1 (latest)
yeah thats called rapid trigger
as soon as u release the key (by default 0.15mm) it will stop editing
here's a few ways how you can fix your issue:
- up your rapid trigger distance
- turn off rapid trigger
That’s not how it works it’s more of a ghost tap/double activation which confirms the edit again as if the key has been pressed again, not because it’s been released
I have the issue as well and disabling rapid trigger didn’t change anything so it’s either an issue on Fortnite’s end, a firmware issue, or a production issue considering many people also have the exact same issue and others don’t even with 0.1mm actuation and rapid trigger highest sensitivity
I sent them a support ticket either way but should be a while before they reply
hmm
thats interesting
ill run you thru the beginner troubleshooting rq
replug keyboard (i assume you tried this before opening this community support)
Trust me I’ve done every troubleshoot possible and still no fix 😭
u tried restoring your keyboard?
which keyboard do u have
About a year ago
alright
October 2023 around
do you not have confirm edits on release turned on?
I tried with both and I get it
thats extremely odd.
Yh but with so many people having the exact same issue it seems weird
alot of ppl are experiencing this?
Ideally they put out a firmware patch or send replacements
Yh if u look on the Fortnite tag I’ve seen at least 5 others on this server
And in yt comments I’ve asked and some people also say they’ve had the exact same issue
But until support replies prob just have to wait and see
u said ur 60he made u slower in fortnite?
and how long have u been experiencing this issue?
Ik what he means by slower it’s like the ghost tap doesn’t happen if u purposefully slow down ur edits but any attempt at editing quickly makes it happen
@hasty granite do you guys have the same issue as this guy? https://www.reddit.com/r/FortniteCompetitive/comments/wcqi9u/everybody_turn_off_disable_preedit/
i have a feeling this is what you guys are experiencing
That seems to be addressing a different issue but I’ll try it out later and see if it works
But even then some people can edit perfectly fine with disable pre edit on so still weird
it is for sure a weird issue you guys are experiencing
dont really know what to think of it and how to analyze it either since i dont play fortnite and havent for quite a few years by now
Yes it made me slower from the day I got it last summer like 1 year and a few months ago
When I use my ducky mecha mini keyboard with mechanical switches it doesn’t happen
It’s really weird cus u don’t notice it while typing but u do while playing
I should deff turn of rapid trigger
Or something
yh this doesn't fix it
any fix yet?
any fix?
its not this
im having the same issues
i just bought this keyboard to. ive tried numerous setups, different actuation points, rapid trigger settings, etc. some would slightly fix the issue. but its never fully fixed.
ive even plugged in my old crappy keyboard, and tried them both immediatly after one another, and i just cant seem to fix this problem on the wooting. its like the wooting sometimes doesnt even register i clicked, in my case its letter F (my edit bind), or it double clicks.
ill try moving all of my binds to some other part of my keyboard and see if that fixes the issue
so i changed all my binds twice, so i tried editing with F, H, and ;, yet this problem occurs on each one.
I feel as if its a speed thing? If i try everything slowed down, it works perfectly fine. but the moment i try to do things like multiple triple edits, or even a single quad edit, its like it goes to fast it sometimes doesnt even register im clicking
(sorry for the yapping, im just trying to provide as much information as possible.
Have the same issue alr asked but they don’t answer to that problem
i think i might have found the exact issue
its the keyboard itself
if you press a key too hard, it wont activate
it will either click once but very quickly, then stop the input (even if you keep the key held downm)
or it wont click at all
do i lower the actuation point maybe?
it happens no matter what for me ngl
i tried both 0.15, 1, and 2.5
0.15 the double click issue happens, but anything larger than 1 doesnt double click. but they all no matter what sometimes will give 0 input
yea im trying to find a fix for a while now
i got it a month ago and havent found anything
i play faster and better on a $30 1k hz keyboard than a $200 "most competitive keyboard"
type shi
i cant lie tho, this keyboard is god tier for shit like valorant
but anything else, its useless
ive never played osu, but seeing these input issues, idk how its good for that
yea i have the ducky one 2 mini for fortnite and wooting for valo and cs
ive wanted a ducky, but ive also heard alot bad about it
i have this wooting, and a friggin Onn. keyboard
and the onn keyboard is so bad, its loud and clanky and has the worst keycaps on it
but yet its still better
i lowkey hope this input issue is just a software thing and can be fixed
jus get like an npc keyboard
cuz im not trynna unplug and plug in a new keyboard every time
maybe apex pro if u have the money
the Onn. keyboiard is a npc one
might just get the corsair k70
yea whatever does the job
sell this kb for that ong
if i only played fortnite i wouldve sold it by now fs
nah i dont only play fn, i have a bit more of a life than to devout myself to that game
i play Fn, valorant, BO3, BO6 and geometry dash
gd, not as much as i used to though
i quit after my kyouki comp
for real bro i dont mind this issue that much but when i think that i cant even double edit makes me mad
ONG, and i know its not a skill issue cuz im on 0 ping and it works perfectly fine on my other kb
im on 20 ping
and nonetheless, i can do a quad on my controller but not the wooting
office keyboard beating the wooting in a input battle rn is crazy work
its too fast for fortnite prolly
but heres the issue, theres some people on youtube ive watched play with a wooting and they dont have this issue
maybe its the keyboard we got sent idk
yorease and jerian
they showed off the wooting 60he
and they played with no issue whatsoever
lowkey i should too
you wont get any response but go for it
if theres numerous people saying the same issue it could help with response and a fix maybe
yea
ngl i have fortnite at one one the lowest acuation points and i can edit perfectly fine
do any of you play with edit on release?
I do
Can we get your profile code?
you probably just arent used to the speed of it
So we can see if that’s maybe the issue
yea ill send it rn u have a 60he?
Ye 60he+
I even changed actuation to my old keyboard at 2mm
And it still had that issue
529f8e5a00bfa782175f43dca72494be2662
my biggest problem was movement but i had corrected that
i dont have any problems with editing though
Also, which ones your edit bind?
Cuz if it’s not F and you have custom settings for that one key, I’ll just have to change it
i use f to edit
it does not help
@steep scarab did you find anything?
I did not, i guess the wooting forces you to play a bit slower.
I’ve been playing with it, and it’s kinda just something you have to get lucky with, whether it decides to make you struggle with fast editing or if you can actually do what you need without an input not being registered
Sometimes it doesn't edit in Fortnite and I have tried all the keys
It’s bad when you first start, but now that I’ve been playing with it for a good bit. You just gotta get used to it. But you will end up getting to a spot where you just can’t edit any faster. I don’t think I’m at that point yet, but it defiantly is something you just gotta get better at.
Made to remove the 8000Hz and I'm going faster
I think the 8000Hz is not well polished now I'm flying
I haven’t noticed cause I’m bad
lowkey miss when i was bad at fn
it was honestly more fun
how do you remove the 8000hz
Settings and you can put it on 1000Hz
Someone that is having this issue please record it happening while using woot-verlay for keystrokes pls:
https://github.com/DjCrqss/Woot-verlay
Will do
ive used it for somedays now and havent run into any problems
Ive used the apex pro before so im used to a low actuation and its such a benefit while editing in my experience.
Most of it is timing especially while using edit on release
I’ve had a ticket open with support for some time now trying to fix this problem and I’m pretty sure a lot of us just have defective boards
The reason double edits have been failing are either due to ghost presses causing the second edit to confirm before any tiles have been selected or some other unknown underlying issue with the game engine which seems to affect everyone’s max editing speed in general
Lowkey, I still have the issue. But it’s kind of something you learn to start getting past.
Mine does the same, I’ve changed some settings with the wooting.
And after discussing with staff they’ve said that that behaviour is definitely irregular, even though spikes due to key bounce when rapidly double pressing are expected, it shouldn’t be to this scale and any usual bounces are filtered out of the keyboards input
So something may well be wrong with the board itself either due to the switch/key tolerances or a more general hardware issue with the pcb
Edit Bind= I changed the rapid trigger actuation to be later (I think like 1mm), and when I start letting go it’s 0.15.
2nd key switched = Then I had to change my right alt or something (forgot which key as I moved the keys around, but it’s to the right of my space bar) to have the rapid trigger that is 0.15 and ignores everything and just immediately stops when you start to let go of the key
You can’t see the axis on the diagram but the spike due to the ghost actuation/key bounce is about 1.65 mm worth of travel down to 3.25 mm which would mean that even with your settings the issue would still be present
So the issue prob happens to a varying degree on different peoples keyboards it seems
Ik mine detects the entire input, just the game seems to think otherwise.
Wdym by that
Seems similar to the second issue we found
Which is that the second input was there on the analog monitor but doesn’t happen in game
But we put this down to a ‘max edit speed limitation’ of the game bc people on different keyboards have the same issue
Ye, it’s that.
The issue on the top with the analog monitor and the ghost press looks like the edit tiles of the second edit of the double edit turning blue very briefly before the edit is autoconfirmed before selecting any tiles
But the second issue u just talked about, the tiles don’t turn blue at all as if the game hasn’t registered the key press, even though it’s registered on the wootility monitor
And I tested this on 0 ping high fps etc. so it’s not likely due to any other limitation except for the keyboard or the game engine itself
And again like I think you said earlier the keyboard is perfect for other games like val
You’re explaining a lot easier to understand than I did… I’m jealous😭🙏
I mean I’ve been going back and forth with support for a while now so I basically know the issue inside out 😭
I have clips of gameplay overlayed with the live analog monitor to further illustrate but I cba to find them rn
Tried the debounce beta firmware?
issue was present on like 3 of the firmwares available at the time i tested with one of them being beta but idk if the debounce beta one was one of them sounds interesting if u could send
thanks i'll definitely give it a try but i think one of the main unique aspects of this general issue or at least in my case is that the bounces are so abnormally large any debounce filtering recognises it as an actual press no matter what
definitely feel some improvement haven't yet verified if it's perfect though
If it ends up helping it might be good to tag mat1jaczyyy so the team knows about it and can use the work in coming stable firmware builds
yh it's been harder to verify though because before chapter 6 all multi edit fails were due to the 1st issue i mentioned (tiles turn blue briefly and ghost actuation confirms edit before any tiles are selected) but more recently most of the fails have been due to the issues other people have with there being a registered input on the monitor, but nothing happening in-game
so it's been harder to test anything in relation to the older issue bc it's 'overshadowed' by the newer one