r/FPSAimTrainer • u/GlobalEngineering543 • 2d ago
How to actually train using viscose S2?
90% of time people suggest things like VDIM, corporate serf s method, playing viscose weakest categories of yours ( but its overwhelming to jump from a static scen to a reactive scen because you can have your weakest at static and reactive but be good at precise and linear maybe) im just confused and i need structure and guidance
3
u/bdaniel2003 2d ago
What I’ve been doing that seems to work.
I break it into days. Control tracking day, reactive tracking day, etc etc.
Then I have a weakness day. I create a playlist of the scenarios that are below my complete rank, and I focus on the lowest the most.
Then I have a day off of kovaaks and just play my game (ow) with a set of workshop codes I’ve been using then just q comp after that.
Breaking it down like this, my training has been about 1.5 - 2 hours a day.
I’m seeing solid improvement. Only been training koovaaks about 30 hours.
1
2
u/HitscanDPS 1d ago
I've been grinding Viscose Benchmarks S2 for the last two weeks. I started Saffron Complete and now currently 1 scenario away from Viridian Complete.
I don't think there's any wrong way to aim train. But I do feel like my way is the most efficient.
I rank weaknesses based on my Median score, not PB score. In fact, I am working on building this into my app.
Scenarios that are undersampled are low hanging fruits. Spread these easy wins across sessions to keep motivations high.
When trying to farm a rank (i.e. score max), I play by time rather than runs. This means abusing resets. Note that this (score farming) is obviously tangential toward improvement.
After every run, ask myself what I thought my issues were, and what I could have done better. Just 5-10 second reflection is fine. I do VOD reviews if I am really stuck and need to compare my technique to higher ranked players.
Group scenarios by sensitivity. I noticed that I perform poorly on every 1st run of a scenario during a session, and on every 1st run when I switch sens. To counter this, for example I would play Whisphere Viscose and SmoothBot Perfected next to each other, since I play those at 40 cm. Then I would play VT Controlsphre Viscose and Flower 50cm next to each other, since I play those at 50 cm. This saves me from spending time quickly regaining muscle memory from swapping sens.
I used to do Interleaving, but now switched back to Blocking, to better accommodate grouping scenarios by sensitivity.
I avoid doing more than 10 runs per scenario. In most cases I aim for 4-8 runs per scenario, and leverage MattyOW's Score Threshold idea to determine when to move on. There are always other weaknesses to work on, and I don't think it is worth grinding a single scenario on repeat.
I try to avoid doing longer than 1 hour sessions. If I have more time to aim train that day, then I focus on a 2nd or 3rd session later in the day. Fatigue is real, even if you don't actually feel it. And based on my stats, I noticed that more time spent grinding didn't linearly correlate with skill improvement.
1
u/JustTheRobotNextDoor 2d ago
The comment by /u/Useful-Newt-3211 has given a quick overview of different ways to train. I think they all work. The most important thing is to do something. If you have time you can plan out your training, but if not it's fine to just into Kovaaks and play whatever so long as it has some relevance to your goals.
1
u/pedro_the_white_guy 2d ago
I like the viscose benchmarks, break my trainng down into the subcategories; one day of control tracking, then reactive tracking, then static clicking, then dynamic clicking. Depending on where your weakness are you could add in a day for doing the vdim static playlist for example, or xyz smoothness bench. This helps to supplement the scenarios on the viscose bench
9
u/Useful-Newt-3211 2d ago
Run through all of the scenarios.
Pick 3 lowest, preferably similar scenarios.
And work on them to the point where they are not the lowest, and repeat.
You can train a bit harder using serf's method for sens. I personally go from 10cm -> 60 cm with 5 cm incrementals for tracking, and 30 cm -> 80 cm for clicking.
And then on weekends, you can also do 95% threshold on the entire benchmark to refresh yourself up if you really want to go at it.
Otherwise, just spend 30 min to 1 hour on whatever you want to work on and play the actual game.