FSUIPC freezes

[wanabflyer]

Hello. I am a newcomer and have a problem with my regisrered FSUIPC v4.7.6.1

When using the flight control options such as the Axis assignment, Buttons and Keys or Joystick Calibration, FSUIPC seems to freeze up and not accept input or recognize a button press. It also will not allow input when calibrating my yoke and will just give me a bell ring sound. If i then exit FSUIPC and then reopen it, things start working for a while.

This started after upgrading to the 4.7 versions after using an old v4.5 for some time. Is there a known cause for this?

Thanks in advance,

Rick Hobbs.

[Pete Dowson]

When using the flight control options such as the Axis assignment, Buttons and Keys or Joystick Calibration, FSUIPC seems to freeze up and not accept input or recognize a button press.

This is almost always a symptom resulting from a joystick or joystick driver misbehaving and sending continuous signals. Do you get any display of joystick number ot button number or axis at all? Is it possible you have some joystick driver installed for a joystick you no longer have connected?

It also will not allow input when calibrating my yoke and will just give me a bell ring sound.

The calibration tab only beeps when attempts are made to enter values in something other than ascending order, left to right.

Can you please do two things:

1. Show me your FSUIPC4.INI file, from the FSX Modules folder. Best to paste its contents into a message here.

2. Rename that file, to say FSUIPC4.oldini, then run FSX again and see if it works okay then. If so, it will be something corrupted or set incorrectly in the INI file.

If i then exit FSUIPC and then reopen it, things start working for a while.

All that does is re-scan the joystick devices to see if any new ones have connected or old ones disconnected. If doing that changes things it sounds definitely as if one or more of the devices you have connected is playing up. Perhaps you could unplug them all and try one at a time, to see which it is?

This started after upgrading to the 4.7 versions after using an old v4.5 for some time. Is there a known cause for this?

Well, 4.50 is a couple of years old so there are certainly a lot of new facilities and fixes in that period, but I don't know of anything which can specifically give the symptoms you describe.

Regards

Pete

[wanabflyer]

Hi Pete. Thanks for your reply. Below is my ini file.

[General]

UpdatedByVersion=4761

History=U6H7M9TJV14NI4JH9NF0N

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

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=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=Yes

WindSmoothness=-3

WindSmoothAirborneOnly=Yes

PressureSmoothness=20

TemperatureSmoothness=100

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

UseProfiles=Yes

EnableMouseLook=No

DeleteVehiclesForAES=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

0=Saitek Pro Flight Yoke

0.GUID={AECDC960-46C1-11E1-8001-444553540000}

1=CH PRO PEDALS USB

1.GUID={73C56550-A755-11E0-8001-444553540000}

2=Saitek X52 Flight Controller

2.GUID={65A29D90-A62D-11E0-8002-444553540000}

[WideServer]

WideFSenabled=Yes

[sounds]

Path=E:\Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Creative SB Audigy 4 (WDM))

Device3=Speakers (Corsair Vengeance 1500)

Device4=SPDIF Out (Creative SB Audigy 4 (WDM))

[buttons]

ButtonRepeat=20,10

1=P0,0,K90,8

3=P0,32,K75,8

4=P0,36,K73,8

9=P0,1,K88,9

11=P0,12,K68,8

16=P0,22,K69,9

17=P0,20,K70,9

25=P2,6,K87,9

26=P2,22,K219,8

27=P2,20,K221,8

28=P2,26,K71,8

29=P2,27,K71,9

30=P2,28,K116,8

31=P0,11,K70,9

32=P0,13,K69,9

33=P0,38,K75,9

34=P0,34,K90,9

35=P0,4,K85,9

36=P0,5,K68,8

37=P0,6,K74,8

38=P0,7,K76,8

39=P0,2,K86,9

40=P0,3,K77,8

41=P0,14,K117,8

42=P0,15,K118,8

43=P0,16,K220,8

44=P0,17,K191,8

46=P2,7,K191,9

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[Axes]

0=0X,256,D,1,0,0,0

