Jump to content

Recommended Posts

Posted (edited)

Update: The report below can be disregarded.  I finally had some time to delve into this, and discovered that the hooked script interrogating the lamps signals was reading the NMSP HARS signal, 606, and then reading the caution lamp HARS signal, 511, using the same 'HARS' identifier, thus overwriting the NMSP value.  Changing the latter identifier to 'HARS_CAUTION' corrected the issue.

Original post:

While trying to implement the A-10C II NMSP panel lights on an external panel, I found that the HARS signal (606) is always 0.  In a cursory search through the mod code I found the following in ...\Mods\aircraft\A-10C_2\Cockpit\Scripts:

-- Navigation Mode Select panel
count = 0
NMSP_buttons = 
{
	flag_HARS = 0,
	flag_EGI = counter(),	
	flag_TISL = counter(),	
	flag_STRPT = counter(),	
	flag_ANCHR = counter(),	
	flag_TCN = counter(),	
	flag_ILS = counter(),
	flag_UHF = counter(),	
	flag_FM = counter()	
}
 
 function NMSP_button_light(arg,flag)
	local light_  		= CreateGauge()
	light_.arg_number	= arg
	light_.input		= {0.0, 1.0}
	light_.output		= {0.0, 1.0}
	light_.params 		= {flag}
	light_.controller	= controllers.NMSP_button_light_controller
end

NMSP_button_light(606, NMSP_buttons.flag_HARS)	-- HARS

 

I suspect this has probably been noticed by others and there is a good reason elsewhere in the scripts, but I can't help but wonder if this is simply an error and, if  so, whether we could get this fixed.

Thanks.

Edited by Slipstick
changed wording
  • Slipstick changed the title to A-10C II - HARS signal always zero: Resolved
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...