This are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Problem with the TFDi MD11 in MSFS2024
Hello, I'm having a problem with the TFDi MD 11 and its events for landing lights and nose lights, as the numbers are above 90xxx. The custom control and the hop-hop presets aren't responding. Is there a solution? Oddly enough, some things do work, but I'd really like to have the landing and taxi lights on a joystick button.
Regards, Thomas
Posted by: @tommymahoneyI’m having a problem with the TFDi MD 11 and its events for landing lights and nose lights, as the numbers are above 90xxx. The custom control and the hop-hop presets aren’t responding. Is there a solution?
By default, FSUIPC7 only allows for custom controls in the range 69632 to 84232. If you want to use custom controls outside of this range, you can increase this range by setting the MaxCustomControlNumber ini parameter. From the Advanced User guide:
MaxCustomControlNumber: allows the maximun custom control number available for assignment to be specified. Several add-on aircraft use “custom controls”. These are control numbers starting from 69632. By default, FSUIPC7 only maps, and therefore makes available, custoom control numbers 69632 to 84232. If you want to use custom control numbers greater than this, then use this parameter to set the maximum custom control number needed.
Also check your FSUIPC7.log file - the range of custom controls available should be logged in a message.
Not sure why the presets aren't working though, as these should not depend on the custom control mapping. Are other presets working? i.e. is this just a problem with the presets for the MD11 or is it a general problem?
Hello, yes, I managed to do it using the MaxCustomControl extension and the normal Custom Control Button up and down function. However, the Huphop presets contain a function for controlling only one button and both landing lights, but it doesn't work, perhaps it's too complex:
Both_Landing_Light_Retracted#0 (L:md11_ovhd_lts_ldg_l_sw,number) - s0 0 (L:md11_ovhd_lts_ldg_r_sw,number) - s1 :1 l0 0 > if{ 1 90258 (>F:KeyEvent) l0 -- s0 g1 } l0 0 < if{ 1 90257 (>F:KeyEvent) l0 ++ s0 g1 } l1 0 > if{ 1 90260 (>F:KeyEvent) l1 -- s1 g1 } l1 0 < if{ 1 90259 (>F:KeyEvent) l1 ++ s1 g1 } }
Both_Landing_Lights_Extended#1 (L:md11_ovhd_lts_ldg_l_sw,number) - s0 1 (L:md11_ovhd_lts_ldg_r_sw,number) - s1 :1 l0 0 > if{ 1 90258 (>F:KeyEvent) l0 -- s0 g1 } l0 0 < if{ 1 90257 (>F:KeyEvent) l0 ++ s0 g1 } l1 0 > if{ 1 90260 (>F:KeyEvent) l1 -- s1 g1 } l1 0 < if{ 1 90259 (>F:KeyEvent) l1 ++ s1 g1 }
Both_Landing_Lights_On#2 (L:md11_ovhd_lts_ldg_l_sw,number) - s0 2 (L:md11_ovhd_lts_ldg_r_sw,number) - s1 :1 l0 0 > if{ 1 90258 (>F:KeyEvent) l0 -- s0 g1 } l0 0 < if{ 1 90257 (>F:KeyEvent) l0 ++ s0 g1 } l1 0 > if{ 1 90260 (>F:KeyEvent) l1 -- s1 g1 } l1 0 < if{ 1 90259 (>F:KeyEvent) l1 ++ s1 g1 }
I also see that LVAR is written in lowercase, while everything in the TFDI Integration Guide is in uppercase. Could that be the problem?
best wishes for the Day
Posted by: @tommymahoneythe Huphop presets contain a function for controlling only one button and both landing lights, but it doesn’t work, perhaps it’s too complex
If a HubHop preset isn't working, you can ask about this on HubHop support. I don't have the MD11 so cannot look into this. The complexity of the RPN doesn't matter, as long as its valid...!
Posted by: @tommymahoneyI also see that LVAR is written in lowercase, while everything in the TFDI Integration Guide is in uppercase. Could that be the problem?
No - lvars are case independent.
John