FSUIPC freezes when menu is opened

[chevol]

I am running FSX with acceleration on Win7. So far all went well but all of a sudden, when I open the FSUIPC menu to set a button or calibrate an axis, FSUIPC freezes after a couple of minutes even if I do nothing while looking at the options. The only way to get out is to kill FSX through the task manager.

Luc

[Pete Dowson]

I am running FSX with acceleration on Win7. So far all went well but all of a sudden, when I open the FSUIPC menu to set a button or calibrate an axis, FSUIPC freezes after a couple of minutes even if I do nothing while looking at the options. The only way to get out is to kill FSX through the task manager.

If it only happens on buttons and axis assignments tabs it sounds like you have a rogue joystick driver feeding continuous signals and so not allowing the dialogue time to receive inputs. Check Windows game controllers in the control panel.

Regards

Pete

[Pete Dowson]

If it only happens on buttons and axis assignments tabs it sounds like you have a rogue joystick driver feeding continuous signals and so not allowing the dialogue time to receive inputs. Check Windows game controllers in the control panel.

I've added a new check in version 4.562, now available in the Updates Announcement. Please try it and let me know. Here's a description of the change:

An extra check has been incorporated into the Button scanning routines (used when in the FSUIPC options to assign buttons and switches). If any joystick device takes more than 100 mSecs to respond, FSUIPC stops polling it on the assumption that it is either faulty, or has a bad driver. The ban on that device stays operative for the rest of the FS session.

This is intended to prevent the odd hangs some folks get in the Buttons options which are thought to be due to rogue joystick drivers without connected joysticks. The timeout used (100 mSecs by default) can be changed via the parameter in the FSUIPC4.INI file called "JoystickTimeout". This has a minimum of 10 and a maximum of 5000 milliseconds.

If this does help, perhaps you'd be kind enough to try smaller or larger values for that parameter? 100 mSecs might be too large and still cause it to clog up, or it might be too small and have the effect of eliminating good devices (though I very much doubt that). If it doesn't seem to help initially, do please try smaller values in any case.

Oh, if this facility does help, I'd like to see the FSUIPC4.log file, please. It should log the responsible joystick number.

Thanks,

Pete

[chevol]

Thank you Peter, that was quick!

So I did update to vers 4.562, first attempt gave me more time to look at buttons options but everything still froze after, say 1.5 mn. I did modify joysticktimeout in the following way: 75, 50, then 125, 150 and did not notice any significant change but still got more than a minute to browse through the buttons options before it froze, which is better than last night.

Here is my log (I just deleted my name and email address which you can get if you wish, of course)

********* FSUIPC4, Version 4.562 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Luc xxxxxxx"

User Addr="chevolxxxxx"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

3338 System time = 07/01/2010 20:56:19

3338 FLT UNC path = "\\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\"

3338 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

3634 Assuming running on Vista or later in compatibility mode!

3634 LogOptions=00000000 00000001

3634 SimConnect_Open succeeded: waiting to check version okay

10483 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

10483 Initialising SimConnect data requests now

10483 FSUIPC Menu entry added

10576 \\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\MD11 GVA c & d.FLT

10576 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG_MD11F\MD-11F.AIR

35365 Aircraft="PMDG MD-11F GE TITAN N101TA"

35381 System time = 07/01/2010 20:56:51, Simulator time = 20:56:25 (19:56Z)

36504 Advanced Weather Interface Enabled

86705 Sim stopped: average frame rate for last 51 secs = 115.0 fps

to complete, some details on my set up: CH products, quadrant + yoke + pedals

Yesterday I did get a message from Win7 about possible problem with a device which might not be seen. I went into the control pannel and clicked the troubleshoot button. Now Win7 says everything is OK.

I did not load the CH device manager, just plugged in the devices which work very well with all aircrafts (so it seems)

I have additional progs: ASA, FSC, FSFK

Best regards,

Luc

[Pete Dowson]

