atrcaptainjohn

Let me see what the dev team comes up with for an answer. I certainly don't mind buying the new version, your software has been very good to me over the years. But then again, if it wouldn't fix my issues I don't see any reason to change. I just wanted to make sure that if I do I didn't have to start from scratch 🙂 Thanks for the assistance, you guys are the best!!

I am currently using a registered V5 for P3D v4.5. I am considering upgrading to the registered V6. Version 5 does all I need it to, but I'm having issues with my VAs ACARS that they thin might be related to the version of FSUIPC that I run, that's why I'm thinking about upgrading. If I do so, would I lose all my current settings, aircraft config files, etc? I don't really want to have to set everything up again from scratch. Thanks in advance :)

OK, I kind of did that. The .ini file I sent you this time was after I had run a flight with the 737. I still have the old .ini file with all the profiles. What I did was took the GUIDs from the file I just sent you and replaced the ones in the file you fixed previously (they had changed) with the correct ones. That got almost everything working in the 737, which is the only AC that I have installed right now. The only things that don't seem to be working are a few of the MFD buttons. Funny thing there is that some of them work as before, while a couple have moved from MFD1 to MFD2, and a few just do weird things. But I can sort that out. I have spent the last few hours studying how the .ini file is formatted, so maybe I can figure some of this out without having to bother you. But I have a question about the JOYNAMES section. The fix you sent me had me turning the autoassignletters on, and then each device was assigned a number. When I tried changing the GUIDs, I assigned numbers as well, and that didn't work at all. So I went back and assigned letters A-E, and that got it working. Why did numbers work in the fix you sent me, but I had to use letters to get them working? Of course you know that after running the sim the JOYNAMES expanded and each has a letter and a number. I was just confused why I had to use letters.

Yes, unfortunately I had to re-install Windows10. Didn't really want to but I had corruption issues that I couldn't get rid of, so I didn't have much choice in the matter. I will attach the fsuipc.ini file that worked on the last install after you fixed it for me that I copied over to this install, and subsequently showed duplicates. All the other files are the same as what I uploaded earlier. And whenever you have the time to help,m I know you are busy. You have no idea how much I appreciate the assistance. BTW, is there any guidance for how to do what you did last time? Or is it something that you just have to know? I ask because I am going to have to do all this for my P3Dv3 install at some point, and I would rather not have to bother you with it if I didn't have to. Thanks again, john FSUIPC5 (NOT WORKING).ini

Hey Pete, I hate to bother you again with this, but I had to start over with my install, so my problem is back. I tried to copy the fsuipc.ini file from the install you helped with at the beginning of the month, but the JOYNAMES section end up saying that there are duplicates and nothing works. So to get me by for now I renamed the fsuipc.ini file and let it build a new one. Could you assist me one more time with this? If you can please tell me what files you need to me upload and I will get those to you ASAP. Thanks so much.

I believe that did the trick. Thanks so much Pete! YOU are the BEST!! john croft

OK, here are the log files. There are 6, and I have appended (NEW) and (OLD) so you know whether they came from the new install or the old install. Thanks so much! FSUIPC5 (NEW).ini FSUIPC5 (NEW).log FSUIPC5 (OLD).ini FSUIPC5 (OLD).log FSUIPC5 Install (NEW).log FSUIPC5 Install (OLD).log

Pete, I just built a new rig, and am re-installing everything, I'll list the order of things that I have done below: 1) installed P3Dv4, then did a flight 2) installed FSUPIC5 (registered), just downloaded so I know it's the latest version, then did a flight. 3) I then copied the FSUPIC folder from the Modules directory from the old install to the new install. 4) Installed the PMDG 737NG and did a flight 5) coped the PMDG 737 directory from the old install to the new install. I was hoping that this would allow all my saved bey bindings to work in the new install, but apparently I have missed a step. I will say that when I originally installed FSUIPC I didn't set it to assign joystick letters, which I know I should have done, but I don't know if that is affecting this. Is there a step that I missed, or did I do something wrong? I would hate to have to re=assign everything, but I guess I will if I screwed something up along the way. I have attached the JoyScan.csv file, let me know if you want to see anything else. Thanks a ton! FSUIPC5.JoyScan.csv

