Henry Street

Pete, Apologize for the delayed response, have not had time to get back to the sim for a bit. Just for completeness, I will say I am using letters A-E for my assignments and (obviously) are what are re-assigned when I delete the letter assignments and run FSX again. This does appear to be some USB detection issue with my computer, a Windows 10 machine with ASRock motherboard. I am keeping my eye out for driver/bios updates. For now, your suggestion to disable auto letter assignments seems to be doing the trick. Thanks again for taking a look at this. Good luck with Lockheed Martin.

Pete, Hope all is well with you. The good news is this post is not about P3D v3. I am having an issue that does not seem to be caused by FSUIPC but I am not sure. There are 5 joystick devices on my system connected thru a powered USB hub. Many times, but not always, I will go into FSX and the assignments will not work. In FSUIPC.ini I see the duplicate entries below. The workaround is to exit FSX, delete all the joy letters in FSUIPC.ini, then restart FSX. The joy devices are always detected in the correct order and I never have to delete the joy numbers part. Any ideas for the cause that I can chase down? Thanks for any help or advice you can offer. Henry [JoyNames] AutoAssignLetters=Yes 0=Saitek Pro Flight Combat Rudder Pedals 0.GUID={7AA7F380-5A32-11E5-8001-444553540000} 1=F16 MFD 2 1.GUID={7AA81A90-5A32-11E5-8003-444553540000} 2=F16 MFD 1 2.GUID={7AA81A90-5A32-11E5-8004-444553540000} 3=Joystick - HOTAS Warthog 3.GUID={7AA868B0-5A32-11E5-800A-444553540000} 4=Throttle - HOTAS Warthog 4.GUID={7AA88FC0-5A32-11E5-800B-444553540000} A=Saitek Pro Flight Combat Rudder Pedals A.GUID={F0499980-5A10-11E5-8001-444553540000} B=F16 MFD 2 B.GUID={F049C090-5A10-11E5-8003-444553540000} C=F16 MFD 1 C.GUID={F049C090-5A10-11E5-8004-444553540000} D=Joystick - HOTAS Warthog D.GUID={F04A0EB0-5A10-11E5-800A-444553540000} E=Throttle - HOTAS Warthog E.GUID={F04A35C0-5A10-11E5-800B-444553540000} F=Saitek Pro Flight Combat Rudder Pedals F.GUID={7AA7F380-5A32-11E5-8001-444553540000} G=F16 MFD 2 G.GUID={7AA81A90-5A32-11E5-8003-444553540000} H=F16 MFD 1 H.GUID={7AA81A90-5A32-11E5-8004-444553540000} J=Joystick - HOTAS Warthog J.GUID={7AA868B0-5A32-11E5-800A-444553540000} K=Throttle - HOTAS Warthog K.GUID={7AA88FC0-5A32-11E5-800B-444553540000}​

Thanks for the correction, it is working now! I am using LINDA with Thrustmaster MFD and creating a library for Dino C's Goshawk.

Hi Pete, I am a complete novice at programming so please bear with me. I am trying to program the MFD's in the default Hornet using LUA. This picture shows the FSUIPC button definition that is working. Is this Lua command (not working) the equivalent to that FSUIPC programming? function Rt_MFD_Button_5 () ipc.writeDD(x3110, x00011205) end Thanks for all your help

http://fs-linda.com/ http://forum.avsim.net/forum/424-linda/

Could LINDA help?

The condition levers in the Bronco map with the FSX commands for fuel mixture. There is a post/thread in the Aerosoft support forum. I have this mapped with the "slider" axis on my Thrustmaster HOTAS and it works great.