So I did update to vers 4.562, first attempt gave me more time to look at buttons options but everything still froze after, say 1.5 mn. I did modify joysticktimeout in the following way: 75, 50, then 125, 150 and did not notice any significant change but still got more than a minute to browse through the buttons options before it froze, which is better than last night.

Actually the log proves that the timeout modification I made had no effect. If the problem is due to a strange joystick action the timeouts you tried evidently weren't short enough. You might need to try the minimum, 10 mSecs, but maybe that isn't enough.

I don't like this:

3634 Assuming running on Vista or later in compatibility mode!

Have you set FSX to run under win7 in compatibility mode? If so, why? I wouldn't recommend it at all. FSX suits Win7 exactly as a proper application, there's no need for any fiddles like that.

Yesterday I did get a message from Win7 about possible problem with a device which might not be seen. I went into the control pannel and clicked the troubleshoot button. Now Win7 says everything is OK.

Can you look at the thread "FSX Lockup on opening Buttons + Switches tab ", and try the Joyview program I attached there?

I did not load the CH device manager, just plugged in the devices which work very well with all aircrafts (so it seems)

If it isn't a rogue driver then something else is interacting with it somehow. could you test with no joystick devices, nothing plugged in? Also try with a different aircraft loaded first, a default one. This is just part of a process of elimination, because if it isn't a driver problem it is certainly something I've not seen before.

Regards

Pete

[chevol]

Good morning Peter,

Do you ever sleep ?

First test 8hZ

I set joysticktimeout to 10, result NO FREEZE! I went up and down the "control sent when button pressed" list several times without any prob. I managed tro set 2 buttons on my Quadrant but when I tried to set a 3rd one FSUIPC did not recognize it (nothing appeared in the PREES box when pushing the button) I tried other buttons, nothing but still no freeze.

Here is a copy of the log:

********* FSUIPC4, Version 4.562 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Luc xxxx"

User Addr="chevolxxxxx"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

671 System time = 08/01/2010 08:41:04

734 FLT UNC path = "\\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\"

734 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

1015 Assuming running on Vista or later in compatibility mode!

1030 LogOptions=00000000 00000001

1030 SimConnect_Open succeeded: waiting to check version okay

8206 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

8206 Initialising SimConnect data requests now

8206 FSUIPC Menu entry added

8315 \\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\MD11 GVA c & d.FLT

8315 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG_MD11F\MD-11F.AIR

28658 Joy 3 taking too long to respond (> 10 mSecs). Removed from scan

29313 Aircraft="PMDG MD-11F GE TITAN N101TA"

29329 System time = 08/01/2010 08:41:33, Simulator time = 08:41:13 (07:41Z)

29828 Advanced Weather Interface Enabled

74631 Sim stopped: average frame rate for last 46 secs = 110.0 fps

87860 Joy 5 taking too long to respond (> 10 mSecs). Removed from scan

87876 Joy 12 taking too long to respond (> 10 mSecs). Removed from scan

89046 Joy 11 taking too long to respond (> 10 mSecs). Removed from scan

89061 Joy 9 taking too long to respond (> 10 mSecs). Removed from scan

89295 Joy 10 taking too long to respond (> 10 mSecs). Removed from scan

89311 Joy 13 taking too long to respond (> 10 mSecs). Removed from scan

89545 Joy 7 taking too long to respond (> 10 mSecs). Removed from scan

89810 Joy 15 taking too long to respond (> 10 mSecs). Removed from scan

89826 Joy 8 taking too long to respond (> 10 mSecs). Removed from scan

90450 Joy 6 taking too long to respond (> 10 mSecs). Removed from scan

90684 Joy 4 taking too long to respond (> 10 mSecs). Removed from scan

114926 Joy 14 taking too long to respond (> 10 mSecs). Removed from scan

887116 Joy 1 taking too long to respond (> 10 mSecs). Removed from scan

