April 8, 200521 yr I really need some help if someone can help me. I want to use the map mode of the ch yoke to program buttons for each panel i have PMDG, LDS, etc. BUT if i use map mode, FSUIPC does not recognize any buttons on my joystick at all. It is nice to use my prop control for reverse, mixture for spoilers etc but if fsuipc will not recognize my yoke then i am s.o.l. Has anyone figured a way around this? thx guys
April 8, 200521 yr You can always program FSUIPC's button assignments to be aircraft specific, at least that is what I have done for those instances. Another option came to me from Fr. Bill, you can make a copy of your FS9.exe and FS9.cfg files and rename them to the aircraft you want a specific programming for (you just have to be sure that the name of the executable is exactly the same as the configuration file). Then use the specific file for each jet when you fly it. I have done this for 4 engine, vs 3 engine, vs twin and it works just fine.Just more options,Zane Dr Zane Gard Sr Staff Reviewer AVSIM Private Pilot ASEL since 1986 IFR 2010 AOPA 00915027 American Mensa 100314888
April 8, 200521 yr But the ting is if i use ch manager i can use a button on my yoke to be assigned as a shift button. with that i can turn the 12 buttons into 23 useable buttons BUT i believe you have to use the MAP mode in ch manager to do so and as said before going into map mode makes it so fsuipc can not read the yoke buttons. DOH!
April 8, 200521 yr Actually this is weird. In map mode FSUIPC recognizes my prop level as being used for reverse on page 7 of 10 int he joysticks menu BUT it will not recognixe mixture control for spoilers
April 8, 200521 yr Hi Monsoon,Go into Flight Sim and check the Sensitivity and Null Zone page. When you activate a map, FS doesn't have a default set of assignments for the "Control Manager Devices" that it creates and it falls back the the 4-axis defaults defined in Devices.cfg. As a result it sets some of the axes to 0% sensitivity. FS will still assign the axis, but it won't move any control surfaces and FSUIPC can't see it move either. Anyway, make sure the sensitivities are 100% and the null zones are 0%, usually that fixes it right up.Best regards,- BobThe StickWorkshttp://www.stickworks.com
Create an account or sign in to comment