Andre69271 Posted September 25, 2020 Report Posted September 25, 2020 Hi, after installation fsuipc 6 in the default locations (P3D v4 only) and re-naming the v5 ini file, I found that only the rudder, elevator and pitch axis are working, no switches and no buttons, also on the controller screen I dont see any inication that the axis or something else is programmed. Do I missed soomething? Thx for any help Andre
Pete Dowson Posted September 25, 2020 Report Posted September 25, 2020 1 hour ago, Andre69271 said: after installation fsuipc 6 in the default locations (P3D v4 only) and re-naming the v5 ini file, I found that only the rudder, elevator and pitch axis are working, no switches and no buttons, also on the controller screen I dont see any inication that the axis or something else is programmed. Is the only change you made upgrading from FSUIPC5 to FSUIPC6? If you made no other changes, no Windows updates, no P3D4 reinstallation, then all the settings in your FSUIPC5.INI file must still apply after renaming to FSUIPC6.INI if they were left intact. To help we do need to see the FSUIPC6 INI file, so please supply that. The FSUIPC6.LOG file would also help us to see that things are loading okay. Pete
Andre69271 Posted September 25, 2020 Author Report Posted September 25, 2020 As a matter of fact, I re-started my sim after 4 month pause (sommer time -LOL), so there was a LOT of win10 updating (no other modification). If the cause is the updating ,should I be worried when the a new update will come !? Otherwise, no problem , the whether is very bad, so with pleasure I will re-set Your splendid application! Anyway, I am attaching the 2 requested files. A. FSUIPC6.ini.lnk FSUIPC6.log.lnk
John Dowson Posted September 25, 2020 Report Posted September 25, 2020 1 hour ago, Andre69271 said: Anyway, I am attaching the 2 requested files. I don't know what those files are, but they are certainly not the FSUIPC6.log and FSUIPC6.ini files requested. If you go the the logging tab of FSUIPC6, you will see a button to open the installation folder location. Use that, and send us the FSUIPC6.ini andFSUIPC6.log files from that location please. The files you sent are binary files, and look to be (binary) shell link files. Why do you have these, and what for?
Andre69271 Posted September 25, 2020 Author Report Posted September 25, 2020 Sorry , apparently the "ink" extension was added when I draged the files here! I dont have any files in P3D module folder! A. FSUIPC6.ini FSUIPC6.log
John Dowson Posted September 25, 2020 Report Posted September 25, 2020 33 minutes ago, Andre69271 said: dont have any files in P3D module folder! Then FSUIPC6 is not installed into your modules folder, With FSUIPC6, you must select the installation folder when you install. Looking at your log file, you installed FSUIPC6 in this location: C:\Users\Andre\Documents\Prepar3D v4 Add-ons\FSUIPC6 You should really choose a different location. That is the default installation folder for a clean install, and is where the add-on.xml file is (always) located. It is better to choose a different folder for the actual installation directory. Your ini file is confusing. Could it be that your joystick ids have changed? These are your devices: 0=Joystick - HOTAS Warthog 1=Mad Catz Pro Flight Rudder Pedals 2=Throttle - HOTAS Warthog You seem to have a throttle axis assigned to your joystick in various places: 2=0Z,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- And elsewhere also have ailerons, elevator, propeller and mixture assigned to your throttle: 8=2X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 9=2Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 11=2U,256,F,66291,0,0,0 -{ TO SIM: AXIS_PROPELLER_SET }- 12=2V,256,F,66292,0,0,0 -{ TO SIM: AXIS_MIXTURE_SET }- 8 hours ago, Andre69271 said: also on the controller screen I dont see any inication that the axis or something else is programmed. This I don't understand. You have plenty of assignments, although maybe to the wrong devices.... The first thing you should do is activate the 'JoyLetters" facility. See the user guide for details, but to activate just set this in the [JoyNames] section of your ini file and then run P3D: AutoAssignLetters=Yes This will assign letters yo to your devices which won't change, even if the joystick Id changes, preventing problems with assignments when this happens. You then need to review your assignments. I cannot tell which button you have on which device, but you should know this.If you review your ini after the above change, you can switch the device the assignment is made against by changing to the appropriate letter. If that proves too difficult, it may be easier to delete your current assignments and start again. As an example, looking at your general button assignments, you have this: Quote 1=P2,19,C65603,0 -{FLAPS_DOWN}- 2=P2,16,C66079,0 -{GEAR_UP}- 3=P2,18,C65595,0 -{FLAPS_UP}- 4=P2,17,C66080,0 -{GEAR_DOWN}- 5=P2,4,C65615,0 -{ELEV_TRIM_UP}- 6=P2,5,C65607,0 -{ELEV_TRIM_DN}- 7=P2,7,C66277,0 -{AILERON_TRIM_RIGHT}- 8=P2,6,C66276,0 -{AILERON_TRIM_LEFT}- 9=P0,13,C65758,0 -{FLAPS_INCR}- 10=P0,12,C65759,0 -{FLAPS_DECR}- 11=R0,15,C65615,0 -{ELEV_TRIM_UP}- 12=R0,17,C65607,0 -{ELEV_TRIM_DN}- 13=P0,16,C66277,0 -{AILERON_TRIM_RIGHT}- 14=P0,11,C66080,0 -{GEAR_DOWN}- 15=P0,10,C66079,0 -{GEAR_UP}- 16=P0,5,C65752,0 -{PARKING_BRAKES}- 17=P0,18,C66276,0 -{AILERON_TRIM_LEFT}- 18=P0,6,C65861,0 -{AUTO_THROTTLE_TO_GA}- 19=R0,29,C65602,0 -{THROTTLE_DECR}- 20=U0,29,C65604,0 -{THROTTLE_CUT}- Looking at the first assignment: 1=P2,19,C65603,0 -{FLAPS_DOWN}- This is button 19 on your device 2, which is your throttle. Once you have assigned letters, this will change to something like: 1=PC,19,C65603,0 -{FLAPS_DOWN}- where your joystick id 2 is mapped to the letter C (although the actual letter may be different). If you know that this was assigned on your joystick (which has joystick id 0), then you need to find the letter assigned to the joystick (probably 'A'), so to switch this assignment back to your joystick you would change to: 1=PA,19,C65603,0 -{FLAPS_DOWN}- But really, I think you would be better of starting again. You don't have that many assignments, and they do look rather confusing. For example, you have your ailerons assigned to two different axis on your joystick (in general axes assignments): 0=0X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 3=0R,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- and you have duplicate button assignments but to different devices: To your HOTAS throttle (general buttons): 1=P2,19,C65603,0 -{FLAPS_DOWN}- 2=P2,16,C66079,0 -{GEAR_UP}- 3=P2,18,C65595,0 -{FLAPS_UP}- 4=P2,17,C66080,0 -{GEAR_DOWN}- 5=P2,4,C65615,0 -{ELEV_TRIM_UP}- 6=P2,5,C65607,0 -{ELEV_TRIM_DN}- 7=P2,7,C66277,0 -{AILERON_TRIM_RIGHT}- 8=P2,6,C66276,0 -{AILERON_TRIM_LEFT}- and to your HOTAS joystick:10=P0,12,C65759,0 -{FLAPS_DECR}- 11=R0,15,C65615,0 -{ELEV_TRIM_UP}- : assigned above 12=R0,17,C65607,0 -{ELEV_TRIM_DN}- : assigned above 13=P0,16,C66277,0 -{AILERON_TRIM_RIGHT}- : assigned above 14=P0,11,C66080,0 -{GEAR_DOWN}- 15=P0,10,C66079,0 -{GEAR_UP}- : assigned above 16=P0,5,C65752,0 -{PARKING_BRAKES}- 17=P0,18,C66276,0 -{AILERON_TRIM_LEFT}- : assigned above 18=P0,6,C65861,0 -{AUTO_THROTTLE_TO_GA}- 19=R0,29,C65602,0 -{THROTTLE_DECR}- 20=U0,29,C65604,0 -{THROTTLE_CUT}- Another example, in your 'beach' profile you have Aileron, Elevator and Throttle assigned both to your joystick and throttle: 0=0X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=0Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- 3=0U,256,F,66291,0,0,0 -{ TO SIM: AXIS_PROPELLER_SET }- 4=0V,256,F,66292,0,0,0 -{ TO SIM: AXIS_MIXTURE_SET }- ... 8=2X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 9=2Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 10=2Z,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }- 11=2U,256,F,66291,0,0,0 -{ TO SIM: AXIS_PROPELLER_SET }- 12=2V,256,F,66292,0,0,0 -{ TO SIM: AXIS_MIXTURE_SET }- All rather confusing!
Andre69271 Posted September 26, 2020 Author Report Posted September 26, 2020 Thank you for the explanations. have re-installed the fsuipc in a new (different) location, and started programming, keeping in mind your remarks. A
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