Thanks so much Pete! You're a lifesaver :)

OK I renamed the section you mentioned and the aircraft in the aircraft.cfg file and that fixed it, thank you so much! One more question on the PMDG stuff though. Let's say I can figure out how to assign, lets say the heading knob up/down through the PMDG sdk stuff. How would I reassign it is FSUPIC so it wouldn't send the current keypresses but whatever new command that it needed to send? Would that happen automatically when I reassigned it? Thank you again! john

Yes, that makes sense. So can I just delete the [Maddog CAL] section from the .ini file, rename the a/c in the aircraft config file and reassign the maddog? And no, I have never looked at the other assignment options. I figured that because PMDG used keyboard presses for assigning button presses in the FMC setup that I needed to assign key presses and the map the stick buttons to those presses. Is there a toturoal somewhere on how to make that more efficient? Because I have essentially run out of keyboard options to assign to things, and there are more assignments that I would like to make, and I certainly have more joystick buttons that I could use.

OK, I think we found the issue. I never looked at the name that popped up at the top when I click the "profile specific" button. It says "Maddog CAL" when I have the PMDG 737 loaded. I still had the console log opened when I loaded the aircradt and I did notice that the log said the right aircraft when it was loading, but once loaded withe the FSUPIC intercafe open, on Buttons + Switches and I click "profile preficid" it is definitely showing "Maddog CAL". Regardless, I have programmed Joystick A, Button 0 to send the command "L". The .ini file and the log file are on the way to you. I appreciate your assistance with this. :) john

I'm sorry, I didn't see the suggestion to log. I started the console log, and loaded the PMDG 737 WL. The buttons that are not profile specific log just fine, the ones that are profile specific, nothing happens in the log when I press them. And yes, when I am in the FSUPIC interface and press a button, with profile specific checked, the correct stick and button appear to be showing when I press a button. I can just start reassigning things, but I don't want to screw something up if I can get it to work again because I had a lot of buttons assigned.

When I go to the FSUPIC interface with the specific aircraft loaded and click "profile specific" and then click one of the buttons, it shows as being pressed, shows which button it is, and says above that "choose the action for this button...". I have a HOTAS Warthog throttle and stick and 2 Thrustmaster MFD Cougars, and this happens regardless of which button I press, except for the ones assigned to non profile specific aircraft, which are gear, flaps, and trim. Like I said before, the ONLY thing that has changed id this morning I set up the throttle, prop, and mixture on a Carenado plane, and when I click on the "profile Specific" button to start assigning it popped up a dialog that asked me if I wanted to save previously made changes. I hadn't made any changes to that point, but I selected yes.

