Detlef_747 Posted October 17, 2019 Report Posted October 17, 2019 Hi everybody, I am trying to assign Joystick Buttons to Elevator trim down and elivator trim up. And trim down works but trim up causes P3D to cycle through the views. I tried to delete the Control assignment in P3D that I had set earlier in the P3D menu but somehow the sim still uses that old button assignment and ignores the FSUIPC button assigment. Do you know how I can delete all Joystick button definitions from P3D? I want to program them using FSUIPC. Thank you Detlef
Primesim Posted October 17, 2019 Report Posted October 17, 2019 So I have had this happen in the past, sometimes you have to delete the control in the P3D Controls menu multiple times for it to 'stick', also when deleting the control, make sure your device is selected in the drop down menu. If you have more devices, like a joystick, throttle quadrant, and rudder pedals, P3D treats them all separate and assigns the same controls to each device, so even if you delete "Change View" with your throttle quadrant selected in the drop-down menu, it will still retain the "Change View" assignment for any other devices you have connected (like a joystick for example).
aua668 Posted October 18, 2019 Report Posted October 18, 2019 Hi, If you use only FSUIPC for your assignments, you could eliminate all assignments of the P3D control configuration file with an editor and make it afterwards read-only. Then no automatically added assignments to axis, buttons, etc. will happen anymore. I am currently not at my PC but I think it should be here: %APPDATA%\Lockheed Martin\Prepar3D\Controls\Standard.xml Rgds Reinhard
DaveG Posted October 18, 2019 Report Posted October 18, 2019 I just disable controllers entirely in p3d (there's a checkbox for it) and assign everything via fsuipc.
John Dowson Posted October 18, 2019 Report Posted October 18, 2019 28 minutes ago, DaveG said: I just disable controllers entirely in p3d (there's a checkbox for it) and assign everything via fsuipc. This is the recommended method.
Detlef_747 Posted October 19, 2019 Author Report Posted October 19, 2019 Hello everybody, I got it solved following your advice, so thank you. I changed every control within P3D that was assigned to a button to the same button, thus effectively removing all button assignments. I saved that configuration as buttons_deleted in case I need it at some time. Then I unchecked controllers in the P3D settings. Still after that I had trouble with elevator up button assignments. My impression is for elevator trim up I may have used the wrong control, since the aircraft control surface change from the trim fought against the control stick. In any case, I assigned the buttons to Pos1(home) and End keys now. That worked. And I did a lot of other button programming in FSUIPC which also worked. Oh and also I reassigned all axis to FSUIPC. I have a Logitech joystick and CH products throttle control and rudders. Again, thanks for your help Detlef
Thomas Richter Posted October 19, 2019 Report Posted October 19, 2019 Hi, best is to attach your FSUIPC INI file that makes it easier to actually see what you have assigned. Thomas
Detlef_747 Posted October 20, 2019 Author Report Posted October 20, 2019 Hi Thomas, yes I see. Thank you and here it comes. Detlef [General] UpdatedByVersion=5152 History=K8WWIYSSL0KJVKHEHSL64 InitDelayDevicesToo=No PMDG737offsets=Auto PMDG747offsets=Auto PMDG777offsets=Auto Annotate=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 RestoreSimcWindows=No FixMachSpeedBug=No AutoScanDevices=Yes 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 TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No WideLuaGlobals=Yes TextFileMaxRead=4095 TextFileNumbers=Yes TextFilePhonetics=Yes AxesWrongRange=No TCASid=Flight TCASrange=40,3 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No ThreadAffinityMask=x0 LuaAffinityMask=x0 InitDelay=0 GetNearestAirports=Yes LogOptionProtect=Yes TimeForLuaClosing=2 WeatherReadFactor=2 WeatherRewriteSeconds=1 TrafficStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 ComReadLoopTime=20 ControlsListBuild=30293 Console=No LogLua=Yes FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.12.30293 SimConnectUsed=4.5.0.0 [Traffic Limiter] AirportPreference=50 PlannedAirportsPreference=50 GroundPreference=50 NearerPreference=50 TargetFrameRate=0 TrafficLimit=0 [JoyNames] AutoAssignLetters=No 1=Logitech Attack 3 1.GUID={52394020-B5E6-11E9-8003-444553540000} 0=CH Pro Pedals USB 0.GUID={5238F200-B5E6-11E9-8002-444553540000} 2=CH Pro Throttle USB 2.GUID={5239B550-B5E6-11E9-8007-444553540000} [JoystickCalibration] RudderBlendLowest=1 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 Rudder=-16380,-512,512,16380 Throttle=-16383,16380 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 1=0Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 2=0Z,256,D,3,0,0,0 -{ DIRECT: Rudder }- 3=1X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 4=1Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 5=2X,256 6=2X,B,128,16255,65864,0 -{ Entering=LANDING_LIGHT_LEFT }- 7=2Z,256,D,4,0,0,0 -{ DIRECT: Throttle }- [Buttons] PollInterval=25 ButtonRepeat=20,10 1=P2,10,CL2:S,0 -{LuaSet RealSwitches (Flag 0)}- 2=P2,9,C1084,0 -{LuaKillAll}- 3=P2,0,CL1:D,0 -{LuaDebug ipcDebug}- 6=P1,10,CL6:R,0 -{Lua display_fuel}- 7=P1,9,C66708,0 -{EXTINGUISH_ENGINE_FIRE}- 8=P1,3,C65681,0 -{VIEW_FORWARD_LEFT}- 9=U1,3,C65674,0 -{VIEW_FORWARD}- 10=P1,4,C65675,0 -{VIEW_FORWARD_RIGHT}- 11=U1,4,C65674,0 -{VIEW_FORWARD}- 12=R1,2,K36,8 -{Key press: Home}- 13=R1,1,K35,8 -{Key press: End}- 14=P2,13,K83,8 -{Key press: S}- 15=P2,15,K83,9 -{Key press: shft+S}- 16=P2,14,C66153,0 -{NEXT_SUB_VIEW}- 17=P2,12,C66154,0 -{PREV_SUB_VIEW}- 18=P2,7,C65827,0 -{NEXT_VIEW}- 19=P2,1,C65589,0 -{SPOILERS_TOGGLE}- 20=R2,2,K113,8 -{Key press: F2}- 22=P2,3,K112,8 -{Key press: F1}- 23=R2,36,K37,9 -{Key press: shft+Left}- 25=R2,32,K39,9 -{Key press: shft+Right}- 26=R2,38,K38,9 -{Key press: shft+Up}- 27=R2,34,K40,9 -{Key press: shft+Down}- 28=R1,0,K75,11 -{Key press: ctl+shft+K}- [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [WideServer] WideFSenabled=No AdvertiseService=1 Port=8002 Port2=9002 [Sounds] Path=C:\P3D\Sound\ Device1=Primärer Soundtreiber Device2=Lautsprecher (High Definition Audio Device) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=Remoteaudio [Auto] [LuaFiles] 1=ipcDebug 2=RealSwitches 3=textmenu 4=tevent 5=display_ap 6=display_fuel [Keys] 1=76,8,L2:R,0 -{L: Press=Lua RealSwitches }- 2=190,8,1084,0 -{.>key: Press=LuaKillAll }- 3=86,8,L5:R,0 -{V: Press=Lua display_ap }-
Thomas Richter Posted October 20, 2019 Report Posted October 20, 2019 Hi, I actually don't see TRIM UP/DN assignments? Easiest way is to assign Buttons or Keys direct to controls and not to assigned keys from FS. It looks like this for example for Elevator TRIM with Joystick button. Same you would do for key presses on Keys Presses tab Thomas
Detlef_747 Posted October 31, 2019 Author Report Posted October 31, 2019 On 10/20/2019 at 8:57 PM, Thomas Richter said: Easiest way is to assign Buttons or Keys direct to controls and not to assigned keys from FS. It looks like this for example for Elevator TRIM with Joystick button. Same you would do for key presses on Keys Presses tab Hello Thomas, thank you for your reply. I have not yet come arround to try your suggestion but will do. Thank you Detlef
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