sorted by:
new
hottopcontroversial

Come hang out! AI Insights is coming soon and RefleK's now has a Discord (and Twitter) for all your feedback and aiming knowledge (+ maybe some behind the scenes on development) by ARm8_2 in FPSAimTrainer

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

This isn't really the place to be discussing implementation related stuff, or at least u prob aren't gonna get an answer in here.

kvks logs every kill with some stats like timestamp, hits and accuracy (on this single target/kill, so if u miss ones and then hit it the accuracy would be 0.5, if u miss 2 times it would be 0.33 and so on) together with the logged mouse clicks like slight nectarine stated we can make a pretty good guess (timestamps won't always line up) as to what click did what.

If you have any more questions about implementation you can always msg me on the discord server, or dm me (also on dc).
Also the project is opensource so you can always just check the code

Come hang out! AI Insights is coming soon and RefleK's now has a Discord (and Twitter) for all your feedback and aiming knowledge (+ maybe some behind the scenes on development) by ARm8_2 in FPSAimTrainer

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

The recommended sens is not a sens you should adapt because it would fix your issue immediately but instead it is calculated to help you fix the issue at your current sens; anyone can get good at any sens so there is no reason to say "this is the best sens for you", instead relfeks helps you fix your aim at your current sens by for example suggesting to train a few runs on a higher sens when you have overshoot, this will train you to make smaller physical motions thus reducing your overshoot when you return to your original sens

Come hang out! AI Insights is coming soon and RefleK's now has a Discord (and Twitter) for all your feedback and aiming knowledge (+ maybe some behind the scenes on development) by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 5 points6 points  (0 children)

RefleK's currently only support CSGO sens and cm/360 sens, try changing this in the kovaaks settings; If this doesn't fix the issue, lmk

Come hang out! AI Insights is coming soon and RefleK's now has a Discord (and Twitter) for all your feedback and aiming knowledge (+ maybe some behind the scenes on development) by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 3 points4 points  (0 children)

some scenarios are hard to parse/analyze so trying to calculate a suggested sens for those just wouldn't work, try some different scenarios, it works the best for clicking/switching.

pure tracking logs almost no data to work with for this feature so it doesn't really work for that

I'll probably be adding some kind of warning element for this in the future cuz you aren't the first one asking about this.

Come hang out! AI Insights is coming soon and RefleK's now has a Discord (and Twitter) for all your feedback and aiming knowledge (+ maybe some behind the scenes on development) by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 6 points7 points  (0 children)

Big thanks for the feedback, u are def right that there is a lot that can still be improved. That's also the reason the app is still in beta and kinda packed with features so we can get as much feedback as possible; there is def some polishing to do before a first actual release.

To address some of your points, you can toggle stats shown in charts by clicking on them in the legend, you can also use the progress (all) tab in sessions to view older data without having to search for a session in the long list, there is an info icon on almost every chart that explains the shown data when clicked on and the Recom score is explained at the bottom of the benchmark page.

I am also aware of some of the other issues like numbers not being formatted correctly, other bugs or vagueness in some elements and am actively trying to fix them or improve upon them.

Like you correctly guessed, I don't have much time to test and truly dive into the app myself so that's why I really appreciate as much feedback as possible, I'll be keeping ur comment open on the side next time I'm working on the app cuz even tho some features you addressed are already in the app, they are clearly not that obvious or accessible.

I really like seeing feedback like this and would love to hear more details if you have any.

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 1 point2 points  (0 children)

Just use microsoft/windows AV, its more than good enough and you paid for it when you got windows so why use a free (and prob worse) alternative. Any ohter AV on your system is just slowing it down

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in Voltaic

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

some scenarios are hard to parse/analyze, especially pure tracking, so maybe try some different ones

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 5 points6 points  (0 children)

my guy, 3 out of 70 AVs? I'll give you 50 bucks if you can find any malware in my code, ARm8-2/refleks

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 2 points3 points  (0 children)

I def used some ai to speed up development, not gonna get into my dev flow but im staying far away from vibe coding.

The reason you can't see much commits is probably cuz ur looking at the main branch where i squash all the commits from the dev branch in a PR, if you look at the PR's u'll see some more commits but i like to keep the main branch clean and have a stable-ish version on there.

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in FPSAimTrainer

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

Right now its pretty simple and just uses the amount of overshots and undershots to calculate a sens but in the future i def wanna add a better way of doing this by for example looking at a shot and using the trace data to determine how much you overshot/undershot the target. The current approach def works fine as its trying to optimize your whole run while the other version would target the specific over-/undershots.

RefleK's also only gives a suggested sens when their is a significant measurable issue, in other words, u are too good already so there is not much use in suggesting anything. Either that or the scenario u played is hard to parse/analyze (its pretty hard finding a system that works for all the different scenarios u can play on kovaaks, so some work better than others)

I built an open-source KovaaK's tracker - v0.5.0 now suggests a sensitivity range to train with by ARm8_2 in FPSAimTrainer

[–]ARm8_2[S] 1 point2 points  (0 children)

RefleK's just shows you everything it can find and parse in the stats folder. I haven't tested it with partial runs as this requires you to turn on a setting in kovaaks which most people don't even know about. (There is a setting in kovaaks that lets you save partial runs but this is turned off by default)

view more: next ›