947613 Joy 2 taking too long to respond (> 10 mSecs). Removed from scan

959251 Sim stopped: average frame rate for last 28 secs = 68.6 fps

1081025 Joy 0 taking too long to respond (> 10 mSecs). Removed from scan

1133644 Sim stopped: average frame rate for last 40 secs = 74.1 fps

Regarding the compatibility mode of FSX, I did not touch anything because I would'nt know where to look... can I check this somewhere?

Best regards,

Luc

[Pete Dowson]

I set joysticktimeout to 10, result NO FREEZE! I went up and down the "control sent when button pressed" list several times without any prob. I managed tro set 2 buttons on my Quadrant but when I tried to set a 3rd one FSUIPC did not recognize it (nothing appeared in the PREES box when pushing the button) I tried other buttons, nothing but still no freeze.

Well this proves that the problem is due to a rogue joystick driver, but also that 10 mSecs is probably too tight for your genuine joystick connections to respond.

The log shows what happened:

28658 Joy 3 taking too long to respond (> 10 mSecs). Removed from scan

...

87860 Joy 5 taking too long to respond (> 10 mSecs). Removed from scan

87876 Joy 12 taking too long to respond (> 10 mSecs). Removed from scan

89046 Joy 11 taking too long to respond (> 10 mSecs). Removed from scan

89061 Joy 9 taking too long to respond (> 10 mSecs). Removed from scan

89295 Joy 10 taking too long to respond (> 10 mSecs). Removed from scan

89311 Joy 13 taking too long to respond (> 10 mSecs). Removed from scan

89545 Joy 7 taking too long to respond (> 10 mSecs). Removed from scan

89810 Joy 15 taking too long to respond (> 10 mSecs). Removed from scan

89826 Joy 8 taking too long to respond (> 10 mSecs). Removed from scan

90450 Joy 6 taking too long to respond (> 10 mSecs). Removed from scan

90684 Joy 4 taking too long to respond (> 10 mSecs). Removed from scan

114926 Joy 14 taking too long to respond (> 10 mSecs). Removed from scan

887116 Joy 1 taking too long to respond (> 10 mSecs). Removed from scan

947613 Joy 2 taking too long to respond (> 10 mSecs). Removed from scan

1081025 Joy 0 taking too long to respond (> 10 mSecs). Removed from scan

Joystick #3 is favourite to be the rogue. But then every single possible joystick connection scanned by FSUIPC occasionally took longer than 10 mSecs. So that is obviously too tight a timeout. You'll have to gradually increase it. You have plenty of room as the tightest you tested before was 50. So try 25. Zero in by halves. If 25 is too tight 35. If too loose 15, etc. You should find some value which consistently cuts the bad one (or more than one?) out whilst letting the good ones work.

Anyway, as this does really prove you have some rogue joystick driver installed, you really need to eliminate it. When you have the timeout set correctly (let me know and I'll change the default), the Log will show you the joystick number responsible. Did you check Windows game controllers for an unknown and unwanted joystick driver? Did you run that Joyview program as I suggested?

Please check the [JoyNames] section of the FSUIPC4.INI file --show it to me, in fact, please -- this should list the Joysticks identified via DirectInput. Any others shouldn't be "real".

Incidentally:

74631 Sim stopped: average frame rate for last 46 secs = 110.0 fps

959251 Sim stopped: average frame rate for last 28 secs = 68.6 fps

1133644 Sim stopped: average frame rate for last 40 secs = 74.1 fps

With frame rates like those I'd recommend you use the FS frame rate limiter to limit it to say 30 or 35 fps. You'd get a moother ride. (This is nothing to do with the joystick scanning though).

Regarding the compatibility mode of FSX, I did not touch anything because I would'nt know where to look... can I check this somewhere?

You mean you didn't set FSX to run in compatibility mode yourself? It's right-click on the shortcut, Properties-Compatibility. Make sure none of the boxes are checked.

[LATER]

I'm making a revised version of FSUIPC4 which only operates that timeout when you are in the FSUIPC options I suspect that 10 mSecs would be okay, but in normal FS mode the time can probably be exceeded even for a good joystick because of FS loads -- if FS is running at over 100 fps it is taking the whole processor and could slow other things down. Look out for version 4.563 later today. However, please don't let this stop you doing that timeout test -- I do still need to know what value catches the bad and not the good. ;-)