Here is my log file, it looks to me like the name matches exactly, but maybe I'm seeing it wrong. What I don't understand is that everything worked fine 2 days ago, which was the last time I flew either the 727 or the 777. ********* FSUIPC4, Version 4.949 by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "Z:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=5EC10000 User Name="John Croft" User Addr="atrcaptainjohn@yahoo.com" FSUIPC4 Key is provided WideFS7 Key is provided 62 System time = 26/02/2016 12:37:05 62 FLT UNC path = "X:\Users\John Croft\Documents\Flight Simulator X Files\" 62 ------ Module Version Check ------ 62 acontain.dll: 10.0.61637.0 62 api.dll: 10.0.61637.0 62 controls.dll: 10.0.61637.0 62 fs-traffic.dll: 10.0.61637.0 62 G3D.dll: 10.0.61637.0 62 sim1.dll: 10.0.61637.0 62 visualfx.dll: 10.0.61637.0 62 weather.dll: 10.0.61637.0 62 window.dll: 10.0.61637.0 62 ---------------------------------- 78 Trying to connect to SimConnect Acc/SP2 Oct07 ... 78 FS UNC path = "Z:\FSX\" 171 ---------------------- Joystick Device Scan ----------------------- 171 Product= Joystick - HOTAS Warthog 171 Manufacturer= Thustmaster 171 Vendor=044F, Product=0402 (Version 1.0) 171 Serial Number= 171 Product= Throttle - HOTAS Warthog 171 Manufacturer= Thrustmaster 171 Vendor=044F, Product=0404 (Version 1.0) 171 Serial Number= 171 Product= Saitek Pro Flight Combat Rudder Pedals 171 Manufacturer= Saitek 171 Vendor=06A3, Product=0764 (Version 2.1) 171 Serial Number= 171 ------------------------------------------------------------------- 218 LogOptions=00000000 00000001 218 ------------------------------------------------------------------- 218 ------ Setting the hooks and direct calls into the simulator ------ 218 --- CONTROLS timer memory location obtained ok 218 --- SIM1 Frictions access gained 218 --- FS Controls Table located ok 218 --- Installed Mouse Macro hooks ok. 218 --- Wind smoothing fix is fully installed 218 --- G3D.DLL fix attempt installed ok 218 --- All links checked okay 218 ------------------------------------------------------------------- 218 SimConnect_Open succeeded: waiting to check version okay 218 Trying to use SimConnect Acc/SP2 Oct07 1076 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1076 Initialising SimConnect data requests now 1076 FSUIPC Menu entry added 1092 X:\Users\John Croft\Documents\Flight Simulator X Files\Default Cessna C172.FLT 1092 Z:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 27628 System time = 26/02/2016 12:37:32, Simulator time = 12:37:07 (18:37Z) 27628 Aircraft="Cessna Skyhawk 172SP Paint1" 28626 Starting everything now ... 28657 ASN active function link set 28657 Ready for ASN WX radar 29968 Advanced Weather Interface Enabled 61729 Z:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR 74724 Aircraft="Boeing 737-824NGX Continental Airlines Winglets" 176671 Sim stopped: average frame rate for last 102 secs = 61.6 fps 200102 System time = 26/02/2016 12:40:25, Simulator time = 12:38:59 (18:38Z) 200102 *** FSUIPC log file being closed Minimum frame rate was 29.7 fps, Maximum was 96.1 fps Minimum available memory recorded was 1176Mb Average frame rate for running time of 113 secs = 64.4 fps G3D fix: Passes 16148, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 56 Allocs, 56 Freed ********* FSUIPC Log file closed ***********