1=0Y,256,D,2,0,0,0

2=0U,256

3=0U,B,-16384,16383,65786,0

4=1X,256,D,7,0,0,0

5=1Y,256,D,8,0,0,0

6=1Z,256,D,3,0,0,0

7=2Z,256,D,4,0,0,0

8=2Z,BR,-16384,-14173,65602,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

Aileron=-16223,-481,416,15264/8

Elevator=-15322,-224,256,16064/8

Rudder=-16384,-260,-260,16256/8

Throttle=-8192,16383

LeftBrake=-16384,16256/24

RightBrake=-16383,16256/24

SlopeAileron=7

SlopeElevator=7

SlopeRudder=7

SlopeThrottle=3

SlopeLeftBrake=7

SlopeRightBrake=7

Yes i have changed my yoke from a CH to a Saitek PF yoke, but this problem started before i switched. I will however still take another look to see if there is anything related to the CH left.

I do not install any control software such as CH C.M. or SST. I just plug in and set up with FSUIPC.

To enlarge on the the lack of response in the button press area, i can press a button on my yoke and a button # will show up along with a joystick #. I can then check the 'select for key press' box and set my key press. This will be ok for a few, then it just stops responding to a button press at which time i exit and return. (This does not happen every single time)

Just to put you in the picture, I am using a X52 throttle and now a Saitek Yoke and seem to be working perfectly together after managing to get my button and axis input done, but i know i am going to go through the same thing when i start setting up my Saitek throttle quadrant to replace my X52 axis.

I will be at my FSX pc tomorrow evening when i will try to rename my ini file and report on the results.

Regards,

Rick Hobbs.

[Pete Dowson]

Hi Pete. Thanks for your reply. Below is my ini file.

Okay. Nothing there truly odd, but a couple of questions and suggestions.

First, I see all your Button assignments are to keypresses, every single one. Are they all to do things which FS cannot do -- i.e. all aimed at some add-on? If not, if you are using them for FS controls, it is a very very inefficient way of doing thnigs. You'd be far better off assigning to the relevant FS control instead, for every one.

Second, you have two axis assignments which operate on 'ranges' -- i.e. the right-hand side of the axis assignments -- in one case instead of any true axis input:

This one:

2=0U,256

3=0U,B,-16384,16383,65786,0

appears to set the complete possible range to sending FS control "SPOILERS SET" (65786). So why not simply assign to that control instead? You used Direct to FSUIPC Calibration for other axes, why not to Spoilers too?

This one

7=2Z,256,D,4,0,0,0

8=2Z,BR,-16384,-14173,65602,0

Looks okay. Instead of mapping the throttle ot the 4 separate throttles so you can have a reversed zone you've used the right-hand zone settings for "THROTTLE_DECR". An interesting solution, I suppose, to those add-ons which don't like the normal way FSUIPC accomplidhes this?

In the calibration section:

Aileron=-16223,-481,416,15264/8

Elevator=-15322,-224,256,16064/8

Rudder=-16384,-260,-260,16256/8

Throttle=-8192,16383

LeftBrake=-16384,16256/24

RightBrake=-16383,16256/24

you have 5 of the 6 axes set with "Filtering" enabled. That worries me. Really filtering is a last resort for very dirty or badly behaved controls or extremely poor power -- it was originaly added to help a chap with wobbly mains power in the Malaysian jungle!

I'm paricularly concerned that the filtering relies on extra timers and Windows messages which might be getting blocked by other add-ons, so please try without. You can do this most easily by changing the above to:

Aileron=-16223,-481,416,15264

Elevator=-15322,-224,256,16064

Rudder=-16384,-260,-260,16256

Throttle=-8192,16383

LeftBrake=-16384,16256/16

RightBrake=-16383,16256/16

Please also can you tell me what other non-aircraft add-ons are running inside FSX? Maybe the easiest way is to show me the DLL.XML file, from the same folder as your FSX.CFG file.

