VRInsight MCP Pro Support

[CathyH]

Will Fsuipc for FSX be supporting this addon?

[Andydigital]

If you mean VRInsight MCP Combo then yes it already does support pretty much all VRInsight hardware, that's one of the new features just added to FSUIPC 4.6a for FSX and 3.98a for FS9.

[CathyH]

I have just downloaded and installed 4.60a. NOW if somebody could put what is in the advanced user's manual into VERY simple English, I MIGHT be able to program the bloody thing. I will need to buy the addon program as I have 64 bit Windows 7 Home Premium, but how t=do I set up the comport? I have the MCP combo plugged into a usb on the back of my machine. Can anyone help?

[Andydigital]

Hi, it is simple plain English, have you actually tried following the instructions step by step? or did you just read through them and say "I cant do that". If you are stuck at a particular part please do ask, and please don't just say I'm stuck on the com port part, its a large step and there must be one particular section you don't quite understand, please do expand.

I would imagine you are having a problem understanding the virtual COM ports and how to enter the correct number in the FSUIPC.ini [VRInsight] section. Its actually quite simple when you know how. First plug the MCP Combo in an switch it on (FS doesn't need to be running) then start SerialFP2. If you look at the image below you will see the real COM port SerialFP2 is using to connect to the MCP Combi (known as FMER by SerialFP2)

1.

write the number down (Com 5 in this instance, it will be different for you though most likely) that appears next to Port we will need it later.

I have at least 5 VRI devices so I set up 5 virtual Com port pairs in VSPE.

2.

Below is how my FSUIPC.ini looks as a whole for my VRInsight hardware, I only use about 3 devices at once in my flying hence only 3 instances of serialFP2 loading automatically in the [Programs] section.

3. .

You should be able to work out what to do just from the images above but if you still aren't sure I'll try and explain it as simple a possible.

Image 1 above shows Com 5 as the real Com port. (this number will most likely be different on every machine)

Image 2 shows the virtual pair of Com ports FSUIPC will use (and which I choose) with that VRI device (MCP Combo in your instance Cathy) in this case I used Com 29 of the pair 28 --> 29, you could use 28 if you wished it really doesn't matter it just has to be one of the pair of numbers.

Image 3 the section I have highlighted shows COM 5 (the real port) associated with Com 29 (one of the virtual pair of com ports, you could use 28 or 29 here it doesn't matter)

The middle section [VRInsight.Mpanl] in image 3 isn't relevant to you by the way and can be left out of the FSUIPC.ini.

I hope that helps a little.

[CathyH]

Andy, thanks, YES, this exactly what I needed!

[CathyH]

[VRInsight]

1=COM3, COM4

[Programs]

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

Andy: I am having some problems above ius the entry from FSUIPC.INI.

Com three is the ACTUAL port the MCP combo is on, com 4 is the virtual

I get a cannot load configuration error and fsx freezes

THIS is then ent4ry from the shortcut in my start menu

"D:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe" -minimize –hide_splash D:\ComPair_24_56.vspe

:?: :( HELP!!!!!

[Andydigital]

I get a cannot load configuration error and fsx freezes

I presume this error is from VSPE?

I had problems using the command line for VSPE as shown in your example above and as shown by Pete when I put it in the Start Up folder, I had to remove –hide_splash before it would work and minimise doesn't work either even though I've left it in the command line.

It would have been better if you had quoted what your virtual pair was called too as it isn't clear what ComPair_24_56.vspe is supposed to mean. Why have one pair as 2<-->4 and another 5<-->6 (or is that not what 24_56 means), it would be better to stick to a convention (i.e. one odd and one even number per pair) to avoid confusion at a later date.

Also make absolutely certain your MCP is connected to your PC and switched on before you start FS otherwise FSUIPC will not be able to connect if you try switching on the MCP after FS has loaded.

[Pete Dowson]

I had problems using the command line for VSPE as shown in your example above and as shown by Pete when I put it in the Start Up folder, I had to remove –hide_splash before it would work and minimise doesn't work either even though I've left it in the command line.

Really? That's very odd. It works perfectly with that command line in two of my PCs -- one running Win7 Ultimate 64 and the other Win XP 32.

I wish you'd given me some feedback on VSPE command line problems so I could have put some warnings in the final documentation. If they are consistent on your system I think you ought to report them to Eterlogic so they can fix them.

It would have been better if you had quoted what your virtual pair was called too as it isn't clear what ComPair_24_56.vspe is supposed to mean. Why have one pair as 2<-->4 and another 5<-->6 (or is that not what 24_56 means), it would be better to stick to a convention (i.e. one odd and one even number per pair) to avoid confusion at a later date .

In my case the odd numbering came about because Windows seems to allocate real COM numbers rather randomly. For instance the MCP-Combi came up as COM5 no matter where I connected it, whilst the M-Panel (which arrived yesterday) came up as COM7. Weird. I have some other COM devices too. You have to be careful to assign truly free ones to VSPE. Maybe this is the problem here responsible for "cannot load configuration"? Best to go into Device Manager and find out which COM ports are free.

Alternatively I suppose you could start using virtual port numbers at some high value, like 20, to keep well clear of real ports.

As for FSX freezing -- I cannot imagine anything in any of this which could possibly freeze FSX, as everything is done is separate threads. There's nothing on any COM ports handled in FSUIPC's main FS thread routines. I'd like to see the log as far as it got -- because nothing VRInsight-wise is done in FSUIPC until FSX is "ready to fly". That doesn't at all relate to a "cannot load configuration" problem in VSPE, which would have occurred many minutes beforehand, surely?

Best Regards

Pete

[Andydigital]

I wish you'd given me some feedback on VSPE command line problems so I could have put some warnings in the final documentation.

I wasn't sure if it was user error or not and I'd forgotten about it in the mean time Pete.

[Andydigital]

Can you see anything wrong with this Pete.

"C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe" -minimize –hide_splash c:/VRI.vspe

As that's what I've just tried and it always comes up with that error "cannot load configuration"

Your path C:/is wrong. Windows uses \ not / for path separators. It's Unix which uses /.

Pete

[Andydigital]

Later;

Well this is bloody odd, now that I've removed the hide-splash section again the minimise facility has started working again, I simply tried logging out of W7 and back in a few times to test the command lines and now it will minimise even after a cold boot, VERY STRANGE!.

[CathyH]

The pair naming was because I orginally made 2 pairs, but dleeted one. I will try again and get back to you

Cathy

[CathyH]

I am still locking up, and getting this

130931 VRI driver port 1 "COM4" failed to open

130931 VRI port 1 "COM3" failed to open

I made one pair "Compairs24" where 2and 4 are the two virtual com ports

This is the section from FSUIPC

[VRInsight]

1=COM3,COM4

[Programs]

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

THIS is the section from the desktop

"D:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe" -minimize –hide_splash D:\ComPairs24.vspe

Where am I going wrong?

[CathyH]

I tired removing the "Hide Splash" parameter, still freezing. The screen opens, then I get the little circular "Working" icon, actually, I get two!, then it freezes and dumps to Winbdows

[Andydigital]

Please make sure you have the MCP plugged in and switched on before you start the simulator, also do not start SerialFP2 manually otherwise it wont work as SerialFP2 will take ownership of the com ports before FSUIPC gets chance to piggy in the middle. You also need to go into device manager and make sure that those com ports aren't already in use by some other device, you would be better off making a virtual pair of something like 11 <--> 12 rather than low numbers as they are more likely to be in use already.

I tired removing the "Hide Splash" parameter, still freezing. The screen opens, then I get the little circular "Working" icon, actually, I get two!, then it freezes and dumps to Winbdows

Try launching VSPE by double clicking on your saved profile (ComPairs24.vspe) for now just to see if it will load it properly. Time for bed for me now.

[CathyH]

OK. will try, How do I set SerialFP to run in Auto mode?

[CathyH]

OK, I am officially stumped! I can start VPSE manually and I get the screen saying that the emulation has intialized, BUT when I try to load it dumps me back out. This occurs wether I have loaded SerailFP2 or not, and although I have ticked the Load automatically option, it will not do so, I am using RC version 2.520

[CathyH]

OK, I made one pair COM21&COM22. I renaimed COM21 to COM3, the actual port my MCP Combi is on, and I CAN get the ports to load ok, provided I click on the shortcut. The Default flight loads, then freezes, then CTD. I am running FP2.520RC. I am gewtting closer, hopefully you can coach me thru this :D

[CathyH]

Please make sure you have the MCP plugged in and switched on before you start the simulator, also do not start SerialFP2 manually otherwise it wont work as SerialFP2 will take ownership of the com ports before FSUIPC gets chance to piggy in the middle. You also need to go into device manager and make sure that those com ports aren't already in use by some other device, you would be better off making a virtual pair of something like 11 <--> 12 rather than low numbers as they are more likely to be in use already.

I tired removing the "Hide Splash" parameter, still freezing. The screen opens, then I get the little circular "Working" icon, actually, I get two!, then it freezes and dumps to Winbdows

Try launching VSPE by double clicking on your saved profile (ComPairs24.vspe) for now just to see if it will load it properly. Time for bed for me now.

Andy, here is my COMPLETE INI File

[General]

UpdatedByVersion=4600

History=XGX9J1BOXJKK8MAJO70LI

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,COM22

[Programs]

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

[CathyH]

I can't seem to see my posts!

[CathyH]

Found them, my internet connection went down :(

[Pete Dowson]

I am still locking up, and getting this

130931 VRI driver port 1 "COM4" failed to open

130931 VRI port 1 "COM3" failed to open

With the ports failing to open, FSUIPC is doing nothing regarding anything VRInsight-wise. What on Earth is "locking up" and what exactly do you mean by that? You haven't said either time -- surely not FS as it really isn't getting involved at all with no COM ports to handle.

If COM3 and COM4 fail to open then they are not available to be opened. It is as simple as that. Either they don't exist, or something has them open already.

Please show the WHOLE of the FSUIPC log files, not extracts -- close FS down first if it isn't "locked up".

Regards

Pete

[CathyH]

Pete: Here is the complete log:

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

47 System time = 11/03/2010 11:15:13

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

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

812 LogOptions=00000000 00000051

812 SimConnect_Open succeeded: waiting to check version okay

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

7566 Initialising SimConnect data requests now

7566 FSUIPC Menu entry added

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

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

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

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

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

65630 VRI port 1 "COM3" opened

65630 VRI driver port 1 "COM22" also opened

65630 VRI port 1 "COM3" failed to open

65677 VRI port 1 "COM3" failed to open

65739 VRI port 1 "COM3" failed to open

65802 VRI port 1 "COM3" failed to open

65864 VRI port 1 "COM3" failed to open

65926 VRI port 1 "COM3" failed to open

65989 VRI port 1 "COM3" failed to open

66051 VRI port 1 "COM3" failed to open

66114 VRI port 1 "COM3" failed to open

66176 VRI port 1 "COM3" failed to open

66238 VRI port 1 "COM3" failed to open

66301 VRI port 1 "COM3" failed to open

66363 VRI port 1 "COM3" failed to open

66426 VRI port 1 "COM3" failed to open

66488 VRI port 1 "COM3" failed to open

66550 VRI port 1 "COM3" failed to open

66613 VRI port 1 "COM3" failed to open

66675 VRI port 1 "COM3" failed to open

66738 VRI port 1 "COM3" failed to open

66800 VRI port 1 "COM3" failed to open

66862 VRI port 1 "COM3" failed to open

66925 VRI port 1 "COM3" failed to open

66987 VRI port 1 "COM3" failed to open

67050 VRI port 1 "COM3" failed to open

67112 VRI port 1 "COM3" failed to open

67174 VRI port 1 "COM3" failed to open

67237 VRI port 1 "COM3" failed to open

67299 VRI port 1 "COM3" failed to open

67362 VRI port 1 "COM3" failed to open

67424 VRI port 1 "COM3" failed to open

67486 VRI port 1 "COM3" failed to open

67549 VRI port 1 "COM3" failed to open

67611 VRI port 1 "COM3" failed to open

67674 VRI port 1 "COM3" failed to open

67736 VRI port 1 "COM3" failed to open

67798 VRI port 1 "COM3" failed to open

67861 VRI port 1 "COM3" failed to open

67923 VRI port 1 "COM3" failed to open

67986 VRI port 1 "COM3" failed to open

68048 VRI port 1 "COM3" failed to open

68110 VRI port 1 "COM3" failed to open

68173 VRI port 1 "COM3" failed to open

68235 VRI port 1 "COM3" failed to open

68298 VRI port 1 "COM3" failed to open

68360 VRI port 1 "COM3" failed to open

68422 VRI port 1 "COM3" failed to open

68485 VRI port 1 "COM3" failed to open

68547 VRI port 1 "COM3" failed to open

68610 VRI port 1 "COM3" failed to open

68672 VRI port 1 "COM3" failed to open

68734 VRI port 1 "COM3" failed to open

68797 VRI port 1 "COM3" failed to open

68859 VRI port 1 "COM3" failed to open

68922 VRI port 1 "COM3" failed to open

68984 VRI port 1 "COM3" failed to open

69046 VRI port 1 "COM3" failed to open

69109 VRI port 1 "COM3" failed to open

69171 VRI port 1 "COM3" failed to open

69234 VRI port 1 "COM3" failed to open

69296 VRI port 1 "COM3" failed to open

69358 VRI port 1 "COM3" failed to open

69421 VRI port 1 "COM3" failed to open

69483 VRI port 1 "COM3" failed to open

69546 VRI port 1 "COM3" failed to open

69608 VRI port 1 "COM3" failed to open

69670 VRI port 1 "COM3" failed to open

69733 VRI port 1 "COM3" failed to open

69795 VRI port 1 "COM3" failed to open

69858 VRI port 1 "COM3" failed to open

69920 VRI port 1 "COM3" failed to open

69982 VRI port 1 "COM3" failed to open

70045 VRI port 1 "COM3" failed to open

70107 VRI port 1 "COM3" failed to open

70170 VRI port 1 "COM3" failed to open

70232 VRI port 1 "COM3" failed to open

70294 VRI port 1 "COM3" failed to open

70357 VRI port 1 "COM3" failed to open

70419 VRI port 1 "COM3" failed to open

70482 VRI port 1 "COM3" failed to open

70544 VRI port 1 "COM3" failed to open

70606 VRI port 1 "COM3" failed to open

70669 VRI port 1 "COM3" failed to open

70731 VRI port 1 "COM3" failed to open

70794 VRI port 1 "COM3" failed to open

70856 VRI port 1 "COM3" failed to open

70918 VRI port 1 "COM3" failed to open

70981 VRI port 1 "COM3" failed to open

71043 VRI port 1 "COM3" failed to open

71106 VRI port 1 "COM3" failed to open

71168 VRI port 1 "COM3" failed to open

______________________________________________________________________________________________

HERE is my Complete INI File:

[General]

UpdatedByVersion=4600

History=80D34LV4R3A1HHU38RK5G

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

[Pete Dowson]

Pete: Here is the complete log:

...

65630 VRI port 1 "COM3" opened

65630 VRI driver port 1 "COM22" also opened

65630 VRI port 1 "COM3" failed to open

65677 VRI port 1 "COM3" failed to open

etc..

AhaNOW things become clearer. COM3 is opened okay, as also is COM22, But then something is continually trying to open COM3 again! Ouch.

HERE is my Complete INI File:

With nothing at all to show why it is looping trying to open COM3 again and again! How strange.

[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.

Yes, all that is okay. sorry, I am at a loss at present. I cannot see how this can happen. There's no other user (out of at least the 10 in the Beta group, and I) who've had any such problem as this. I'll need to re-examine my code, see if I can find a clue as to what might be happening.

I might need to supply you with a special test version of FSUIPC with extra logging. Is that okay? Could you send me an email please, so I can send a link to a test version by email? To petedowson@btconnect.com . I'll get onto this tomorrow (it is late here now) and get back to you.

Regards

Pete

[CathyH]

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