It would appear that they still seem to be there, I will post the contents of the file below. But I am loading the same aircraft and livery that I always use. There is only one model/livery of the PMDG 737 that I use, and it is the one that I set up the buttons on. I also just tried it on the PMDG 777-200 that I always use and they don't work there either. Have I done something to screw myself up here? [General] History=MVS8O0W8X4A3FT5F85ZK9 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 SimConnectStallTime=1 UpdatedByVersion=4949 InitDelayDevicesToo=No NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes AssignJoystickIDs=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No AxesWrongRange=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes OOMcheck=Yes OOMcheckInterval=10 CustomWeatherModify=No LuaRerunDelay=66 Console=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [JoyNames] AutoAssignLetters=Yes 2=Joystick - HOTAS Warthog 2.GUID={BDF22170-94E2-11E5-8001-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={BDF26F90-94E2-11E5-8002-444553540000} A=F16 MFD 1 B=F16 MFD 2 C=Joystick - HOTAS Warthog D=Throttle - HOTAS Warthog E=Saitek Pro Flight Combat Rudder Pedals 1=F16 MFD 2 1.GUID={F1D2D720-94E0-11E5-8002-444553540000} 4=Saitek Pro Flight Combat Rudder Pedals 4.GUID={F0B2D640-94E2-11E5-8001-444553540000} 0=F16 MFD 1 0.GUID={F1D2B010-94E0-11E5-8001-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=EX,256,F,66387,0,0,0 3=EY,256,F,66388,0,0,0 4=ER,256,F,65764,0,0,0 [Buttons] PollInterval=25 ButtonRepeat=20,10 1=PC,14,C65759,0 2=PC,16,C65758,0 3=PC,18,C65570,0 4=RC,36,C65615,0 5=RC,32,C65607,0 [LuaFiles] 1=Aerosoft_F14AB [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [Sounds] Path=Z:\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek High Definition Audio) Device3=Speakers (Corsair HS1 USB Headset) Device4=HF289H-0 (NVIDIA High Definition Audio) Device5=Realtek Digital Output(Optical) (Realtek High Definition Audio) Device6=iH282-C (NVIDIA High Definition Audio) Device7=Realtek Digital Output (Realtek High Definition Audio) [Monitor] Display=4 Monitor0=0,024C,4,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [Profile.737-800NGX WL] 1=Boeing 737-824NGX Continental Airlines Winglets [Axes.737-800NGX WL] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Window.VAFS Message:] Docked=262, 2775, 3545, 1010 [Buttons.737-800NGX WL] 0=PD,30,K113,11 1=PD,17,K112,11 2=PD,31,K115,11 3=PD,18,K114,11 4=PB,1,K70,10 5=PB,2,K82,9 6=PB,6,K71,11 7=PB,0,K90,8 8=PB,4,K75,8 9=PB,19,K86,10 10=PB,17,K72,10 11=PB,18,K78,10 12=PB,16,K79,10 13=PB,15,K65,10 14=PB,3,K90,10 15=PB,5,K85,8 16=RA,21,K116,10 17=RA,20,K116,9 18=RA,27,K117,10 19=RA,26,K117,9 20=RB,21,K118,10 21=RB,20,K118,9 22=RB,23,K119,10 23=RB,22,K119,9 24=RB,25,K120,10 25=RB,24,K120,9 26=PD,25,K68,9 27=PD,20,K70,9 28=PB,27,K121,10 29=PB,26,K121,9 30=PA,4,K72,9 31=PA,2,K84,10 32=PA,1,K76,11 33=PA,0,K76,10 34=PB,9,K66,9 35=RA,24,K122,9 36=RA,25,K122,10 [Profile.E175] 1=Embraer 175 United Express Post-Merger [Axes.E175] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.Leodardo Maddog 2008] 1=TWA Spirit of Long Beach [Axes.Leodardo Maddog 2008] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.ERJ145XR] 1=ERJ145LR - United Express [Axes.ERJ145XR] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.Majestic Q400] 1=MJC8Q400_CJC [Axes.Majestic Q400] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=DS,256,F,66382,0,0,0 5=EX,256,F,66387,0,0,0 6=EY,256,F,66388,0,0,0 7=ER,256,F,65764,0,0,0 [Profile.737-900NGX WL] 1=Boeing 737-924NGX Continental Airlines Winglets [Buttons.737-900NGX WL] 0=PD,30,K113,11 1=PD,17,K112,11 2=PD,31,K115,11 3=PD,18,K114,11 4=PB,1,K70,10 5=PB,2,K82,9 6=PB,6,K71,11 7=PB,0,K90,8 8=PB,4,K75,8 9=PB,19,K86,10 10=PB,17,K72,10 11=PB,18,K78,10 12=PB,16,K79,10 13=PB,15,K65,10 14=PB,3,K90,10 15=PB,5,K85,8 16=RA,21,K116,10 17=RA,20,K116,9 18=RA,27,K117,10 19=RA,26,K117,9 20=RB,21,K118,10 21=RB,20,K118,9 22=RB,23,K119,10 23=RB,22,K119,9 24=RB,25,K120,10 25=RB,24,K120,9 26=PD,25,K68,9 27=PD,20,K70,9 28=PB,27,K121,10 29=PB,26,K121,9 30=PA,4,K72,9 31=PA,2,K84,10 32=PA,1,K76,11 33=PA,0,K76,10 34=PB,9,K66,9 35=RA,24,K122,9 36=RA,25,K122,10 [Axes.737-900NGX WL] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.777-200LR] 1=PMDG 777-224LR Continental Airlines (Fictional) [Buttons.777-200LR] 0=PD,30,K113,11 1=PD,17,K112,11 2=PD,31,K115,11 3=PD,18,K114,11 4=PB,1,K70,10 5=PB,2,K82,9 6=PB,6,K71,11 7=PB,0,K90,8 8=PB,4,K75,8 9=PB,19,K86,10 10=PB,17,K72,10 11=PB,18,K78,10 12=PB,16,K79,10 13=PB,15,K65,10 14=PB,3,K90,10 15=PB,5,K85,8 16=RA,21,K116,10 17=RA,20,K116,9 18=RA,27,K117,10 19=RA,26,K117,9 20=RB,21,K118,10 21=RB,20,K118,9 22=RB,23,K119,10 23=RB,22,K119,9 24=RB,25,K120,10 25=RB,24,K120,9 26=PD,25,K68,9 27=PD,20,K70,9 28=PB,27,K121,10 29=PB,26,K121,9 30=PA,4,K72,9 31=PA,2,K84,10 32=PA,1,K76,11 33=PA,0,K76,10 34=PB,9,K66,9 35=RA,24,K122,9 36=RA,25,K122,10 [Axes.777-200LR] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.CS 757-300] 1=Captain Sim 757-300 FSX 2 [Axes.CS 757-300] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.Maddog CAL] 1=Continental [Axes.Maddog CAL] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 [Profile.Carenado F33 Bonanza] 1=BONANZA F33A BLUERED [Axes.Carenado F33 Bonanza] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66421,0,0,0 3=DR,256,F,66420,0,0,0 4=DS,256,F,66422,0,0,0 5=EX,256,F,66387,0,0,0 6=EY,256,F,66388,0,0,0 7=ER,256,F,65764,0,0,0

