magnusl Posted January 7, 2016 Report Posted January 7, 2016 Hello! I have some trouble using the FSUIPC GUI to edit my button settings. I get the message "This has multiple actions already! Please edit in FSUIPC.ini" when the button, in this case A,11 is pressed/unpressed. From the start I assigned a lot of buttons and practically it works in the simulator, but I just cannot edit the buttons anymore in the GUI. Every button has multiple assignments somehow and I can't figure out why. I have removed all assignments and started from scratch, with only one button, but I get the same error. My setup is Windows 10 and P3D with latest(?) FSUIPC (UpdatedByVersion=4949) and I have restarted P3D, Windows a few times. My entire [buttons] section looks like this: [buttons] PollInterval=20 ButtonRepeat=20,10 IgnoreThese=A.30, A.31, A.22, A.23, A.24, A.25 1=PA,11,C65841,0 2=UA,11,C65836,0 And [JoyNames] section contains duplicate ID:s but when I remove 0,1,2 they appear again automagically when I start P3D/FSUIPC, so I suppose it is correct. [JoyNames] AutoAssignLetters=No 2=CH PRO PEDALS USB 2.GUID={0E785AE0-B0A1-11E5-8004-444553540000} 0=Saitek Pro Flight Yoke 0.GUID={0E6BD7C0-B0A1-11E5-8001-444553540000} 1=BU0836X Interface 1.GUID={0E7833D0-B0A1-11E5-8003-444553540000} A=BU0836X Interface A.GUID={0E7833D0-B0A1-11E5-8003-444553540000} B=CH PRO PEDALS USB B.GUID={0E785AE0-B0A1-11E5-8004-444553540000} C=Saitek Pro Flight Yoke C.GUID={0E6BD7C0-B0A1-11E5-8001-44455354000} Is there any obvious error with my settings which you can see? Kind regards Magnus
Pete Dowson Posted January 7, 2016 Report Posted January 7, 2016 Is there any obvious error with my settings which you can see? Please post the whole of the INI file. And [JoyNames] section contains duplicate ID:s but when I remove 0,1,2 they appear again automagically when I start P3D/FSUIPC, so I suppose it is correct. Please refer to the documentation where it is clearly explained that the whole purpose of that section is to relate the Windows joystick IDs (0, 1, 2 etc) to the letters you are aassigning. without those equivalent entries how would one be tied to the other? Don't delete either or the whole point of the lettering could be lost. Pete
magnusl Posted January 8, 2016 Author Report Posted January 8, 2016 Here is the entire INI-file attached. Yes, I just thought that the numbers are not needed anymore if I use letters - and each letter is still referencing/tied to an unique GUID - so it made some sense to me to at least give it a try :-) Thanks Magnus [General] UpdatedByVersion=4949 History=P30U161GJ9QGR7P88MEZK 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=Yes CloudIcing=Yes 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=Yes 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 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No OOMcheck=Yes OOMcheckInterval=10 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No FSVersionUsed="Lockheed MartinÆ Prepar3DÆ v3",3.1.3.1 SimConnectUsed=3.1.0.0 [JoyNames] AutoAssignLetters=No A=BU0836X Interface A.GUID={0E7833D0-B0A1-11E5-8003-444553540000} B=CH PRO PEDALS USB B.GUID={0E785AE0-B0A1-11E5-8004-444553540000} C=Saitek Pro Flight Yoke C.GUID={0E6BD7C0-B0A1-11E5-8001-444553540000} 0=Saitek Pro Flight Yoke 0.GUID={0E6BD7C0-B0A1-11E5-8001-444553540000} 1=BU0836X Interface 1.GUID={0E7833D0-B0A1-11E5-8003-444553540000} 2=CH PRO PEDALS USB 2.GUID={0E785AE0-B0A1-11E5-8004-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=CX,256,D,1,0,0,0 1=CY,256,D,2,0,0,0 2=CZ,256,D,4,0,0,0 3=CR,256,D,6,0,0,0 4=CU,256,D,5,0,0,0 5=BX,256,D,7,0,0,0 6=BY,256,D,8,0,0,0 [buttons] PollInterval=20 ButtonRepeat=20,10 IgnoreThese=A.30, A.31, A.22, A.23, A.24, A.25 1=PA,11,C65841,0 2=UA,11,C65836,0 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM0 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=Yes [sounds] Path=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sound\ Device1=Prim‰r ljuddrivrutin Device2=Hˆgtalare (Realtek High Definition Audio) Device3=Realtek Digital Output(Optical) (Realtek High Definition Audio) Device4=Realtek Digital Output (Realtek High Definition Audio) Device5=SAMSUNG-0 (NVIDIA High Definition Audio) [LuaFiles] 1=ipcReady [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=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16380,727,878,16380/8 Elevator=-16380,0,512,16380/8 LeftBrake=3745,12882/24 RightBrake=3741,12769/24 SlopeLeftBrake=-5 SlopeRightBrake=-5 Rudder=-16380,-512,512,16380
Pete Dowson Posted January 8, 2016 Report Posted January 8, 2016 Yes, I just thought that the numbers are not needed anymore if I use letters - and each letter is still referencing/tied to an unique GUID But FSUIPC uses the joystick ID numbers, 0-15, as used in the original Windows joystick API, and needs the number lines to relate the number to the GUID and Name as well as the Letters so it can understand the lettered assignments. Anyway it actually does no harm, as you can see, FSUIPC re-constructs those from the registry next time. It might only go wrong if the registry was not complete with the IDs, and seems to happen more often now with Win8 and Win10 and Saitek drivers. On the original problem: I get the message "This has multiple actions already! Please edit in FSUIPC.ini" when the button, in this case A,11 is pressed/unpressed. I found it. It is actually a very very old bug, and I'm surprised it hasn't occurred before. It was intriduced when I added the "IgnoreThese" facility (in 2008), as in your line IgnoreThese=A.30, A.31, A.22, A.23, A.24, A.25 The code I inserted to cope with that re-uses the counter used to keep track of how many button assignments there are. This makes the Buttons Tab scan spurious entries in the table and get matches where none exist. Without the IgnoreThese line it works fine. I'll make an interim update with this fixed today -- 4.949a. Look out for it in the Download Links subforum above later. It'll be just a replacement DLL. Thanks for the report! Pete 1
magnusl Posted January 8, 2016 Author Report Posted January 8, 2016 Ah! Thanks a lot for looking into this and for the quick solution. Actually, I have been using FSUIPC3 and FS2004 for a few years and that line is from there. I have some rotary encoders I manage via a LUA script instead. Will look out for the update. No hurry, it is of course not a "deal-breaker". Thanks again! Magnus
Pete Dowson Posted January 8, 2016 Report Posted January 8, 2016 Will look out for the update. No hurry, it is of course not a "deal-breaker". Update is up there now. Pete
magnusl Posted January 9, 2016 Author Report Posted January 9, 2016 I can confirm it is working as intended now. Thanks a lot!
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