KovaaK's News

A small update to address some things identified with the last release.

IMPORTANT: If you are experiencing crashes and have an AMD card, please visit the link below to get an optional driver update. There was a known issue that AMD recently fixed: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-2

Users of the Trainer may experience some minor glitches on Jan 24th at 11:30am PST / 8:30am PST for about half an hour, as we upload newer content. While we don't expect any issues with Trainer play, should any occur, the Sandbox and all Steam workshop scenarios will still be accessible and function normally.

The fixes:

• Reduced volume of opening video. 50% less ear bleed.
  
• Updated arrow speed for Tempest Bow to match recent OW change.
  
• Sandbox: Fixed issue with Fortnite Config mouse sensitivity.
  
• Sandbox: Vertical sensitivity can be separated from horizontal sensitivity again.
  
• Sandbox: Fixed hit registration issue with weapons such as Ascended Tracking series of scenarios.
  
• Sandbox: When players first spawn in a scenario, momentum is no longer halted after a split second
  
• Sandbox: Applied spawn sound concurrency to prevent excessively loud sounds in 1w9000t and similar scenarios.
  
• Trainer: made it easier to return to Sandbox from the trainer home screen and login/registration screens.
  
• Trainer: adjusted despawn timers so they always appear over the targets’ heads.
  
• Trainer: email validation flow fixed.
  
• Trainer: side quest messaging adjusted to inform you on what area you just improved.

Feel free to join our Discord server and let us know if you have any feedback!

Happy New Year! We’ve worked hard over the last month on a wide variety of technical issues that the community has helped us identify, and we are now excited to relaunch 2.0. All of the features that were listed in the 2.0 patch notes are once again available.

IMPORTANT: If you are experiencing crashes and have an AMD card, please update your drivers. There was a known issue that AMD recently fixed with an update: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-2

There is a lot of under the hood stuff going on that should result in better player experiences all around. Most notable from the first 2.0 release:

• On the first run, players who come from 1.x will automatically load into the Sandbox.
  
• First-time new players will be greeted by a selection screen to choose the Sandbox or Trainer.
  
• If a player quits from Sandbox, they will automatically boot into Sandbox next time. Same for Trainer.
  
• Sandbox: fix for bots jumping in air as they respawn.
  
• Sandbox: fix for bots getting stuck in place on respawn.
  
• Trainer: fix for Fortnite weapons being blocked from turning while ADSing.
  
• Settings updates to ensure better saving across Sandbox and Trainer.
  
• Trainer: Hide Weapon now works.
  
• Trainer: Level 5 removed. Wasn’t quite working as envisioned.
  
• Players should be able to progress past Level 4 now.
  
• Trainer: Moved a lot of logic from the cloud to the client to allow for speedier performance.
  
• Trainer: Removed actions widget (from left side of screen) for better performance and less eye noise.

We are getting back to developing cool new features (scenario playlists, anyone?), but if you come across any issues, please let us know—a great place to chat is our Discord.

Happy New Year! We’ve worked hard over the last month on a wide variety of technical issues that the community has helped us identify, and we are now excited to relaunch 2.0 in the form of a public beta. All of the features that were listed in the 2.0 patch notes are once again available. Help us out by giving it a shot and let us know how everything feels!

To join the beta:

1. Right click on the game in your Steam Library
   
2. Go to “Properties”
   
3. Click on the “Betas” tab
   
4. Click on the dropdown menu and select “beta - Public Beta Branch”

There is a lot of under the hood stuff going on that should result in better player experiences all around. Most notable from the first 2.0 release:

• On the first run, players who come from 1.x will automatically load into the Sandbox.
  
• First-time new players will be greeted by a selection screen to choose the Sandbox or Trainer.
  
• If a player quits from Sandbox, they will automatically boot into Sandbox next time. Same for Trainer.
  
• Sandbox: fix for bots jumping in air as they respawn.
  
• Sandbox: fix for bots getting stuck in place on respawn.
  
• Trainer: fix for Fortnite weapons being blocked from turning while ADSing.
  
• Settings updates to ensure better saving across Sandbox and Trainer.
  
• Trainer: Hide Weapon now works.
  
• Trainer: Level 5 removed. Wasn’t quite working as envisioned. Players should be able to progress past Level 4 now.
  
• Trainer: Moved a lot of logic from the cloud to the client to allow for speedier performance.

If everything performs as well as we are hoping, 2.0 will be relaunching for all users in the short term. We want to minimize the amount of time where both 1.0 and 2.0 builds are accessible, because new bot-AI behavior features have been introduced in 2.0 that mean some new scenarios will be overly simplified for 1.0 players.
If you come across any issues, please let us know—a great place to chat is our Discord.

Launching 2.0 on Wednesday was premature, and we apologize for the state that it was released in. We've heard all of your concerns, are taking them seriously, and we’re actively working hard to fix everything. Most specifically:

1. Until the Trainer is more polished, the Sandbox will be the first thing loaded for users. Eventually there will be a different front page that allows users to choose whether to jump into the Sandbox or Trainer, because the goal of the Trainer is to have it be the go-to/starting place for helping newcomers improve. The Sandbox is awesome, but 2500+ scenarios can be intimidating.
   
2. For the short term instead of registering new users with our services, we will go with Steam IDs. As many of you know, we will eventually be moving off of Steam for workshop content and leaderboards (migrating workshop scenarios, but wiping the leaderboards clean). There are limitations with Steam’s leaderboards that have proved to be a problem for long-term sustainability and improvement, so we do need external accounts—we’ll just make sure to have it as painless as possible for everyone and include features that make it very worth it.
   
3. Any other technical issues that we documented after 2.0’s initial launch, including setting revert bugs.

So, when/how is it coming back? We don’t have a set date in mind for when it’s coming back, but we plan on releasing it first as an open Public Beta within Steam. When that happens, we’ll post another announcement and let everyone know how to opt in and give it a spin. At that point, please give it a test and let us know if we’ve addressed your concerns.

Finally, we really appreciate that you care enough to provide feedback, in whatever form. We’re listening, and we’ll get this right.

Two quick QoL fixes:

• You can now adjust video settings in the Sandbox and they will work! However: they will reset when you go to trainer/exit out and come back. We are working on a larger settings saving patch, hopefully coming tomorrow.
  
• Fix for very dark/wrong color Sandbox maps
  

Please read the below, as well -- more fixes coming!

First, and most importantly, we apologize to all of you who have experienced bugs or struggled to use the Sandbox as efficiently as you used FPS Aim Trainer. We are attacking bugs and adjusting the experience in response to your feedback as quickly as we can. This release should alleviate some of the initial technical pain, and it should enable you to get where you want to be in the software much more quickly.

Second, please keep in mind that we are a small team, and the Flicking trainer is the first early release on a long roadmap; it is going to have bugs, and you may experience wonky gameplay and analytics, as we learn from your interactions with the trainers and work to improve the software. Meanwhile, the Sandbox is going to receive important new features, including Playlists, as quickly as the team can build them.

Finally, we hope this follow-up release clearly signals that we are listening to you. Everything in this release is the result of feedback we got from you, over the past 24 hours.

Thanks!
The Meta Team