1 reply to this topic

[Hauksbee]

I can't get ROF to recognize either of my joysticks. It wants to fly-by-mouse. Where do I go to make the joystick the default? Thanks.

[mu2freighter]

I can't get ROF to recognize either of my joysticks. It wants to fly-by-mouse. Where do I go to make the joystick the default? Thanks.

I believe ROF includes normal joystick axes assigned as default, sounds to me like you were in the right place, the 'controls' GUI, but got your mouse assigned to pitch and or/roll.

ROF's most finicky aspect is when you go to change ANY control the first input it reads after activating the function gets that control assigned to it.

I'll bet money you're inadvertently assigning a mouse axis instead of the desired control if your binds don't seem to work; it's absurdly easy to move the mouse a tiny bit when you double click on a control function to reassign it. Happens to everybody.

Double click the desired control function, but before you move the stick, throttle or pedals or press a button, make sure the box that pops up isn't showing 'mouse_axis_x' or 'y.' If it is, you moved the mouse, guaranteed.

Hit 'retry' and be really really careful not to move that mouse on the next go, or (as Viper69 has suggested) with your mouse cursor positioned over the desired control, flip the mouse over and click it so the optical sensor or ball have nothing to input.

Remember to save after EVERY change!

My standard advice when setting controls: Each time you make a change to a control assignment, save it, and NOT to the default 'input' .map file, which can be overwritten by game updates. Just pick a name you'll easily recognize in the dropdown menu of the 'controls' GUI. Once you've created a good generic .map file with all of your preferred button and control device inputs, you can use it as a template later when/if you get into adjusting joystick response curves. Say you have that generic one selected (mine's just named 'x52' after the stick I use). When you change a response curve you then save it to something like 'sopcamel' or whatever the name of the plane it'll be used with is. Then you'll have that profile to use with that plane with all your desired buttons and such AND the modded response curves that can be called up in just a couple of seconds using the GUI in the main menu or in-cockpit.

I've made custom files for most of the planes and find it almost effortless to swap out as needed in SP or MP when I switch planes.

Now, I definitely recommend making copies of any .map you've created and storing them in a flash or external drive. They're the ONLY things you lose in the event of a system crash, everything else can be replaced from the disc and/or digitally downloaded. I've got a dozen or so of these with lots of hours spent making them. I'd hate to have to redo all of these, and the cheapest flash drive will hold a zillion of them, cheap insurance.

These .map files are saved to your 'Input' folder, and I periodically save the collection to my flash drive so they're complete and current. If I had to do a fresh install, all I'd have to do is copy and paste them into that 'Input' folder from my flash drive and the sim would be restored to where I left it.