chickster25

Thank you for the explanation and additional information. I will take another look and see if I can replicate the same functionality that you have found.

Hi John So I have followed your instructions and set up the Myevents.txt file and added into FSUIPC, as a "Send Preset to FS". For clarity, on the Axes Assignments screen, In/out goes from 16383 to -16384 when I move the lever. I have cleared the spoiler setting on the Joystick calibration page. When I get into the cockpit of the PMDG 737, the spoiler lever on screen is not moving inline with my movements. It is moving randomly and stopping midway, even if the real lever is full open or closed? Although my in/out settings match yours, I dont understand what the +327.68 refers to? FSUIPC7.ini FSUIPC7.log myevents.txt

Hi Thanks for your quick reply. I have tried to do as instructed by hit a few issues. When setting "Send Direct to FSUIPC Calibration" the option of "Spoilers" can be chosen and then I can set the in/out When I choose "'Send to FS as normal axis", the option of "Spoilers Set" is the only thing I can select. When I went to the Joystick calibration screen, I could not set the In/out for spoilers as the lever was not having any effect? I do not have any clashing assignments in MSFS for this lever. FSUIPC7.ini FSUIPC7.log

Hi, I am using a Logitech quadrant as well as the Logitech yoke. I am using the first lever Joystick-L-X for the spoiler settings. In Windows control panel, I can see the level setting moving and it can go in the full range from 0-255 as expected. I have set the spoiler in FSUIPC and used "Send Direct to FSUIPC Calibration" but when I go to Joystick calibration for the spoiler, the In/Out settings are all over the place. The numbers are moving, even when the lever is stationary and I cannot get the numbers to show the full range. The numbers are moving constantly? Any ideas, as the device looks fine in windows 10? I am using the latest version .23 of FSUIPC?

Hi all, I am having a similar problem with the ATR, where i am unable to use the throttles via FSUIPC but the flaps are working with the default settings. Will wait for John to take a look at the ATR before trying some of the workarounds

Hi John, I have a weird issue since the last PMDG update in that the rudder is not working with the 737-700. It works with all the other variants, -600, -700-BBJ etc just not the main 700. When I load the aircraft on the runway, the rudder initially has restricted movement from the maximum range. As I move the pedals left and right, the rudder control becomes less and less each time until it is fixed dead centre. It takes about 5-6 movements before there is no rudder at all. This shown on screen as the tail does not move after this point. I have tested multiple times with the same result. I have also tested with other aircraft which are unaffected. I am using the latest version of FSUIPC v7.3.19 FSUIPC7.log FSUIPC7.ini

Ok thanks, that makes it a bit clearer. I will give it a try. Thank you

Hi John thanks for your help with this. I am a little confused with this advice, as when I calibrate I only take the lever to the zero position, which registers at -16384. This is not the bottom of the lever slot where the button detection (for reversers) is. There is a gap between zero and the bottom where button detection takes place, so there should be no conflict.

Hi John Thanks for the reply. I did have a 737 profile but seems its been lost either when i added the new quadrant or updated the version. Anyway i have added a new profile and have checked that there are no conflicting settings in MSFS controls (there are not) I am finding that when the levers are in the neutral position or when I reduce throttle, the engine covers show in the reverse position. This should not happen as I have reverse set as a button (which is the furthest down position of the lever). Hope that makes sense. So I am wondering if it is something to do with the button config that I am using for reverse thrust? The image shows the button set for throttle1 lever, I have the same settings for throttle 2 button. I got it off the forum but wonder if the settings should be different to what I have? FSUIPC7.ini FSUIPC7.log

Hi John I have upgraded my Logitech throttles so now I have 2 throttle quadrants with 6 levers - 1x spoiler, 4x throttle, and 1x flaps. Windows detects the existing quadrant as part of the logitech yoke, with the new quadrant detected as a USB quadrant. The USB quadrant is now the first device, with throttles 1 & 2. The 'Yoke' quadrant' has throttle 3 & 4. Each throttle lever is set to move independently (not move all 4 together) I have tried to configure the throttles for a 4 engine aircraft, so when using a 737, I am only using the first two levers. Also, when I bring the levers down to the bottom (red zone) then they should work as reverse thrust. I am having some issues with the PMDG 737. The issue is intermittent as when I first load the aircraft and increase thrust via my logitech levers, they appear to be moving the in-game reverse thrust levers instead of the throttles. If I move them up and down a bit more or one at a time, the game then appears to detect them as throttles and they work correctly. There seems to be a clash between what the game is doing with this config, until it sorts itself out. Once in the air, the throttles work for power, although the reverse levers are 'flicking about' when I move the lever, even though I am nowhere near the zero (or minus) lever position. FSUIPC7.ini FSUIPC7.log