Pete, I have all of my PMDG aircraft set up with a ton of key commands, and this morning I seem to have lost all the profile specific data. My "General assignments" still appear to work, but none of the profile specific buttons work, and when I go into the FSUPIC control panel and hit one of them they don't show what I had previously assigned to them. FWIW, earlier this morning I set up the axis controls on a Carenado Bonanza, and when I ticked the profile specific box before I started it asked me if I wanted to save changes before I started, and I selected yes. Any ideas? I would rather not have to set them all up again. I'm using ver 4.949 with FSX Accel boxed version, Windows 7 64bit. Thanks john croft

ACtually every time I open the CP the speering mode has reverted to Mouse only. I select Spoiler axis each time and reload the aircraft, but no joy.

Thanks Stephan. I have mine set up exactly as you do, and mine doesn't work. I am using 1.014, and everything worked fine before this update. Is the 1.016 update the Pro model? I was under the impression that 1.014 was the latest version of the aircraft. This is driving me nuts :)

Pete, the majestic Q400 uses the spoiler axis to control the tiller. That is how they designed it to work. But they are telling me that the spoiler axis should never be negative. If this is wrong I will tell them that. I'm not saying this is an FSUPIC issue, I am just trying to figure out how to make it work. So my question to you is, is there a way to make FSUPIC report this axis starting at 0 and going to 65000 or whatever? If not I will tell them that and see what other ideas they have. Thanks.

Hi Pete. I have something that I'm not really sure what the issue is. In the Majestic Q400 I can't get the tiller to work after they updated to their latest version. I use a Thrustmaster HOTAS Warthog, and I have the grey throttle friction control assigned to the spoilers, with it being aircraft specific. This is the only plane I have this control set up for. In FSUPIC this axis reports values from -16384 to 16383, with 0 obviously being centered. Majestic says that the spoiler control should never have a negative value. In their control panel program however, the axis shows values from 0-65536. Either way, I can't get it to control the tiller. Is there a way in FSUPIC that I can give this axis values from 0 to whatever instead of what it naturally reports? I hope this made sense...:) Thanks john croft

Maybe I will give ASN a try once I break down and decide to spend some more money..:) Thanks again.

So would it be better to set the lower number to 2 or 4 instead of how I have it now, with the top number being 2? I know that FSUPIC won't kill all the wind shifts, I was just trying to get it to settle it down a little more than it currently is. Thanks. john

Bump for Pete.

Hi Pete. I hate to ask you this, but especially lately with the crazy upper level winds I have been having problems with REX Exxential Plus causing huge sudden wind shifts, both in velocity and direction. This causes either an overspeed or a severe underspeed. In my FDUPIC I have "Smooth wind changes near aircraft" selected with a value of 2, and the number below that is 0. Also checked is "Smooth only when airborne". Those are the only things I have checked on the Winds tab. Is there something else that I need to select to have this not be at least as much of an issue? Thanks in advance! john croft