Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics

FPV Freerider

A member registered May 06, 2015 · View creator page →

Creator of

Recent community posts

(1 edit)

Anti aliasing is not possible to activate at the moment (even with command line options) but I am thinking of maybe adding an anti-aliasing option later on.

(1 edit)

The first thing I would try if I were you is to try both a default model file and a model file with the offset described in the Frsky setup document:

That way you should be able to figure out if the cause is the model setup itself.

If you are suspecting the problem might be an update of the Taranis drivers you can check this post for clues:

If it was working before and an automatic Windows update caused it to stop working I can suspect that it has something to do with your systems USB input/joystick drivers.

Hi, sometimes the automatic stick detection gets it wrong.
Keep an eye on the little circles as you go through the calibration.
You can manually click on the circle that you see is the correct one for each stick (instead of clicking "OK")
Hope that helps!

(1 edit)

Hello, thank you, glad you like it! Unfortunately I am sorry to have to tell you that it is not possible to load a custom level from the command line. So you will have to go into the level editor and load the custom levels from there as usual.

Thank you, I'm glad you like it! I'm not exactly sure what you mean since I'm not a Linux user myself. However, in short, I don't have direct control over the input - I can only see what comes through Unity's input manager (I use Unity for development). Therefore any device needs to be correctly recognized by the Unity input manager to work.

Thank you for the information. I use Unity's built in input manager, which, with the benefit of hindsight, probably wasn't the best idea (since I've learned that Unity's input system is, well, know not to be the best to put it that way). (Unity is the engine I use for development). If I had known this when I first started out developing the sim I would probably have looked into other alternatives. The way it is now, I can only read the values that come through the Unity input manager. Therefore it is not some thing I can change in my own code. I would need to change to a completely different input system. I am hesitant to do that now, since if I did it might fix the issue that you describe, but it might instead cause other unexpected issues to people who now has their setup working perfect.

What do you mean by "noticed that your calibration routine only looks at one value per axis"? (The row of little circles above the OK button when going though the calibrate controller procedure shows the values exactly as I see them in the input manager).

Make sure you have downloaded the version called "", which is marked latest version, that one should work.

I suggest deleting the entire simulator and unpacking the zip again, maybe to a different folder. Sometimes the folder name/location can make a difference.

Currently it is the same expo for roll, pitch and yaw. I prefer to keep it simple. If a lot of people request separate curves, maybe I will add that later. For now, those who wish to set separate curves for the different axis will need to do it in their transmitter.

Great, glad it's working now.

Great, glad it's working now.

In the latest update you can now adjust the expo/superexpo settings like you suggested.

Try again later, I'm sure it's just something temporary

Uploaded a new build today (built using the trusty old version of Unity).

You can try if this one works better on your machine.

You should still be able to use the same equipment. The input system of FPV Freerider is the same. 

Note that if you are using a FrSky 9X/Frsky Q X7 or similar you should be able to connect it directly via USB cable (no need for a dongle). There are lots of youtube videos that shows how that is done, a collection of links is at the very first post of this forum thread.

(2 edits)

Thank you, could you give some more info - what operating system are you running it on?

(I built the latest version of Freerider using the latest version of Unity. That might cause all sorts of unexpected problems. Might have to revert back to the old version of Unity that I haven been using for ages (deliberately, to avoid theses kind of issues) ).

(1 edit)

Very nice freestyle map, thanks for sharing! Best dive obstacles that I've seen so far in a Freerider community map. Also lots of good stuff for powerloops etc.

Hi, that sounds like an interesting project. There is no automatic way to retrieve information from the simulator itself. You can write me at for easier communication. 

(2 edits)

That's a good initiative!

It might be that the USB connection of the Tiny X8 can't be used directly as joystick (might be for USB update only).

Even if it would theoretically be possible to use it as a joystick my guess is it will not be a plug-and-play solution.

If I'm not mistaken the Tiny X8 is Frsky compatible. Then it might be possible to use it with a wireless Frsky receiver such as the Frsky XSR-sim USB dongle or similar. I haven't tried it myself though, so I can only recommend it if you are interested in going down the DIY hacking route.

(Might be easier to just get a Frsky Q X7.... )

