smoore Posted September 28, 2009 Report Share Posted September 28, 2009 I recently purchased a Saitek Pro Flight multi panel and it doesn't work properly with FSUIPC 4.53 (fully licensed). The autopilot button and trim wheel do not work properly when FSUIPC is running. When I remove the FSUIPC4.dll file from the FSX modules folder and run the game without FSUIPC, the multipanel works as it should. Just wondering if anyone has had a similar problem and if there is a fix for this (haven't had any help from Saitek support yet). The multipanel doesn't actually show up as a joystick in FSX; buttons can't be assigned. If there's no fix for this problem, I'll have to get rid of the multipanel. Definitely can't go without the FSUIPC program. I am running Windows 7 64 bit, but I don't think this should be an issue. Thanks for any help Steve Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 28, 2009 Report Share Posted September 28, 2009 I recently purchased a Saitek Pro Flight multi panel and it doesn't work properly with FSUIPC 4.53 (fully licensed). The autopilot button and trim wheel do not work properly when FSUIPC is running. FSUIPC doesn't do anything unless you or an application program has asked it to. It most certainly doesn't touch either autopilot or trim. It sounds like you've made some settings or changes which you've now forgotten about, or you are using an add-on which is influencing those things through FSUIPC's facilities. If you don't know what you've done with FSUIPC's facilities, first try removing your FSUIPC4.INI file before starting FSX -- save it somewhere separately. That will render all of its actions to default -- i.e. nothing. If that doesn't fix it, you need to start eliminating add-ons using FSUIPC one by one. You could also try to find out exactly what is happening by using FSUIPC4's logging facilities. Enable the event logging to start with, to see what controls are being sent. Regards Pete Link to comment Share on other sites More sharing options...
smoore Posted September 28, 2009 Author Report Share Posted September 28, 2009 I just reinstalled FSX two weeks ago and have no add-ons installed besides FSUIPC. I will try removing the FSUIPC.ini file when I get home from work and using the logging facilities if necessary. Saitek support also recommended removing the ini file this morning. Thanks for your help, Steve Link to comment Share on other sites More sharing options...
smoore Posted September 28, 2009 Author Report Share Posted September 28, 2009 removing the FSUIPC.ini file did not help. This what the event logger looks like when I push some of the buttons on the Saitek multipanel. ********* FSUIPC4, Version 4.537 by Pete Dowson ********* User Name="Steven Moore" [Continuation log requested by user] Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed 58344 System time = 28/09/2009 19:44:29, Simulator time = 12:20:47 (11:20Z) 58344 LogOptions changed, now 20000000 00000001 59514 Advanced Weather Interface Enabled 62634 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 62666 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 62681 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 62712 *** EVENT: Cntrl= 66416 (0x00010370), Param= 90 (0x0000005a) PAN_VIEW 62728 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 64085 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 64085 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 66659 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 66675 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON 68048 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 68048 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 69654 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 69670 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 70731 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 70746 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 71932 *** EVENT: Cntrl= 66416 (0x00010370), Param= -1 (0xffffffff) PAN_VIEW 75161 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 75161 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON 76409 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 76425 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 78359 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 82540 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 82540 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON 84755 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 88281 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 90465 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 93320 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 93320 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON 94615 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 94630 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 96627 *** EVENT: Cntrl= 65729 (0x000100c1), Param= 0 (0x00000000) AP_NAV1_HOLD 96643 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON 98031 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 98031 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 100808 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 100808 *** EVENT: Cntrl= 66106 (0x0001023a), Param= 0 (0x00000000) AP_PANEL_HEADING_ON 101853 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 101869 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 103429 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 103444 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 105067 *** EVENT: Cntrl= 66108 (0x0001023c), Param= 1 (0x00000001) AP_PANEL_HEADING_SET 105878 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 105893 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER 112991 Sim stopped: average frame rate for last 53 secs = 101.9 fps 118842 Weather Mode now = Theme 118842 \\HOMEPC\Users\Steve\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 121759 *** EVENT: Cntrl= 65794 (0x00010102), Param= 0 (0x00000000) PAUSE_ON I don't know what everything means, but it looks like when the AP_MASTER is pressed it is not switching on and off. Would it help if I uninstalled FSUIPC and tried reinstalling. Edit: just tried it with the console log and every time I press the buttons on the multipanel it registers twice in FSUIPC. Happens for all buttons on the panel. Thanks for your help Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2009 Report Share Posted September 29, 2009 This what the event logger looks like when I push some of the buttons on the Saitek multipanel. Er .. which buttons? Are they the correct events? Sorry, you evidently misunderstood me. It seems likely that the Saitek device is sending spurious button presses. You need to know which button you pressed and link it to the events FSUIPC is logging so yuou can tell which ones should be occurring and which ones not. I don't know what everything means It's not hard. In a line like this: 105893 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER the number on the left is the time since FSUIPC started, in milliseconds, -- so 105.893 in this example. EVENT is a lable meaning this line is logging an Event. The Ctrl=65580 is telling you the internal control number (used also by external programs) The (0x0001002c) part is simply the control number in hexadecimal The Param part gives the parameter sent with the event -- not relevant in this case. For Axis events the parameter would be the axis value, eg throttle setting. The name "AP_MASTER" is the internal name for the Event -- in this case the autopilot master toggle. ... but it looks like when the AP_MASTER is pressed it is not switching on and off. On the contrary, you seem to has so many AP_MASTER events occurring that you are probably switching the autopilot on and off a lot. The problem looks like your button is repeating so it always sets it on and off. Can you try pressing one button once and looking then to see what you get? Just playing with the buttons won't really help. Would it help if I uninstalled FSUIPC and tried reinstalling. Not really. FSUIPC doesn't change. Edit: just tried it with the console log and every time I press the buttons on the multipanel it registers twice in FSUIPC. Happens for all buttons on the panel. So they are all duplicated. It sounds like you either have the same buttons assigned to do the same things in two places, or the same device is being see twice in FS and it is assigning them automatically, twice. Check the FS assignments. See how many devices it thinks there are. You said in your first report here that "the multipanel doesn't actually show up as a joystick in FSX; buttons can't be assigned." That seems quite hard to understand or believe. If it isn't a device as far as FSX is concerned, what is actually sending those events to FS? Are you sure that part is not duplicated, whatever it is? Doesn't FSUIPC see it as a device either? Isn't it listed in FSUIPC's [JoyNames] section, in the FSUIPC4.INI file? Regards Pete Link to comment Share on other sites More sharing options...
smoore Posted September 29, 2009 Author Report Share Posted September 29, 2009 You are right. I am getting the autopilot switching on and off each time I press the button. This also occurs with the other buttons on the panel as well. Neither FSX or FSUIPC recognizes the Saitek panel as a joystick. Odd thing is that the button presses on the panel still show up in the event log. Here is the list of joysticks in the config file: [JoyNames] AutoAssignLetters=No 0=USB Gaming Keyboard Pro 1=Saitek Pro Flight Rudder Pedals 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Quadrant 4=Digital Switch 2040 5=DTA Rotary Encoder [buttons] ButtonRepeat=20,10 I have unassigned all joystick commands in FSUIPC but still get the same problem. It looks like a Saitek problem that I will have to figure out with their support (maybe faulty panel). Thanks for your help..I'm starting to learn more about your program which is a good thing Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2009 Report Share Posted September 29, 2009 Neither FSX or FSUIPC recognizes the Saitek panel as a joystick. So, there must be a driver being pre-loaded, one which sends these commands to FS. Maybe it uses SimConnect direct? Does it get loaded by the DLL.XML or EXE.XML files? Maybe you could get a Simconnect log (see the FSX Help announcement for instructions for that). Of course it could simply be sending keystrokes. You could log Buttons and Keys in FSUIPC logging to find out. If it is basically a keyboard emulator it may be getting repeats activated. Odd thing is that the button presses on the panel still show up in the event log. Not odd -- FSUIPC can log events being received by FSX no matter where they come from. Here is the list of joysticks in the config file:[JoyNames] AutoAssignLetters=No 0=USB Gaming Keyboard Pro 1=Saitek Pro Flight Rudder Pedals 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Quadrant 4=Digital Switch 2040 5=DTA Rotary Encoder Phew, that's quite a list. Are they all actively connected? Could any of those be interfering? I have unassigned all joystick commands in FSUIPC but still get the same problem. Er, hang on. I thought you'd removed the INI file in any case? If you are using the default INI file there shouldn't be any "joystick commands" in there in the first place. Maybe you'd better show me the entire INI file -- I am now suspecting you have things assigned you've forgotten about? Regards Pete Link to comment Share on other sites More sharing options...
smoore Posted September 29, 2009 Author Report Share Posted September 29, 2009 here is the ini file [General] UpdatedByVersion=4537 History=FRSHOJJD5RM8DAKYG2WHM MouseWheelTrim=No MouseWheelTrimSpeed=1 FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-1 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 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 [JoyNames] AutoAssignLetters=No 0=USB Gaming Keyboard Pro 1=Saitek Pro Flight Rudder Pedals 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Quadrant 4=Digital Switch 2040 5=DTA Rotary Encoder [buttons] ButtonRepeat=20,10 [AutoSave] AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 The panel gets loaded by EXE.XML files. Not sure why it loads for FS9 as well. - Saitek Panel(s) Plugin for FSX False C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe -run - Saitek Panel(s) Plugin for FSX False C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanelsFS9.exe -run Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2009 Report Share Posted September 29, 2009 here is the ini file Okay, that looks fine. But: The panel gets loaded by EXE.XML files. Not sure why it loads for FS9 as well. is a bit of a worry. Having two programs sending what presumably is the same stuff to FSX doesn't seem correct, and may well be the cause of your double button actions. Make a safe copy of your EXE.XML file and remove this part: Saitek Panel(s) Plugin for FSX False C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanelsFS9.exe -run so that only one driver loads. If that fixes it then tell Saitek they've got an installer problem which needs fixing. Regards Pete Link to comment Share on other sites More sharing options...
smoore Posted September 29, 2009 Author Report Share Posted September 29, 2009 You're right...looks like a problem with the installer. I disabled SaiPanelsFS9 in the Task Manager and the panel works properly now. I can't figure out a way to edit the EXE.XML file. Hopefully I don't have to disable this in task manager each time I play. Hopefully Saitek will fix this. Thanks for your help and the temporary fix. Regards, Steve Edit: figured it out. Just right click on the exe.xml file and go to edit. Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2009 Report Share Posted September 29, 2009 I can't figure out a way to edit the EXE.XML file. Just open it with Notepad or any ordinary text editor, and delete that section. Edit: figured it out. Just right click on the exe.xml file and go to edit. Yes. Regards Pete Link to comment Share on other sites More sharing options...
snyderdb Posted December 27, 2009 Report Share Posted December 27, 2009 Have the same issue. I am running Win 7 32 bit though. I will follow the advise in the thread to see if can come to the same resolution. I sent an e-mail to Saitek reporting this conflict. Sounds like a driver update is in order. Link to comment Share on other sites More sharing options...
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