SMN204 Posted Saturday at 08:46 PM Report Posted Saturday at 08:46 PM Many of the control sets in FSUIPC do not work! For example, all of these don't work! Landing_Light_Switch_Left_Up#OVHD_LTS_LDG_L_SW_RIGHT_BUTTON_DOWN#90258 (>L:CEVENT) Landing_Light_Switch_Right_Down_#OVHD_LTS_LDG_R_SW_RIGHT_BUTTON_DOWN#90260 (>L:CEVENT) Landing_Light_Switch_Right_Down__#OVHD_LTS_LDG_R_SW_Right_BUTTON_DOWN#90259 (>L:CEVENT) Landing_Lights_Left_Switch_Down__#OVHD_LTS_LDG_L_SW_LEFT_BUTTON_DOWN#90257 (>L:CEVENT) Left_Runway_Turnoff_Light_Button_Press_#OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_DOWN#90263 (>L:CEVENT) Left_Runway_Turnoff_Light_Button_Release#OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_UP#90264 (>L:CEVENT) Nose_Gear_Light_Switch_Down#OVHD_LTS_NOSE_SW_RIGHT_BUTTON_DOWN#90262 (>L:CEVENT) Nose_Gear_Light_Switch_Up#OVHD_LTS_NOSE_SW_LEFT_BUTTON_DOWN#90261 (>L:CEVENT)
John Dowson Posted Sunday at 09:25 AM Report Posted Sunday at 09:25 AM This is because they are using custom control numbers above 84232. which is the maximum that is mapped (and can therefore be used) by default. To allow for higher numbers, you need to set the following ini parameter in the [General] section of your FSUIPC7.ini file: MaxCustomControlNumber=96323 Your FSUIPC7.log file will tell you what numbers are mapped and can therefore be used: Quote 35468 Mapping custom control numbers 69632 - 96323 (maximum defined by ini parameter MaxCustomControlNumber, defaults to 84232 when not present) John
SMN204 Posted Sunday at 12:34 PM Author Report Posted Sunday at 12:34 PM 3 hours ago, John Dowson said: MaxCustomControlNumber=96323 It's working! Thank you.
SMN204 Posted Sunday at 09:47 PM Author Report Posted Sunday at 09:47 PM 12 hours ago, John Dowson said: MaxCustomControlNumber=96323 And this...? OBS_CKTBKR_LT_KB_WHEEL_UP 98304 OBS_CKTBKR_LT_KB_WHEEL_DOWN 98305
John Dowson Posted Monday at 08:44 AM Report Posted Monday at 08:44 AM 10 hours ago, SMN204 said: And this...? OBS_CKTBKR_LT_KB_WHEEL_UP 98304 OBS_CKTBKR_LT_KB_WHEEL_DOWN 98305 Isn't it obvious? 98304 and 98305 are more than the MaxCustomControlNumber set as 96323. Set that parameter the the maximum custom control number that you are using.
John Dowson Posted Monday at 10:50 AM Report Posted Monday at 10:50 AM Sorry - I think I got this wrong... On 11/16/2024 at 9:46 PM, SMN204 said: Landing_Light_Switch_Left_Up#OVHD_LTS_LDG_L_SW_RIGHT_BUTTON_DOWN#90258 (>L:CEVENT) Landing_Light_Switch_Right_Down_#OVHD_LTS_LDG_R_SW_RIGHT_BUTTON_DOWN#90260 (>L:CEVENT) Landing_Light_Switch_Right_Down__#OVHD_LTS_LDG_R_SW_Right_BUTTON_DOWN#90259 (>L:CEVENT) Landing_Lights_Left_Switch_Down__#OVHD_LTS_LDG_L_SW_LEFT_BUTTON_DOWN#90257 (>L:CEVENT) Left_Runway_Turnoff_Light_Button_Press_#OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_DOWN#90263 (>L:CEVENT) Left_Runway_Turnoff_Light_Button_Release#OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_UP#90264 (>L:CEVENT) Nose_Gear_Light_Switch_Down#OVHD_LTS_NOSE_SW_RIGHT_BUTTON_DOWN#90262 (>L:CEVENT) Nose_Gear_Light_Switch_Up#OVHD_LTS_NOSE_SW_LEFT_BUTTON_DOWN#90261 (>L:CEVENT) Custom control numbers are those used in assignments when selecting the "<Custom Control>" entry in the FSUIPC assignments drop-downs. Those presets are incorrectly specified, and looks like the description was mistakenly used as the preset name. e,g, the preset Landing_Light_Switch_Left_Up uses "OVHD_LTS_LDG_L_SW_RIGHT_BUTTON_DOWN#90258 (>L:CEVENT)" which is actually the preset definition, not the calc code. I think these have been added incorrectly, and should be: Quote OVHD_LTS_LDG_L_SW_RIGHT_BUTTON_DOWN#90258 (>L:CEVENT) OVHD_LTS_LDG_R_SW_RIGHT_BUTTON_DOWN#90260 (>L:CEVENT) OVHD_LTS_LDG_R_SW_Right_BUTTON_DOWN#90259 (>L:CEVENT) OVHD_LTS_LDG_L_SW_LEFT_BUTTON_DOWN#90257 (>L:CEVENT) OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_DOWN#90263 (>L:CEVENT) OVHD_LTS_RWY_TURNOFF_L_BT_LEFT_BUTTON_UP#90264 (>L:CEVENT) OVHD_LTS_NOSE_SW_RIGHT_BUTTON_DOWN#90262 (>L:CEVENT) OVHD_LTS_NOSE_SW_LEFT_BUTTON_DOWN#90261 (>L:CEVENT) John
SMN204 Posted Monday at 02:44 PM Author Report Posted Monday at 02:44 PM 3 hours ago, John Dowson said: I think these have been added incorrectly, and should be: Yes! In event.txt c hubhop many assignments are incorrectly specified . I did roughly like this in myevents.txt and it works! LDG_LT_L_Down#90258 (>L:CEVENT) LDG_LT_L_Up#90257 (>L:CEVENT) LDG_LT_R_Down#90260 (>L:CEVENT) LDG_LT_R_R_Up#90259 (>L:CEVENT)
John Dowson Posted Monday at 02:46 PM Report Posted Monday at 02:46 PM 1 minute ago, SMN204 said: In event.txt c hubhop many assignments are incorrectly specified . I did roughly like this in myevents.txt and it works! LDG_LT_L_Down#90258 (>L:CEVENT) LDG_LT_L_Up#90257 (>L:CEVENT) LDG_LT_R_Down#90260 (>L:CEVENT) LDG_LT_R_R_Up#90259 (>L:CEVENT) Yes - you should update these in HubHop, or at least report as erroneous,
SMN204 Posted Tuesday at 12:28 PM Author Report Posted Tuesday at 12:28 PM One more question. The “Master Cautuon” from my “myevents.txt” is assigned to button A25 Master_Caution_Press#86110 (>L:CEVENT) Master_Caution_Depress#86111 (>L:CEVENT) When assigned, everything works fine. But after a while it stops working! In the log instead of the code: 86110 (>L:CEVENT) I see this code: 2 (>L:var_masterCautionLatching). So that's why it stops working. I assign it again - it works and then “86110 (>L:CEVENT)” is replaced automatically to “2 (>L:var_masterCautionLatching)” I see this in FSUIPC7.log 2017265 Button changed: bRef=0, Joy=1 (A), Btn=25, Pressed 2017265 [Buttons.TFDi Design MD-11F GE CF6-80c] 157=PA,25,CPMaster_Caution_Press,0 2017265 [DEBUG]: Calculator code sent: 2 (>L:var_masterCautionLatching) 2017468 Button changed: bRef=0, Joy=1 (A), Btn=25, Released 2017468 [Buttons.TFDi Design MD-11F GE CF6-80c] 158=UA,25,CPMaster_Caution_Depress,0 2017468 [DEBUG]: Calculator code sent: 86111 (>L:CEVENT)
John Dowson Posted Tuesday at 12:43 PM Report Posted Tuesday at 12:43 PM This is because you are using a preset name already defined in the events.txt file: Quote //Black Square/Duke/Warning Master_Caution_Press#2 (>L:var_masterCautionLatching) Master_Warning_Press#2 (>L:var_masterWarningLatching) Please give your presets a unique name. As most presets are aircraft dependent, its a good idea to prefix the preset name with the aircraft name, e.g. TFDi_MD11_Master_Caution_Press#86110 (>L:CEVENT) TFDi_MD11_Master_Caution_Depress#86111 (>L:CEVENT) I should maybe add a check to make sure the name is unique when loading the presets... John
SMN204 Posted Tuesday at 03:24 PM Author Report Posted Tuesday at 03:24 PM 2 hours ago, John Dowson said: This is because you are using a preset name already defined in the events.txt file Oh, that's the reason !!! 2 hours ago, John Dowson said: I should maybe add a check to make sure the name is unique when loading the presets... 👍
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now