To enlarge on the the lack of response in the button press area, i can press a button on my yoke and a button # will show up along with a joystick #. I can then check the 'select for key press' box and set my key press. This will be ok for a few, then it just stops responding to a button press at which time i exit and return. (This does not happen every single time)

That does sound like some sort of hangup on a joystick driver during the scanning. Can you check the Windows game controllers (or, in Vista/Win7 the "devices and printers" applet) to see if it lists anything you don't actually have connected?

Regards

Pete

[wanabflyer]

Hi Pete.

The various button assignments are for the PMDG 737NGX where the controls are applied by key press assignments specific to and set up within that add on. When trying to use 'Select For FS Control', it does not appear to work with this aircraft in many cases, so i went the key press route within FSUIPC. I have however found so far that one will work. That being the autothrottle arm, which for some reason works in reverse, so i now use it selected for FS control, for disconnect.

Having said all that, it could be that i am just not aware of how to use this feature and need to do some more reading.

As for the spoilers, i have now set up on one of my throttle quadrant levers and am just about ok with that but still need some more tweaking to set the 'arm' position.

As for the throttle, Until i can come up with a mod to tie the levers together, i am using my X52 throttle to control both engines and have set up my reverse thrust in the area below the detent. This actually works very nicely (probably by luck more than good management)

I have removed the filtering and will post you the DLL.XML file shortly.

As for other devices not actually connected, there is one device shown within the applet you mention. It is listed as unknown device and under properties state's that no drivers installed and i do not know how to remove it.

Thanks and regards,

Rick Hobbs.

[Pete Dowson]

As for other devices not actually connected, there is one device shown within the applet you mention. It is listed as unknown device and under properties state's that no drivers installed and i do not know how to remove it.

Try just uninstalling the device. You'll probably need to go to the device manager for that. Control Panel - System - Device Manager. finding the device in the list might not be so easy though.

Regards

Pete

[wanabflyer]

Have deleted the unknown device and here as promised is my dll.xml file:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon><Name>Addon Manager</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>bglmanx.dll</Path></Launch.Addon>

<Launch.Addon>

<Name>Object Placement Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Traffic Toolbox</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Visual Effects Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG Options</Name>

<Disabled>False</Disabled>

<Path>PMDG\DLLs\PMDGOptions.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG Events</Name>

<Disabled>False</Disabled>

<Path>PMDG\DLLs\PMDGEvents.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG Sounds</Name>

<Disabled>False</Disabled>

<Path>PMDG\DLLs\PMDGSounds.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG HUD interface</Name>

<Disabled>False</Disabled>

<Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>VistaMare Core</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>VistaMare\ViMaCoreX.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Multi Crew Experience</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>fsInsider.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

</SimBase.Document>

Regards,

Rick hobbs.

[Pete Dowson]

Have deleted the unknown device

You've done that, and you removed the filtering. Any change to the problem at all?

and here as promised is my dll.xml file:

Well the other modules which are also alaways running as well as FSUIPC4 are the PMDG ones:

PMDG\DLLs\PMDGOptions.dll

PMDG\DLLs\PMDGEvents.dll

PMDG\DLLs\PMDG_HUD_interface.dll

VistaMare\ViMaCoreX.dll

fsInsider.dll

Of those I also have PMDG_HUD_interface.dll and ViMaCoreX.dll running, but oddly not the other two PMDG modules despite having the 737NGX installed.

Just to see if there's some interaction, could you please try this:

1. Rename that DLL.XML to something different, like DLL.MYXML

2. Run the FSUIPC4 installer so it makes a fresh DL.XML file with only FSUIPC4 loading.

3. Test again.

Let me know if that helps. If not, restore your DLL.XML and I'll have to look into what sort of other tests we can do.

Regards

Pete

[wanabflyer]

Tried renaming but lost all add on airport buildings and although my PMDG NGX loaded, PMDG was not listed in the menu.

Pmdg is apparently about to release SP1C, so am thinking i will just clean re install NGX at that point and see if that helps.

Regards,

Rick Hobbs.