$Player Autoaim FOV: works in degrees, not radians. 1 degree isn't really going to be very noticeable, try bumping that up to 30, seeing if that has any effect, and then troubleshooting from there.
Also FSO should fully support any dinput gamepad or joystick and only the triggers will be problematic for xinput ones so you're probably better off rebinding controls in-game rather than using software to map your gamepad to keyboard presses.
Oh you're right, judging from videos I watched from mods using it, I thought there'd be some sort or triangle lock-on and that it didn"t have to be bumped too high to have any effect. Tried at 30 and it's indeed working. Silly me.
About the controls, I'm letting the joysticks mapped in game but there's just too much needed mappings for a single gamepad. Pinnacle can bind double commands (single press / double press or long press) and toggle profiles on the fly so I can deal with wings orders and energy / shields management as well. Pretty handy.
Thanks for the help !
EDIT : I may add that for making this work for FS Port, the $Profile Name must be FS1 RETAIL. FS2 works with FS2 RETAIL. STR works with SILENT THREAT REBORN. since you can add up to 9 profiles, it's pretty handy when mods uses different profiles. For example, my autoaim-aip.tbm for FS Port and STR is like this :
#AI Profiles
$Profile Name: FS1 RETAIL
+nocreate
$Player Autoaim FOV: 30,30,30,30,30
$Profile Name: SILENT THREAT REBORN
+nocreate
$Player Autoaim FOV: 30,30,30,30,30
#End
30 is for testing, it's obviously way too big and needs to be narrowed to a value you're comfortable with. Now I can enjoy even more all these great mods !