diff --git a/src/app.scss b/src/app.scss index 65547e7..2017e78 100644 --- a/src/app.scss +++ b/src/app.scss @@ -94,7 +94,7 @@ $divider-margin-size: 0px; left: 0; right: 0; bottom: 0; - background-color: #ccc; + background-color: $grey-darker; border-radius: 34px; transition: 0.4s; diff --git a/src/lib/components/Faq.svelte b/src/lib/components/Faq.svelte index baa2305..d9115d8 100644 --- a/src/lib/components/Faq.svelte +++ b/src/lib/components/Faq.svelte @@ -6,15 +6,16 @@ } -
FAQ
++ + FAQ + +
- By using this web based Superglide trainer you trade accuracy for convenience, compared to the Powershell script. + By using this web based Superglide trainer you trade accuracy for convenience, compared to the + Powershell script. +
On the web we can only pull your inputs at a certain frequency. This introduces uncertainty. We are currently working on displaying this
@@ -42,8 +48,9 @@
But this means this web based Superglide Trainer still fulfills its purpose.
It helps beginners and intermediates get used to the order of inputs, resolve hardware problems and track their rough progress.
But if your overall superglide consistency starts to regularly stay above 70% and you want to make sure that your progress towards 90 and 100%
- is as accurate as possible, you could start using the Powershell script linked at the bottom. It's not limited by browser limitations and doesn't
- suffer from the same uncertainty problem.
+ is as accurate as possible, you could start using the
+ Powershell script . It's not limited by
+ browser limitations and doesn't suffer from the same uncertainty problem.
Keyboard issues: @@ -159,8 +166,10 @@
In general, yes. At 60 FPS you have to time the two inputs 16ms apart at 300 FPS it's just 3ms. So your input window definitely gets shorter at higher fps. We had a short moment where we suspected that Superglides might not need a 1 Frame gap. But after some extensive - testing we are now very certain that it's always 1 frame. However there are also scenarios where Supergliding becomes easier with higher - FPS. + testing we are now very certain that it's always 1 frame. However there are also scenarios where Supergliding becomes easier with higher FPS.
diff --git a/src/lib/components/Tips.svelte b/src/lib/components/Tips.svelte index 40b83e7..09245f4 100644 --- a/src/lib/components/Tips.svelte +++ b/src/lib/components/Tips.svelte @@ -5,15 +5,16 @@ } -Helpful tips to get better
++ + Helpful tips to get better + +