Regards

Pete

[chevol]

Well this proves that the problem is due to a rogue joystick driver, but also that 10 mSecs is probably too tight for your genuine joystick connections to respond.

at 25 I got another freeze but at 15 no freeze... here is the log

********* FSUIPC4, Version 4.562 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Luc xxxxx"

User Addr="chevol"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

3478 System time = 08/01/2010 12:46:21

3478 FLT UNC path = "\\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\"

3478 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

3775 Assuming running on Vista or later in compatibility mode!

3775 LogOptions=00000000 00000001

3775 SimConnect_Open succeeded: waiting to check version okay

10904 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

10904 Initialising SimConnect data requests now

10904 FSUIPC Menu entry added

10998 \\LUC-HP\Users\Luc\Documents\Flight Simulator X Files\MD11 GVA c & d.FLT

10998 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG_MD11F\MD-11F.AIR

51948 Aircraft="PMDG MD-11F GE TITAN N101TA"

51964 System time = 08/01/2010 12:47:10, Simulator time = 12:46:29 (11:46Z)

52806 Advanced Weather Interface Enabled

87298 Sim stopped: average frame rate for last 36 secs = 89.0 fps

96081 Joy 11 taking too long to respond (> 15 mSecs). Removed from scan

140697 Joy 3 taking too long to respond (> 15 mSecs). Removed from scan

152319 Joy 15 taking too long to respond (> 15 mSecs). Removed from scan

153302 Joy 8 taking too long to respond (> 15 mSecs). Removed from scan

153333 Joy 14 taking too long to respond (> 15 mSecs). Removed from scan

153349 Joy 5 taking too long to respond (> 15 mSecs). Removed from scan

159776 Joy 13 taking too long to respond (> 15 mSecs). Removed from scan

159807 Joy 7 taking too long to respond (> 15 mSecs). Removed from scan

159823 Joy 6 taking too long to respond (> 15 mSecs). Removed from scan

160291 Joy 9 taking too long to respond (> 15 mSecs). Removed from scan

160759 Joy 4 taking too long to respond (> 15 mSecs). Removed from scan

160790 Joy 12 taking too long to respond (> 15 mSecs). Removed from scan

161757 Joy 10 taking too long to respond (> 15 mSecs). Removed from scan

643863 Sim stopped: average frame rate for last 33 secs = 43.8 fps

1317756 Sim stopped: average frame rate for last 199 secs = 51.3 fps

1325446 System time = 08/01/2010 13:08:23, Simulator time = 12:51:13 (11:51Z)

1325446 *** FSUIPC log file being closed

Average frame rate for running time of 284 secs = 55.9 fps

Memory managed: 130 Allocs, 130 Freed

********* FSUIPC Log file closed ***********

Please check the [JoyNames] section of the FSUIPC4.INI file --show it to me, in fact, please -- this should list the Joysticks identified via DirectInput. Any others shouldn't be "real".

here is the .ini file

[General]

UpdatedByVersion=4562

History=WQGONV54CDGZXGPBAC6RA

MouseWheelTrim=No

MouseWheelTrimSpeed=1

FixControlAccel=No

FixMachSpeedBug=No

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=0.5,2.5

TurbulenceDivisor=40,40,80,80

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=Yes

WindSmoothness=-3

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

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

Console=No

JoystickTimeout=15

BrakeReleaseThreshold=75

DontResetAxes=No

[JoyNames]

AutoAssignLetters=No

0=CH PRO PEDALS USB

1=CH THROTTLE QUADRANT

