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.
Recent community posts
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.
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) ).
Hi, that sounds like an interesting project. There is no automatic way to retrieve information from the simulator itself. You can write me at email@example.com for easier communication.
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) : https://oscarliang.com/adjust-tx-channel-mid-end-point/
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.
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.
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")
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?
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.
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.
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.
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
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.
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!
I you press Alt+Enter on Windows, it changes to windowed mode. Once in windowed mode, you can drag it onto the correct monitor, and then press Alt+Enter again to go back to fullscreen mode.
If you wish you can also adjust the resolution to fit your goggles.
You change the resolution by adding command line parameters to the exe file as described in the manual. For example:
-screen-fullscreen 0 -screen-width 800 -screen-height 400
(That will run the simulator in a 800x400 window)
To be able to select different displays you might also be able to use the -adapter command line argument. Have a look at the Unity Standalone Player command line arguments here:
(Under "Unity Standalone Player command line arguments")
Here is a tutorial how to add command line parameters on Windows:
(They explain how to do in on shortcuts - you can create a shortcut of Freerider by right-clicking the FPVFreerider.exe file and choose "Create Shortcut")
Here is a tutorial on how to update your drivers, for example your graphics card drivers:
First, try restarting your computer.
Make sure your graphics card drivers updated to the latest version.
Try running the simulator in a window by adding command line parameters to the .EXE file as described in the manual.
-screen-fullscreen 0 -screen-width 640 -screen-height 360
If it still doesn't work, try downloading the entire .ZIP file again and unpack it. Try unpacking it to another location (Such as in a new folder in "My Documents" for example).
Thank you for sharing! Very creative use of the objects. It's quite a detailed level you've built (in fact so much that my computer is struggling to play it).
Please note that the name of the .txt file needs to be the same as the folder name in order for Freerider to find it.
I am uploading a new version of Recharged today that should fix the flickering lights.
Ok but if you run the desert level in the full version, does that have the performance issue?
I'm not a Linux user myself so I wouldn't really know how to begin examining it, but I presume there is some kind of CPU/GPU performance monitor included in your distribution that you might have a look at (while running the simulator) to see if you can find a clue as to what the bottleneck might be.