Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

.Yes, but how can it even be affected by where throttle stick is at startup ? - that defies the whole point of storing calibration.

Messing up axis invertion should not be possible as well. It's the only application that behaves that way, would you please just make it like "any" other joystick calibration ?


The link you sent to a discussion thread , - when searched for work "calibration" (only that) - returns 17 pages of results !

I am frustrated because I bought it long time ago, mentioned the problem (apparently as many others) - and see that it's still ignored.

"Perfect symmetry is not needed by the way" - so, hitting full pitch forward can give a given pitch rate , but full back, something different, - also.. when roll left hits 100% , roll right may be restricted to 90% . in a any 3D flight , that would be a awfully poorly tuned vehicle.


Please observe that no other application has this amount of sliders and gadgets for joystick calibration.

Normally, you assign axis, manually or automatically, then ask user to center, and do maximum and minimum input. - and there you have it, values that can be scaled to internal attitude demand numbers, no need for manual sliders to move things up and down.

Finally - where a stick is during application start, is not supposed to have any influence. Just imagine if you had to restart Xplane every time pedals, throttle quadrant , trims, or the yoke were in anything that perfect center.

it would be nice to have the problems fixed, not tell people how to try to workaroud them (and still have imprecise controls.)

(2 edits)

My guess is that it's something with the joystick drivers on your particular setup that is doing something unusual. You should only have to calibrate once, and once that works, the simulator remembers the settings and they will be exactly the same the next time you start up the sim. If the behavior is different at different start-ups it must mean that the output (from your radio via the operating system) changes somehow. (Either that, or that your operating system somehow keeps Freerider from actually saving the settings. On Linux, they can be found in ~/.config/unity3d/[CompanyName]/[ProductName] I believe, so you can check if they are kept correctly).

You should know that I have spent a lot of time working with the calibration to enable it to work with most operating systems and USB controllers/dongles/radios. There are so many different variables, and some devices that give very strange values. I am developing in Unity and am using Unity's input manager the best way I can.