2=CH FLIGHT SIM YOKE USB

[buttons]

ButtonRepeat=20,10

1=P2,4,C66079,0

2=P2,5,C66080,0

4=P1,3,C65963,0

5=P1,5,C65968,0

6=P1,7,C65973,0

7=P1,9,C65978,0

8=P1,4,C65972,0

9=P1,2,C65967,0

10=P1,6,C65977,0

11=P1,8,C65982,0

12=P1,1,C66068,0

13=P1,0,C66067,0

[AutoSave]

AutoSaveEnabled=No

Interval=60

Files=10

SaveOnGround=No

Next=1

1=Wed 174744

2=Wed 174843

3=Wed 174943

4=Wed 175042

5=Wed 175142

6=Wed 175242

7=Wed 175341

8=Wed 175441

9=Wed 175540

10=Wed 175640

[GPSout]

GPSoutEnabled=No

Port=COM0

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=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

Throttle1=-16256,-12773,-11483,13208

Throttle2=-16256,-12257,-10709,14605

Throttle3=-16380,-12515,-10322,14478

Throttle4=-16256,-13289,-10967,13843

[Axes]

0=1R,256

1=1R,U,-390,13952,66079,0

2=1R,D,-16384,-6111,66080,0

Did you check Windows game controllers for an unknown and unwanted joystick driver? Did you run that Joyview program as I suggested?

game controller says everything OK the devices function normally according to the tests. I ran Joyview, got 16 "none" and the only action that got something moving was right and left brake....

You mean you didn't set FSX to run in compatibility mode yourself? It's right-click on the shortcut, Properties-Compatibility. Make sure none of the boxes are checked.

I wish I was more of a technician! when I right click on the shortcut I can go into properties but find no trace of compatibility, sorry!

Cheers

Luc

[Pete Dowson]

at 25 I got another freeze but at 15 no freeze... here is the log

15 looks good then, because according to your [JoyNames] section:

[JoyNames]

AutoAssignLetters=No

0=CH PRO PEDALS USB

1=CH THROTTLE QUADRANT

2=CH FLIGHT SIM YOKE USB

you only have joysticks 0, 1 and 2 connected, and those survived okay through the 15 mSec timeout check.

96081 Joy 11 taking too long to respond (> 15 mSecs). Removed from scan

140697 Joy 3 taking too long to respond (> 15 mSecs). Removed from scan

152319 Joy 15 taking too long to respond (> 15 mSecs). Removed from scan

153302 Joy 8 taking too long to respond (> 15 mSecs). Removed from scan

153333 Joy 14 taking too long to respond (> 15 mSecs). Removed from scan

153349 Joy 5 taking too long to respond (> 15 mSecs). Removed from scan

159776 Joy 13 taking too long to respond (> 15 mSecs). Removed from scan

159807 Joy 7 taking too long to respond (> 15 mSecs). Removed from scan

159823 Joy 6 taking too long to respond (> 15 mSecs). Removed from scan

160291 Joy 9 taking too long to respond (> 15 mSecs). Removed from scan

160759 Joy 4 taking too long to respond (> 15 mSecs). Removed from scan

160790 Joy 12 taking too long to respond (> 15 mSecs). Removed from scan

161757 Joy 10 taking too long to respond (> 15 mSecs). Removed from scan

There's something odd, though, with your system because all 12 other possible joystick numbers are causing Windows to take too long finding they aren't there. It is as if there is a driver processing those requests when there shouldn't be. Here, running Win7 Ultimate, I get no timeouts at all even with the value set as low as 10 mSecs.

game controller says everything OK

Did you click on the "Hardware" tab and see if there was anything listed which you didn't recognise?

I ran Joyview, got 16 "none" and the only action that got something moving was right and left brake....