Yes, it sounds like it could be the same issue as with the Taranis X9D. On the Taranis it is pretty simple to change the endpoints to work with Freerider but I guess there is no such possibility with your RTF transmitter.

What might work is to change the endpoints in the Betaflight CLI using the rxrange command. Not sure if it will help (or if it will be a practical solution even if it would help) but it could be worth a try. 

There is more info on how to adjust endpoints in Betaflight here (towards the end of the post) :

Yes many people are successfully using that transmitter with Freerider, so it should work. 

You can have a look at this video for an example on how to get it connected:

There are also many other videos that show how to do it.
(1 edit)

Yes that's a known issue, I haven't managed to find a fix for it without changing the very core of the input system (which I am reluctant to do since that might cause other issues), so you will have to work around it by only have your controller connected.

When you purchased the sim you got an email with a link to your personal download page, you can download the latest version from there.
In case you have lost that email you can request a new on the Itch support page that you linked to:
(Under "recover purchases")

Does it only happen at max throttle?

Check if the stick input behaves as expected by going to the Trim Settings screen (Click Calibrate Controller on the main menu and then choose "Go To Trim Settings")

(2 edits)

The settings for the demo drone is the 'Sluggish' preset setting on the custom settings screen (called Default in the earlier versions)

Edit: Actually it is the 'sluggish' preset but with lower yaw speed, 280 degrees/sec

How do you mean by a model for less space or content?

Great, glad to hear you got it working!

Thanks for sharing!

Yes it should work. I believe you need to have TAER channel order set up on your radio.  You can have a look at this video for instructions:

Hope that helps!

Yes, that is puzzling. One thing is for sure - FPV Freerider cannot change by itself or auto-update somehow. Since it worked before I guess it must be that there is something that has changed in your system, perhaps some driver update or something.

To make sure that there is not some missing or corrupted file you could first try to download the entire Freerider zip file from Itch again and unpack it.

(1 edit)

That's right. The existing expo curves are simply:

expo1: x^2 

expo2: x^3

expo3: x^4

Have you ever been able to run the custom levels?

Have you tried the level editor itself, does that seem to work?

Did it run fine several times, and then suddenly started crashing?

Are you still running it on Windows 7?

Maybe there is some problem with the memory.  You could try running it in a window (as described in the manual) and see if that makes a difference.

Thank you! Glad you like it. Well, yeah, it's been requested a few times...I will consider it. Thanks for the formula, that in itself should be fairly simple to implement.

What problem do you have exactly, does it have to do with low framerate or with the stick input itself? Please get back with more info and I might be able to help.

(3 edits)

Good point!

I forgot about that, I will add it to my earlier reply. You're right, if you want the Linux version you need to purchase the sim here on Itch.

(It's actually intentional - since the Linux version is somewhat experimental and I can't guarantee that it will work for sure I decided not to offer it on Steam. Those who still want it for their Linux machines can get it here. I recommend trying the free version first to see if it works on your particular setup).


There is no option for crosshair (yet). I might add it in a future update.

So, for now, probably the easiest way to get a crosshair is to put one on your screen by using a small piece of tape in the true DIY FPV spirit.

The android version is separate and only available on the Google Play Store. It needs to be purchased separately.

Fortunately it's pretty cheap.

(1 edit)

It doesn't make much difference really.

Both will get the same updates.

It is the exact same simulator, just two different marketplaces to purchase it.

Edit: Please note that the Linux version is only available here on Itch

(1 edit)

I agree it may not be very intuitive, have added some info in the custom levels download instructions (and in the user manual) so that it will hopefully be more clear.

It's one of the things I would like to add most of all, however it comes with it's own set of challenges to do well and for now I have put multiplayer on hold.

(2 edits)

Yes, I am aware that the HUD is not readable in stereoscopic mode. I will take a note of it and see if I can fix it in a coming version (It's not so easy since the menu system is completely different from the in-game camera, otherwise I would have done it like that right away). My recommendation the way it is now is to take the goggles off whenever you're navigation the menu.

Thank you, I'm glad to hear you like the sim and have found good use for it!

You use the Level Editor to load the custom levels.

On the main menu - click the Level Editor icon.
In the Level Editor view, go to "Level" on the top right menu. Click "Load"
The custom levels should show up in the list.
Select the level that you want and click "Play"
Hope that helps!