Ron Attwood Posted June 21, 2024 Report Posted June 21, 2024 First let me make clear I don't think this is an FSUIPC7 problem. This is manifested only on Blackbird/Milviz's F-4 Corsair. The command works on every other aircraft that it's assigned to. I've posted on the Milviz Support forum but there's a deadly hush. I just wondered if you could throw some light on it. The axis works with the in-game controls but not in FSUIPC7 Log and .ini attached FSUIPC7.ini FSUIPC7.log
Ron Attwood Posted June 21, 2024 Author Report Posted June 21, 2024 Stand down. I figured it out. Milviz, for reasons best known to themselves, use different commands to everyone else Instead of AXIS_THROTTLE_SET, they use THROTTLE_AXIS_SET_EX1 This is my .ini extract 2=DZ,256,F,65765,67096,0,0 -{ TO SIM: AXIS_THROTTLE_SET, THROTTLE_AXIS_SET_EX1 }- Back to real life. 😁
John Dowson Posted June 25, 2024 Report Posted June 25, 2024 Different aircraft use different controls/events. You can use the logging facilities in FSUIPC to see what an aircraft is using - for axes controls, just set logging for Axes Controls, open the logging console (Log -> Open Console) and see what is logged when you move the axis in the VC, then use that. Note also that for some aircraft there can be no controls/events that work, and you have to look into other methods of control, such as Input Events or Lvars. John
Recommended Posts