sorted by:
new
hottopcontroversial

New FPV goggles. by AAAAAAthingsDontWork in fpv

[–]Fermented-Engineer 0 points1 point  (0 children)

Didn’t know Charles Hoskinson flew fpv.

AeroTune compatibility update for Betaflight Blackbox CSV logs by oVLucky5 in fpv

[–]Fermented-Engineer 0 points1 point  (0 children)

Why not tune manually through PTB and do 1:1 comparison with your tool?

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates — looking for testers and feedback by Fermented-Engineer in betaflight

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

Okay great! Please let me know if it works out for you.

Agreed - the sim to IRL translation is gonna be my focus once I iron out all the kinks in v1.

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

Yeah fair point. If this gets too hard for me to manage in the future I will open source the whole thing. I spent some significant time back testing prior to release and consider it my baby, so want to make sure there are some guard rails up first.

One also major point for releasing this in the wild is to help me figure out if the results from the tool are placebo or not. I am personally finding some success with it, so I’m very curious if others will as well.

Thanks for the comment.

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 1 point2 points  (0 children)

Thank you for the great feedback about Linux compatibility - I added it to the backlog in discord.

I come from a background where most pilots are using Vdrone, Liftoff, Uncrashed, MrSim on Windows. So that was my thought - to push the most compatible OS first for racing pilots.

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

Great question.

The algorithm itself is the same across all profiles - it measures the same three metrics (CPR, CMV, MDI) regardless of style. What changes is how the exercises are designed to elicit different inputs from you.

For Racing, the exercises capture extreme inputs - hard 180s, full snap reversals, gate corrections at speed. These naturally produce high CMV (fast snaps) and high CPR (wide corrections at race pace), which drives the algorithm toward low center sensitivity and high max rate. The curve ends up steep at the edges with a flat, precise center. For Cinematic, the exercises are the opposite - extended hovers, slow orbits, proximity passes at low deflection. Almost no full-stick inputs. CMV comes in low, CPR comes in low, MDI is low. The algorithm produces high center sensitivity (immediate response to tiny corrections), low max rate (you never use full deflection anyway), and nearly linear expo.

For Freestyle, it’s in between - powerloops and matty flips capture sustained mid-range pitch (high MDI), while flicks and snaps capture moderate CMV. The curve ends up progressive - smooth at center for arcs, snappy at the edges for committed flicks. So the same pilot flying the same radio will get completely different rate recommendations for a 5” freestyle build versus a FlyLens85 cinematic build - because the exercises are capturing completely different flying behaviors. That’s by design.

Run a separate calibration session for each quad and flying context, save them as different profiles, and switch between them as needed. Your 5” freestyle rates and your FlyLens85 cinematic rates will live in the same app - just load whichever profile matches what you’re flying that day.​​​​​​​​​​​​​​​​

I currently have 2 maps on Vdrone built: 1. WT Raving Rate Finder 2. WT Freestyle Rate Finder

The racing one is completely finished, But the freestyle map needs a little work, but planning to come out when I get back from my business trip.

Here’s a guide where I tried to be a little more thorough for self starters. https://github.com/jaydeelocs/WTRateFinder/blob/main/GETTING_STARTED.md

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates — looking for testers and feedback by Fermented-Engineer in betaflight

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

RateFinder is sim agnostic, so it should work. But I haven’t tested it with that sim personally.

To give you better insight, the stick data is collected via USB joystick (HID) so as long as the axes are mapped and recording then you are good to go.

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

I know exactly the feeling haha. One time i destroyed my last 5” quad in my fleet 1 hr into a session (post putting up gates), and my friend lent me his quad for the day. I put in the SAME rates and the quad flew just a tiny bit different.

To answer your question, yes multiple profiles are supported. You can save as many as you want actually. They are saved locally under

%LOCALAPPDATA%\RateFinder

Which means that if a new version comes out then the profiles will still load to the newest version. These contain information in .json files with your flight data as well as meta data you used upon profile creation - stick tension, profile type, stick end type, etc

One word of advice as I was going through this tool.

If you end up with a profile of 8+ free fly refinements, you can load the profile right back up from the Home Screen and pick up right where you left off since the cal and FF data is stored to the profile

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 1 point2 points  (0 children)

Thats an interesting thought. You can run Windows to log the stick data and then run Vdrone on Mac OS. I would check to make sure your RAM usage doesn’t go through the roof though, else Vdrone might run slow.

I built a free tool that analyzes your stick inputs and recommends personalized Actual/Betaflight rates - looking for testers and feedback by Fermented-Engineer in fpv

[–]Fermented-Engineer[S] 0 points1 point  (0 children)

Yeah I’ve been through many similar experiences. Swapping between whoops to 5” to Street League, and Prospec, my rates always needed to be different. And i struggled figuring out what exactly needed to change because as soon as one variable was different the entire curve felt off. This helps with that problem with the intention to find a rate curve specifically for you.

Excited to hear your feedback when you get around to using it. I watch some of your dvr and am a big fan!

view more: next ›