Sorry, on Win7 all of the names listed in Joyview will say "none". It's an old program, meant for Win95 I believe. but it will show a lot of details. If there are any drivers for any of the 16 devices, this will show by having entries in the "joyGetDevCaps" entry. Genuinely unused slots will have no numbers against any of the details listed for 'folder', whilst ones with a driver will have data like Mid ("manufacturer ID") and Pid ("Product ID"). With those we should be able to identify the device/driver.

I wish I was more of a technician! when I right click on the shortcut I can go into properties but find no trace of compatibility, sorry!

Weird. In the Win7 installation I have, the Properties dialogue has 6 tabs:

General, Shortcut, Compatibility, Security, Details and Previous Versions.

Maybe this is only with the Ultimate edition? Anyway, the compatibility options must be there, in the Properties, somewhere. Even Windows XP had a Compatibility tab in the Properties dialogue!

At least with the timeout set to 15 you have everything working by the looks of it. I may make that the default.

Regards

Pete

[chevol]

Found the compatibility box... I had to go and click on the .exe file itself not the icon on deskstop (mystery) and un-clicked "run this prog in compatibility mode" for XP. but I left "run this prog as an administrator"

Luc

[chevol]

got the mids and pids!

Device 01

MID 1678

PID 242

Microsoft PC joystick driver

Device 02

MID 1678

PID 250

Microsoft PC joystick driver

Device03

MID 1678

PID 255

Microsoft PC joystick driver

Re hardware, apart from a Logitech headset I have nothing else

Thank you for all the hard work!

Luc

Luc

[Pete Dowson]

Found the compatibility box... I had to go and click on the .exe file itself not the icon on deskstop (mystery) and un-clicked "run this prog in compatibility mode" for XP. but I left "run this prog as an administrator"

Well really you shouldn't have to "run this prog as administrator" either. Is this because someone told you it was needed to run his application program? It only arises because:

a) if you let FS install into its default place, in "Program Files" or "Program Files (x86)", its folders are protected against being written to by programs without elevated admin rights, like installers.

b) Some add-ons need to write to FS folders which are still not Vista / Win7 aware and cannot handle this, so have to be run "as administrator", and

c) If those add-ons need to connect to FSUIPC4, which is running inside FSX, both the Add-On and FSX must be at the same privilege level, otherwise Windows stops them talking to each other!

It's a mess really. FSUIPC's installer makes the modules folder read/write capable for all users so it doesn't have the problem. Hopefully one day all add-ons will be Vista or win7 aware. Meanwhile, the easiest option is never install FS into the Program Files folders. Too late for many of course.

got the mids and pids!

Yes, but those are the three legitimate joystick devices we know you've got. Strange that there's nothing for units 4-16 which appear to be those causing the problems. Ah, well, if the timeout feature in FSUIPC gets over the problem I suppose it doesn't matter. It will remain a puzzle though.

Regards

Pete

[chevol]

Strange that there's nothing for units 4-16 which appear to be those causing the problems. Ah, well, if the timeout feature in FSUIPC gets over the problem I suppose it doesn't matter. It will remain a puzzle though.

I checked all other units (4 to 16) and they are all empty.

Another interesting point: I did a short test flight running ASA + FSX. once up in the air I loaded Squawkbox... It did not open and got stuck at initialising voice... I closed everything down, went back to the FSX.exe compatibility tag (I know it now) and re-clicked compatible XP. I Loaded FSX and then SB which opened and connected normally... bizarre

Again thank you Pete for your time and big help, what a good service!

Cheers

Luc

[Pete Dowson]

Another interesting point: I did a short test flight running ASA + FSX. once up in the air I loaded Squawkbox... It did not open and got stuck at initialising voice... I closed everything down, went back to the FSX.exe compatibility tag (I know it now) and re-clicked compatible XP. I Loaded FSX and then SB which opened and connected normally... bizarre

Well, Squawkbox4 does not use FSUIPC, and I don't know why it has such a need, but perhaps that's why you enabled the compatibility mode in the first place? Certainly FSX doesn't install with that option set.

Regards

Pete