VRInsight MCP Pro Support

[Pete Dowson]

I could wish I was a little less unique! :D sorry to be such a pain in the ass! My system is OC'd to 4GHz on an 17 socket 1152 with a base speed of 2.8, but I can't see anyhting running that would cause this interaction with FSUIPC. My Video card is a GTX 285 2GB, and I have the latest NVDIA WHQL drivers, basically WTF???? :D

No idea at present. Tell you what. don't worry about the email for now, just download this:

http://fsuipc.simflight.com/beta/FSUIPC4601a.zip

Copy the DLL into the FSX Modules folder, and rerun the test. Then show me the FSUIPC4.LOG again, please (even if it works by some chance, which is unlikely because i've only added a couple of Log lines into it -- for entry and exit from the routine doing those Open okay/fail attempts).

It's only that 1=COM3,COM22 line which could be doing this, but how I've no idea, yet. To simply get on and have a fly, remove that line -- but not till after you run this test for me, please!

I'll not get to see it till tomorrow (Thursday) now.

Regards

Pete

[CathyH]

********* FSUIPC4, Version 4.601a by Pete Dowson *********

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

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

User Name="CatHERINE hOWAT"

User Addr="cathyhowat@hotmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

187 System time = 11/03/2010 13:23:56

187 FLT UNC path = "C:\Users\User 977\Documents\Flight Simulator X Files\"

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

1029 LogOptions=00000000 00000051

1029 SimConnect_Open succeeded: waiting to check version okay

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

11325 Initialising SimConnect data requests now

11325 FSUIPC Menu entry added

11372 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

11372 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

11372 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

117531 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

117781 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

117781 Checking for VRI COM ports to Open ...

117796 VRI port 1 "COM3" failed to open

117796Finished VRI COM port checking.

132335 System time = 11/03/2010 13:26:08, Simulator time = 13:24:09 (21:24Z)

132772 Aircraft="Aircreation582SL red"

133474 Advanced Weather Interface Enabled

154051 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

154051 Sim stopped: average frame rate for last 36 secs = 12.4 fps

165033 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

167810 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y

174908 System time = 11/03/2010 13:26:51, Simulator time = 13:24:33 (21:24Z)

174908 *** FSUIPC log file being closed

Average frame rate for running time of 38 secs = 12.7 fps

Memory managed: 75 Allocs, 74 Freed

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

OK, on loading, (default flight but with ORBX NA Blue PNW) the screen locked for a moment and I had to hit "Escape". Note, with UTX2 the screen does sometime lock while it loads it's traffic. After that I was over Friday Harbor and hitting around 22FPS, but the thing is not loading that com3, which would tend to bear out what you are thinking, wouldn't it?

FYI my motherboard is a Gigabyte GA-P55A-UD5,

[Pete Dowson]

*

117781 Checking for VRI COM ports to Open ...

117796 VRI port 1 "COM3" failed to open

117796Finished VRI COM port checking.

I'm afraid this tells me nothing, as evidently this time something else already had the COM3 port to which your VRI device is connected. You need to ensure SerialFP2 is closed BEFORE running FS or there's no way FSUIPC can access the port.

OK, on loading, (default flight but with ORBX NA Blue PNW) the screen locked for a moment and I had to hit "Escape". Note, with UTX2 the screen does sometime lock while it loads it's traffic.

The log does show that FSX is taking a long time to load your initial flight:

11372 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

11372 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

11372 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

117531 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

117781 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

117781 Checking for VRI COM ports to Open ...

That's 106 seconds to load the flight. However, if there's a lot of photo textures to load that's not unexpected, especially if you've not defragmented your hard disk for a while. FSUIPC is not doing anything at all during that time -- it will be nearly all disk activity, probably with the progress bar going very slowly to 100% (the numbers on the left in the log are milliseconds. Divide by 1000 for seconds).

After the COM3 port failed to open, the SerialFP2 program should have been loaded:

117796Finished VRI COM port checking.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< HERE

132335 System time = 11/03/2010 13:26:08, Simulator time = 13:24:09 (21:24Z)

but there's no sign except that 15 second gap. Are you sure that the apparent hang, which you get out of by hitting "ESCape", isn't an error message box saying that SerialFP2 either can't be loaded or has an error? If you are running FSX in full screen mode you might not see it. For testing try running FSX in Windowed mode, just in case.

And check that you have this line right in your FSUIPC4.INI file:

Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

It seems odd that you have SerialFP2 on D:\Program Files (x86)\ when FSX is on G:\Program Files (x86)\

After that I was over Friday Harbor and hitting around 22FPS, but the thing is not loading that com3, which would tend to bear out what you are thinking, wouldn't it?

No, nothing in this log bears any relationship at all to what happened in the last and doesn't help locate THAT problem at all. Sorry. You'll need to reproduce the first case -- i.e. where COM3 is, in fact, available for use as it was then.

Maybe you should restart Windows before doing any test, to make sure everything starts off the same way?

FYI my motherboard is a Gigabyte GA-P55A-UD5,

I don't think hardware has anything to do with this. This last inability to open COM3 merely means either that the device is no longer on COM3 (which seems unlikley), or that the COM3 port was already owned by another program.

If you aren't sure what is running before starting FSX, right-click in the task bar and select "Start Task Manager", then the "Processes" tab. Scroll down the list and make sure neither FSX.exe or SerialFP2.exe are listed there. If they are, terminate them ruthlessly.

Regards

Pete

[KAPTEJNLN]

[VRInsight]

1=COM3,COM22

[Programs]

Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

The Dialog box for vspe shows that virtual ports for VSPE show virtual ports 21 and 22 are OK.

By Locking up I mean freezing then crashing to desktop. I have tried loading with both traffic set at zero, with traffic, or with the other option I have of Ultimate Traffic FSX which is generated externally. I have tried autoloading SerialFSP with MS Default file, with a file I have created, and with a Wilco file. Nothing works and the program is still freezing. If I can get the virtual com port to open, the problem has to occur after that, but I am blowed if I know where.

Cathy

Well 1 small things i have spottet try to do like this

[Programs]

Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

Have you instalt SerialFP2.exe on your d drive like in the manual as i have corectet my to the location of it by simply copy it from the line then add \SerialFP2.exe at the end and it shoul look like below

[Programs]

Run1=READY,CLOSE,C:\Program Files\SerialFP2\SerialFP2.exe

best regards Lars

[CathyH]

Been stuck in bed with a bad migraine for some days, any news?

Cathy

[Andydigital]

What? Pete is waiting for you to answer his questions, he cant advise you further if you don't do anything, please review the posts on page 2 at least.

Peter is away till next Monday now anyway so it will give you plenty of time to test. Also as Lars said in the post before yours are you sure SerialFp2 is installed to your D or G drive, because the line below must point to the correct location otherwise it wont work.

Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

[CathyH]

I have tried the above, still locking and crashing. I am now running without UTX2 and with default scen ery

Here is the log file:

******** FSUIPC4, Version 4.60a by Pete Dowson *********

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

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

User Name="Catherine Howat"

User Addr="cathyhowat@hotmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

187 System time = 19/03/2010 11:40:22

187 FLT UNC path = "C:\Users\User 977\Documents\Flight Simulator X Files\"

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

671 LogOptions=00000000 00000051

671 SimConnect_Open succeeded: waiting to check version okay

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

12261 Initialising SimConnect data requests now

12261 FSUIPC Menu entry added

12308 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

12308 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

12308 G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

116579 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

116642 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N

116735 VRI port 1 "COM3" opened

116735 VRI driver port 1 "COM24" also opened

116735 VRI port 1 "COM3" failed to open

116751 VRI port 1 "COM3" failed to open

116813 VRI port 1 "COM3" failed to open

116876 VRI port 1 "COM3" failed to open

116938 VRI port 1 "COM3" failed to open

117001 VRI port 1 "COM3" failed to open

117063 VRI port 1 "COM3" failed to open

117125 VRI port 1 "COM3" failed to open

117188 VRI port 1 "COM3" failed to open

117250 VRI port 1 "COM3" failed to open

117313 VRI port 1 "COM3" failed to open

117375 VRI port 1 "COM3" failed to open

117437 VRI port 1 "COM3" failed to open

117500 VRI port 1 "COM3" failed to open

117562 VRI port 1 "COM3" failed to open

117625 VRI port 1 "COM3" failed to open

117687 VRI port 1 "COM3" failed to open

117749 VRI port 1 "COM3" failed to open

117812 VRI port 1 "COM3" failed to open

117874 VRI port 1 "COM3" failed to open

117937 VRI port 1 "COM3" failed to open

117999 VRI port 1 "COM3" failed to open

118061 VRI port 1 "COM3" failed to open

118124 VRI port 1 "COM3" failed to open

118186 VRI port 1 "COM3" failed to open

118249 VRI port 1 "COM3" failed to open

118311 VRI port 1 "COM3" failed to open

118373 VRI port 1 "COM3" failed to open

118436 VRI port 1 "COM3" failed to open

118498 VRI port 1 "COM3" failed to open

118561 VRI port 1 "COM3" failed to open

118623 VRI port 1 "COM3" failed to open

118685 VRI port 1 "COM3" failed to open

118748 VRI port 1 "COM3" failed to open

118810 VRI port 1 "COM3" failed to open

118873 VRI port 1 "COM3" failed to open

118935 VRI port 1 "COM3" failed to open

118997 VRI port 1 "COM3" failed to open

119060 VRI port 1 "COM3" failed to open

119122 VRI port 1 "COM3" failed to open

119185 VRI port 1 "COM3" failed to open

119247 VRI port 1 "COM3" failed to open

119309 VRI port 1 "COM3" failed to open

119372 VRI port 1 "COM3" failed to open

119434 VRI port 1 "COM3" failed to open

119497 VRI port 1 "COM3" failed to open

119559 VRI port 1 "COM3" failed to open

119621 VRI port 1 "COM3" failed to open

119684 VRI port 1 "COM3" failed to open

119746 VRI port 1 "COM3" failed to open

119809 VRI port 1 "COM3" failed to open

119871 VRI port 1 "COM3" failed to open

119933 VRI port 1 "COM3" failed to open

119996 VRI port 1 "COM3" failed to open

120058 VRI port 1 "COM3" failed to open

120121 VRI port 1 "COM3" failed to open

120183 VRI port 1 "COM3" failed to open

120245 VRI port 1 "COM3" failed to open

120308 VRI port 1 "COM3" failed to open

120370 VRI port 1 "COM3" failed to open

120433 VRI port 1 "COM3" failed to open

120495 VRI port 1 "COM3" failed to open

120557 VRI port 1 "COM3" failed to open

120620 VRI port 1 "COM3" failed to open

120682 VRI port 1 "COM3" failed to open

120745 VRI port 1 "COM3" failed to open

120807 VRI port 1 "COM3" failed to open

120869 VRI port 1 "COM3" failed to open

120932 VRI port 1 "COM3" failed to open

120994 VRI port 1 "COM3" failed to open

121057 VRI port 1 "COM3" failed to open

121119 VRI port 1 "COM3" failed to open

121181 VRI port 1 "COM3" failed to open

121244 VRI port 1 "COM3" failed to open

121306 VRI port 1 "COM3" failed to open

121369 VRI port 1 "COM3" failed to open

121431 VRI port 1 "COM3" failed to open

121493 VRI port 1 "COM3" failed to open

121556 VRI port 1 "COM3" failed to open

121618 VRI port 1 "COM3" failed to open

121681 VRI port 1 "COM3" failed to open

121743 VRI port 1 "COM3" failed to open

121805 VRI port 1 "COM3" failed to open

121868 VRI port 1 "COM3" failed to open

121930 VRI port 1 "COM3" failed to open

121993 VRI port 1 "COM3" failed to open

122055 VRI port 1 "COM3" failed to open

122117 VRI port 1 "COM3" failed to open

122180 VRI port 1 "COM3" failed to open

122242 VRI port 1 "COM3" failed to open

-------------------------------------------------------------------------------------------

Here is my INI file.:

[General]

UpdatedByVersion=4600

History=XM1RT7HSFPWEA35KP81MW

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

Console=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

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

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

PollGFTQ6=Yes

BlankDisplays=No

Debug=Please

LogExtras=x4

[JoyNames]

AutoAssignLetters=No

0=Saitek Pro Flight Rudder Pedals

1=Saitek Pro Flight Yoke

2=Saitek Pro Flight Quadrant

3=Saitek Pro Flight Quadrant

4=Logitech Attack 3

0.GUID={67AEFD60-11AD-11DF-8005-444553540000}

1.GUID={67AEFD60-11AD-11DF-8006-444553540000}

2.GUID={67AEFD60-11AD-11DF-8007-444553540000}

3.GUID={67AEFD60-11AD-11DF-8008-444553540000}

4.GUID={AC5BA660-17F8-11DF-8001-444553540000}

[WideServer]

WideFSenabled=Yes

[buttons]

ButtonRepeat=20,10

[AutoSave]

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[MacroFiles]

1=737vs

2=Abxpd

3=Aphs

4=Apsp

5=Axcl

6=Lnav

7=Vnav

8=Vsmode

9=wxr

10=Xpd

[Keys]

2=8,8,65729,0

5=35,8,65729,0

9=120,8,65726,0

11=118,8,66720,0

13=117,8,65903,0

15=115,8,66724,0

16=114,8,66536,0

18=112,8,66287,0

20=123,8,66100,0

23=122,8,66102,0

[VRInsight]

1=COM3,COM24

[Programs]

Run1=READY,CLOSE,G:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

Lets hope this helps!

[Andydigital]

I have tried the above

Tried what exactly? Please us quotes if you cant be bothered typing a more detailed reply.

Are you making sure you do not run SerialFP2 manually and are instead letting FSUIPC start it for you?

Are you absolutely certain that SerilaFP2.exe is installed on your G: drive?

Have you confirmed that nothing else on your computer is using COM port 3 as well? this shouldn't be possible but locking up could be a sign of this if two devices are trying to share the same port. Something screwy is definitely happening on your system, make sure you haven't got any other really old hardware connected that uses real Serial ports.

[CathyH]

Is there a software that can tell me what each device is using. Com Three is a USB serial port and almost all of my usb ports are in use. :(

[guenseli]

Hi Cathy,

one tip: take out your mailadress (3rd line on the FSUIPC log, User Addr...) or you get spammed

[guenseli]

second tip:

"Run1=READY,CLOSE,G:\Program Files (X86)\VRInsight\SerialFP2\SerialFP2.exe"

this path is wrong, look at the red backslash, this is missing in your path

you can comment it also out

"\\Run1=READY,CLOSE,G:\Program Files (X86)\VRInsight\SerialFP2\SerialFP2.exe"

to disable it and start SerialFP manually after(!) you have loaded a flight and waited some seconds.

so you can test and analyze this...

[CathyH]

YES!!!!!! SUCCESS : now, what is the best way to program my rotary button for best functionality, and do you have a "template" of home others have programmed this device you could post?

[Pete Dowson]

Been stuck in bed with a bad migraine for some days, any news?

News of what? Have you corrected this line:

Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

and re-tested yet? As two of us have already pointed out, that cannot be the correct path to your SerialFP2 program!

Pete

[Andydigital]

This is resolved now Pete :wink:

[Pete Dowson]

This is resolved now Pete :wink:

Ah, good. I respond to each message as I come to it and failed to note there were more below the first one I'd not seen.

Thanks!

Pete

[CathyH]

Thanks for all the help, Pete, much appreciated. Quick question, how can I program my Saitek Yoke hat switch via FSUIPC so it pans smoothly, also, how can I assign the F2 thrust revers to a Throttle qaudrant lever so that it works?

[Pete Dowson]

how can I program my Saitek Yoke hat switch via FSUIPC so it pans smoothly

In FSX assign it to the Pan View axis control in axis assignments. If FS9 the best you can do is shown in the example in the documentation.

also, how can I assign the F2 thrust revers to a Throttle qaudrant lever so that it works?

Why use F2? If you want a reverse zone follow the instructions in the documentation.

Regards

Pete

[CathyH]

PEte, the problem is that I do not realy UNDERSTAND the instruction. I have tried to assign an axis to gear as per the example, on Quadrant 3 lever 1, but even though I have followed the steps, I must be getting something wrong as the control does no cause the gear to lower

[Pete Dowson]

the problem is that I do not realy UNDERSTAND the instruction. I have tried to assign an axis to gear as per the example, on Quadrant 3 lever 1, but even though I have followed the steps, I must be getting something wrong as the control does no cause the gear to lower

Show me what you've done, or speciofically what you don't understand in the instructions. I can't explain here better than in the documentation -- if I could it would already be like that in the documentation, don't you see? Why would I prefer to type it differently over and over in a Forum than once and for all in the documentation?

If English isn't your natural language, perhaps you could get someone to help?

Regards

Pete

[mtjoeng]

Thanks for all the help, Pete, much appreciated. Quick question, how can I program my Saitek Yoke hat switch via FSUIPC so it pans smoothly,

dear fellow Saitek user,

you (unfortunately) need to learn how to read/edit your fsuipc.ini

and/or know exactly how it is defined in your fsuipc interface showing;

'Buttons + Switches' menu in the Interface with the

'Select for FS control' checkbox (up right)

dropdown menu 'Control send when button pressed', to be used for Panning, involving

a 'parameter' box that defaults to 0 or Empty

a checkbox 'Control to repeat while held' will write "R" to the fsuipc.ini, to be used for Panning

dropdown menu 'Control send when button RELEASED' not to be used for Panning

(middle checkbox "Aircraft specific" you will want to use when defining Reverse Throttle with different engine aircraft, get to that later)

I have my Saitek configered/checked, referenced to

the "List of FSX controls.pdf" doc's (learn to search it quickly)

'' values, the numbers

the controls named f.i.:

'PAN_DOWN, xx_LEFT, xx_RIGHT' etc. and to be repeated when held 'R'

and

in the fsuipc.in will show up in the [buttons] section as:

210=RJ,32,C65734,0

and means;

210(starting any high number for Line Numbering)=R(for 'repeat')J(your 'Joystick Letter' in Fsuipc menu when you press),32(button number when you press),C(precedes a Control)65734(=control PAN_RIGHT_UP),0(defaults parameter 0)

and the full 8 directions being;

"List of FSX controls.pdf" your pan has 8 'buttons' up, upleft, left, leftdown, etc:

PAN_DOWN 65735

PAN_LEFT 65671

PAN_LEFT_DOWN 65855

PAN_LEFT_UP 65854

PAN_RIGHT 65672

PAN_RIGHT_DOWN 65857

PAN_RIGHT_UP 65856

PAN_UP 65734

so my

[buttons]

(will add line numbering in sequence what is found there before,

but I edit to 'HighUp' sequence, 'out of the way',

so I do not even repeat this block of line in specific other aircraft,

f.i. [buttons.FeelThere Boeing] or [buttons.Piper PA31T], and

this will be remembered for these other planes

(not sure if it's supposed to be like this, but laziness was involved))

has added:

210=RJ,32,C65734,0

211=RJ,33,C65856,0

212=RJ,34,C65672,0

213=RJ,35,C65857,0

214=RJ,36,C65735,0

215=RJ,37,C65855,0

216=RJ,38,C65671,0

217=RJ,39,C65854,0

for my Saitek at "J", and hat buttons 32-39

*******************

and is done through the Fsuipc interface (bar errors, if I mix up the sequence):

*******************

1. go to 'Buttons + Switches' menu in the Interface

2. press Hat (Up) button, shows Joy# and Btn# in upper middle

3. 'Select for FS control' checkbox (to define by dropdown)

4. scroll and select down to 'Pan Up'

5. keep parameter '0' or Empty

6. check box 'Control to repeat while held', this will write "R" to the fsuipc.ini, to be used for Panning (continued)

7. 'Control send when button RELEASED' not to be used for Panning (used for Cut Reverse Throttle)

8. again keep parameter '0' or Empty

and repeat for all 8 directions (middle directions Hard to toggle, good luck :)

******************

done

******************

for education and checking (and cleaning redundant) your fsuipc.ini:

I have also a MS Sidewinder FF joystick attached, same thing for that HAT:

590=RY,32,C65734,0

591=RY,33,C65856,0

592=RY,34,C65672,0

593=RY,35,C65857,0

594=RY,36,C65735,0

595=RY,37,C65855,0

596=RY,38,C65671,0

597=RY,39,C65854,0

makes sense (does it?)

also, how can I assign the F2 thrust revers to a Throttle qaudrant lever so that it works?

Saitek does not really support throttle "Cut" & Reverse <> like in the 'classic' CH Yokes

when you 'click' down to below 'horizontal'

that's really a Button, so no gradual reverse,

BUT that's exactly what you ask for, a 'F2-epeat' to Reverse after touchdown

and the control '#'s I use are

THROTTLE_DECR 65602 (checkbox 'Control to repeat while held' will write "R" to the fsuipc.ini)

THROTTLE_CUT 65604 (define this in the 'Control send when button RELEASED' so

your Throttle gets Unstuck for sure, back up to Cut)

or (multiple engines)

THROTTLE1_CUT 65967

THROTTLE1_DECR 65966

THROTTLE2_CUT 65972

THROTTLE2_DECR 65971 etc 3/4 for multiple engine sliders

for 1/2/3/4 engine planes, that I use

besides 1 original, I have 2 xtra Saitek Quadrants, so 9 sliders,

but with 6 sliders, you can of course do 4 engine jets also,

with 1 qudrant, you have to define 1 slider for left 2 engines,

1 slider for right 2 engines, and there are difinitions for that in the fsuipc interface,

Joystick calibration "3 of 11" "Seperate throttles per engine" "Map" 1->12, 2->34

and this will show up in your [buttons] like this:

50=RT,6,C65966,0 ;THROTTLE1_DECR 65966

51=UT,6,C65967,0 ;THROTTLE1_CUT 65967

52=RT,7,C65971,0 ;THROTTLE2_DECR 65971

53=UT,7,C65972,0 ;THROTTLE2_CUT 65972

R < repeat

65966 ("List of FSX controls.pdf")

T < the Letter show up in the fsuipc interface when click down

'6' < the number show up in the fsuipc interface when click down

*******************

and is done through the Fsuipc interface (bar errors, if I mix up the sequence):

*******************

1. go to 'Buttons + Switches' menu in the Interface

2. slide Throttle1 Down = slider button, shows Joy# and Btn# in upper middle (aircraft specific maybe?)

3. 'Select for FS control' checkbox (to define by dropdown)

4. scroll and select down to 'Throttel 1 Decr'

5. keep parameter '0' or Empty

6. check box 'Control to repeat while held', this will write "R" to the fsuipc.ini, to be used for continued pressing of F2

7. dropdown 'Control send when button RELEASED' to 'Throttel 1 Cut' and writes a 'U' in the fsuipc line

8. again keep parameter '0' or Empty

and repeat for all throttle sliders (or mixture cut or prop pitch feather)

******************

done

******************

for my (default flight) default 2 engine Beech King

I also have 2 slides defined for PropPitch, (could do mixture also, but lazy)

and 'reverse-down-bitton' defined as "Prop Pitch xx Decr" (repeated)

and cuts back to "Prop Pitch xx Hi' to Prop Feather (comes in handy when runaway taxiing)

of course, by now,

u have to figure out which planes will use 1 throttle, or 2 or 3 or 4

or 1 or 2 mixture, or Prop Pitch etc etc

and that's when you wnat to know how to edit your fsuipc.ini straight with

a (programmers!) text editor

(do Not use Wordpad, it leaves - invisible - formatting codes, that will ruin your effort)

not only for checkin errors, but to see what can be done with all those precious buttons and sliders

and then

you will have officialy joined the Fsuipc club :mrgreen: , mt, good night and good luck

[Andydigital]

Or just assigned it in FS like any normal sane person does, which will take all of about 10 seconds :D

[mtjoeng]

Or just assigned it in FS like any normal sane person does, which will take all of about 10 seconds :D

that's how you did it?

your first HAT definition in 10 second?

your first reverse throttle in a seperate 3 engine MD11 aircraft model in 10 seconds?

that's also how your nose grew a couple of inches in the last 10 seconds :twisted:

[Andydigital]

I was only talking about assigning the Hat Switch on the Saitek yoke from within FS, if it really appears as a hat switch in windows then it is a simple matter of assigning it in the FS controls interface which takes about 10 seconds to achieve if you have hands and eyes. If the hat switch appears as just 4 buttons then its not so simple as you have pointed out.

Assigning the Saitek throttle quadrant to send F2 when the levers are pulled to the reverse detent (which is a switch not an axis) is also very easy to assign in FS or FSUIPC, and also only takes a very short time to achieve.

[mtjoeng]

I was only talking about assigning the Hat Switch on the Saitek yoke from within FS, if it really appears as a hat switch in windows then it is a simple matter of assigning it in the FS controls interface which takes about 10 seconds to achieve if you have hands and eyes. If the hat switch appears as just 4 buttons then its not so simple as you have pointed out.

Ms. CathyH seems obviously a newbe

I can remember to get the serial numbers of Fsuipc working took me hours as a newbe (and is still the case when you watch this forum)

Ms. CathyH also did not inquire about FS controls, for these are defined by default by MSFS so that would be redundant advice, like me, she appears to want to diable all FS Controls. Ever tried to clean out your FS Controls? that takes many many 10 seconds, and a HAT never appears anywhere as 4 buttons, btw.

Assigning the Saitek throttle quadrant to send F2 when the levers are pulled to the reverse detent (which is a switch not an axis) is also very easy to assign in FS or FSUIPC, and also only takes a very short time to achieve.

Mr. VRInsight moderator (yes we know), many people (like me when a newbe with my 1st CH Yoke) will have no clue if its a slider or a switch

so lets disregard supposed professional near sightedness

no, flight simulator hardware add-ons are Not easy to connect

unless you fly Cessna 172 only

so let Ms. CathyH do her reading (she only has to notice the ******* in between *******)

and no, I do not think marketing speak is the holy grail towards prosperity

on the contrary

can I myself define a HAT in 10 minutes, sure, now I can, after owning fsuipc for 6 years

(its late Andy)

[Andydigital]

I've no idea why you find it necessary to use such a condescending tone with me, its not appreciated, some of my comments were made tongue in cheek and I was trying to help.

When is a hat switch not a hat switch? when it appears as four separate buttons instead, Saitek hat switches can be setup via its drivers/software to appear as a 4 or 8 way hat and even as separate buttons instead if you so wish. Some really cheap joysticks and game-pads don't even have a true hat switch, its just 4 separate buttons arranged in a cross shape.

I see no reason at all to disable joysticks completely in FS, it always makes sense to at least leave the HAT switch assigned in FS and I'm sure Pete will agree with me on this point.

You only need to assign everything once in FS and this includes removing the assignments you do not want for other devices (don't forget slew mode too), once you are happy with it make a safe backup of the controls setting file for future use after a reinstall or after FS decides that it knows better than the user and reassigns everything back to default again for a newly connected device. If it does this simply copy the file back again and you are back to the way you like it. I think you may even be able to mark the file as read-only which should stop FS making a mess of things but I've never needed to try this for myself.

I was offering Cathy a simpler alternate and you seem to concur as you made the point that Cathy appears to be a newbie (your words) and I'm pretty certain everything you said went completely over her head, no offence meant Cathy.