Hi John Thank you for your help with this. I have made the amends as you recommended and it is working, although I did not change the profile name from FSUIPC as its taken me months to get it all set up and I dont want to lose what I have configured so far. I also have two questions if you have time 1. For the Bae-146, the rudder does not work first time, unless I jump out of MSFS and open FSUIPC to detect the rudder on the Axes Assignment, then I can go back into MSFS and its working 2. I have attempted to load the variants for the BAE -146, but I am not sure if I have added them correctly via the same profile? [Profile.Bae-146 Professional] 1=JF 146-100 2=JF 146-200 3=JF 146-300 Thanks for your assistance FSUIPC7.ini

Hi John I tried to follow the instructions to create the new profile, but I seem to have got myself into a bit of a tangled mess. I cannot see where I am supposed to add the second throttle line in the .ini file, as mine only has one (shown as line 3) - even though I added two throttle lines onto the Axis Assignment tab Before Changes 0=AX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=AY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=AZ,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 3=AU,256,D,4,0,0,0 -{ DIRECT: Throttle }- 4=AV,256,D,23,0,0,0 -{ DIRECT: Flaps }- After adding BAE-146 profile and adding two throttle assignments: [Axes.FSUIPC] RangeRepeatRate=10 0=AX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=AY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=AZ,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 3=AU,256,D,4,0,0,0 -{ DIRECT: Throttle }- 4=AV,256,D,23,0,0,0 -{ DIRECT: Flaps }- 5=CX,256,D,21,0,0,0 -{ DIRECT: ElevatorTrim }- 6=DX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 7=DY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 8=DR,256,D,3,0,0,0 -{ DIRECT: Rudder }- [Buttons.FSUIPC] 0=PA,32,C65734,0 -{PAN_UP}- 1=PA,38,C65671,0 -{PAN_LEFT}- [Profile.Bae-146 Professional] 1=Whopperators JF 146-100 Flybe Old [Buttons.Bae-146 Professional] 0=PA,32,C65734,0 -{PAN_UP}- 1=PA,38,C65671,0 -{PAN_LEFT}- [Axes.Bae-146 Professional] RangeRepeatRate=10 0=AX,256,D,1,0,0,0 -{ DIRECT: Aileron }- 1=AY,256,D,2,0,0,0 -{ DIRECT: Elevator }- 2=AZ,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 3=AU,256,F,67096,67110,0,0 -{ TO SIM: THROTTLE_AXIS_SET_EX1, THROTTLE2_AXIS_SET_EX1 }- 4=CX,256,D,21,0,0,0 -{ DIRECT: ElevatorTrim }- 5=DX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 6=DY,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 7=DR,256,D,3,0,0,0 -{ DIRECT: Rudder }-

Hi, I am running the latest version of FSUIPC 7.3.16 but when i try to use the JF BAE 146 there is no throttle. If I go into FSUIPC it is detecting a throttle input ( on 1 0f 11 : Main Controls) and it is set to Direct input. Other inputs from my saitek work, such as rudder and flaps. If I change my controls to MSFS assigned, then the throttles work. I can use FSUIPC assignments with other aircraft, just not the BAE 146 thanks FSUIPC7.ini

Hi John Thank you for replying so quickly. I had another go and whilst it was better this time (I did mention it was intermittent) i did notice a few things 1. If FSUIPC detects an Axis and then you hit the clear button to reset for another test, it does not detect anything for the movement in the dropdown section - but does show the numbers moving in unison with the actual movement. You have to exit the screen and reopen it for it to detect anything. 2. When trying to detect the rudder, FSUIPC found the left brake 3 times in a row, even though I was moving the rudder pedal. On the fourth attempt, it found the rudder. This then worked in MSFS as expected. 3. I could not replicate it not finding the spoiler axis/lever on my Saitek as it did earlier, so will continue trying... FSUIPC7.ini FSUIPC7.log

Hi, I seem to be having all sorts of issues with FSUIPC since the last update. All my inputs are intermittent, so they will be detected on the Axes Assignments screen at one point, but then if I return, then they are not being detected. I have set all inputs to Send Direct to FSUIPC calibration but they do not always work in game. For instance, I set my saitek rudders via FSUIPC and they were working. When I reloaded MSFS, the rudders were not working and not being detected on the Axes Assignment page - but were being detected on the Joystick calibration tab. If I changed the rudder config in MSFS to non-FSUIPC, then the rudders were working in game with no issues. The same thing happened with the spoiler, in that I set it in FSUIPC and it was all detected and working. When I went back into FSUIPC to tweak a setting, it was not being detected by FSUIPC at all. I am not sure what is happening but I have had to revert to MSFS controls as I cannot get a reliable connection via FSUIPC. I am not having issues when controlling directly via MSFS controls. FSUIPC7_prev.log FSUIPC7.log FSUIPC7.ini