New axis

[Baldawg]

As the title states I was successful in adding the Variable Sight Selector Unit (VSSU) as an axis by adding the line below in \Mods\aircraft\F-86\Input\F-86F\joystick\default.lua

 

{action = device_commands.Button_23,	cockpit_device_id = devices.A4_GUNSIGHT,	name = _('Variable Sight Selector Unit - Rocket Depression Angle Selector - CW/Increase'),	category = {_('Center Pedestal'), _('A-4 Sight')}},

 

The issue I am presented with is the reaction of the in game knob compared to the actual potentiometer movement doesn't coincide and has a very narrow field of adjustment close to the center of the axis range of motion. i bound the axis I'm using for the VSSU to the Wing Span axis and it works as it should ruling out a hardware issue. I've tried adjusting curves and x,y saturation to give a smooth transition of movement throughout the full range but cant seem to dial it in.

 

I've looked in the clickabledata.lua to try to compare designed axis' to see if i can get the same results as the Wing Span, Bomb Wind Control, and other axis for example. What these share in code are not common

 

Wing Span:

elements["Wing_span_adjustment_knob"] =	{	
class 		= {class_type.LEV},
hint  		= _("A-4 Sight Wing Span Adjustment Knob"),
device 		= devices.A4_GUNSIGHT,
action 		= {device_commands.Button_1},
arg 	  	= {716},
arg_value 	= {0.0215}, 
arg_lim   	= {{0,1}},
updatable 	= true, 
use_OBB 	= true,
gain		= {0.1},	
cycle		= false
}

 

Bomb Wind Correction:

local Bomb_wind_control 					= default_axis (_("Bomb-Target Wind Control Knob") 		 , devices.A4_GUNSIGHT, device_commands.Button_14, 727,0.0215, 0.6, false,false,false)
Bomb_wind_control.arg_lim   				= {{-1,1}}
elements["Bomb_wind_control"] 				= Bomb_wind_control	

 

Is the lack of the above syntax the cause of the VSSU axis not performing as desired?

[gnouze]

No comprendo

 

 

Envoyé de mon iPad en utilisant Tapatalk

[funkyfranky]

The issue I am presented with is the reaction of the in game knob compared to the actual potentiometer movement doesn't coincide and has a very narrow field of adjustment close to the center of the axis range of motion.

I have this problem also with some of the axes I added manually. Seems that some axes react like this. Unfortunately, I could not figure out a way to solve it yet. I you find a way, I would also be very interested ;)