FSUIPC and Wide FS for FSX Not Connecting

[AngeloCosma]

Hello Pete, I was told to contact you after me and a freind trouble-shooted for a while trying to get Wide FS for FSX to communicate with my Laptop to my FSX PC. First lets get the details out of the way. My FSX PC is Windows 7 64 Bit, and my Laptop is Vista 32. My ISP is AT&T and my router is a 2Wire 3800HGV-B. None of my PCs are hardwired, there are all on a secured wirless network. We went over the .ini files to set the IP adresses and so-forth we made sure that the IP was correct. My freind recomended that i open ports 8002 and 9002 to port forward on my router but i couldn't figure out how. Also I will include WideClient.ini and Wideserver.ini files maybe they can explain the situation better than I can.

WideClient.ini

[Config]

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port=8002

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

Window=75,81,601,491

WideServer.ini

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

Thats all I got for now Pete, I very much appreciate your help.

Angelo Cosma

[Pete Dowson]

My FSX PC is Windows 7 64 Bit, and my Laptop is Vista 32.

And are they in the same workgroup, as instructed in the "configuring your network" section of the User Guide?

We went over the .ini files to set the IP adresses and so-forth

If the Network is okay and both PCs are in the same workgroup you shouldn't have to make any changes whatsoever. I don't know what you mean by "and so forth", but you only need to set the Server name or IP address and the Protocol if you insist on keeping your PCs in different workgroups.

My freind recomended that i open ports 8002 and 9002 to port forward on my router but i couldn't figure out how.

Sorry, nor do I, and I don't know what that means.

Also I will include WideClient.ini and Wideserver.ini files maybe they can explain the situation better than I can.

No, they explain nothing about what is happening on your system because they are simply the parameters defaulted and used by WideFS in any case, so I know them well (I did write them after all). The files which tell us what is happening are the Log files, one of which is always produced by both parts. So show me those instead.

Incidentally, although you said "We went over the .ini files to set the IP adresses and so-forth" in fact there is no sign at all of any such parameters being set in the copy of the INI you showed! Seems you were editing something completely different and not related to WideFS?

Regards

Pete

[AngeloCosma]

Hello Pete, thanks for getting back to me, I read your post and went over what you mentioned. Both PC's my FSX and Server are n the same "WORKGROUP." Let me put up the correct .ini file, I see what you mean, so heres the right one:

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=145,251,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

Angelo: Protocol=TCP

ServerIPAddr=192.168.1.84

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

The Wide Server.ini hasn't changed.

And also as you requested here are the WideClient.log and WideClient0.logs

0.log:

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 13/06/10, Time 13:02:38.020: Client name is ANGELO-PC

187 Attempting to connect now

5741 Trying to locate server: Protocol not yet decided

5741 Failed to connect: waiting to try again

7784 Attempting to connect now

174050 Trying to locate server: Protocol not yet decided

232238 ****** End of session performance summary ******

232238 Total time connected = 0 seconds

232238 Reception maximum: 0 frames/sec, 0 bytes/sec

232238 Transmission maximum: 0 frames/sec, 0 bytes/sec

232238 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

232238 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

.log:

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 16/06/10, Time 12:03:47.744: Client name is ANGELO-PC

343 Attempting to connect now

5913 Trying to locate server: Protocol not yet decided

5913 Failed to connect: waiting to try again

6662 ****** End of session performance summary ******

6662 Total time connected = 0 seconds

6662 Reception maximum: 0 frames/sec, 0 bytes/sec

6662 Transmission maximum: 0 frames/sec, 0 bytes/sec

6662 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

6662 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Hope there's more info here now to continue troubleshooting. Thanks again for helping me out Pete.

Angelo Cosma

[Pete Dowson]

Both PC's my FSX and Server are n the same "WORKGROUP."

That's the workgroup name, is it, "WORKGROUP"?

Let me put up the correct .ini file, I see what you mean, so heres the right one:

Well you certainly have an error in that file:

Angelo: Protocol=TCP

ServerIPAddr=192.168.1.84

The line "Angelo: ..." will be ignored as "Angelo: Protocol" isn't a known keyword. Therefore you've not specified the Protocol, and you must do if you specify a ServerName or ServerIPAddress because those parameters make it ignore the Server broadcasts which tell the Client where it is and what protocol to use.

If both your PCs are in the same workgroup, as you say, why are you specifying a ServerIPAddr parameter anyway? It shouldn't be needed.

And also as you requested here are the WideClient.log and WideClient0.logs

No, the Wideclient0.log is simply the previous WideClient.log. the Server part of the story is told in the WideServer.log file of course, which you've omitted.

5741 Trying to locate server: Protocol not yet decided

5741 Failed to connect: waiting to try again

7784 Attempting to connect now

174050 Trying to locate server: Protocol not yet decided

There's the problemremove the ServerIPAddr parameter from the client INI, or correct the Protocol line. You need to be more careful when editing files, though really you should not need to as defaults work fine in one workgroup.

Be aware to that unless you've fixed your server's IP address as 192.168.1.84 you would be better off specifying the Server name, or nothing at all. IP addresses assigned by routers can change.

Regards

Pete

[AngeloCosma]

The workgroup name is actually called WORKGROUP.

Here is the WideServer.log

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 16/06/10, Time 01:35:38.273: Server name is ANGELO-PC

15647 Initialising TCP/IP server

15647 Initialising IPX/SPX server

15647 IPX/SPX socket() failed [Error=10044] Socket type not supported

15647 Failed to start IPX/SPX Server

15647 Initialising UDP/IP server

16256 Broadcasting service every 1000 mSecs

2180333 Closing down now ...

Memory managed: Offset records: 2180 alloc, 2178 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

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

I removed the, ServerIPAddr parameter from the client INI.

[Pete Dowson]

The workgroup name is actually called WORKGROUP.

Here is the WideServer.log

Okay. That shows no connection, no attempted connection shown either, properly matching the client logs you showed.

However, it shows something pretty bad. You have a Client named "ANGELO-PC" and a Server also named "ANGELO-PC". How do you think those can be distinguished on an Network. I don't think you should ever do that!

I removed the, ServerIPAddr parameter from the client INI.

And ...? Are you okay now? (You are being a bit cryptic).

If there is still no connection then rename one of ypur PCs. All PCs on a Local Network must have different names -- that is the point of names, after all, to distinguish things.

If still no joy, I will need to see the WideClient and WideServer logs from the revised attempt.

Otherwise, if you are happily connecting now, please say so. The thread should be concluded properly, please.

I am going to bed now, so it'll be tomorrow when I see your answer, either way.

Regards

Pete

[AngeloCosma]

Ok, I renamed all my PC's, to now "Upstairs" and the other "Laptop."

I removed the, ServerIPAddr parameter from the client INI.

And ...? Are you okay now? (You are being a bit cryptic).

That didn't change anything then or now I tried once with it in the .ini and once without it. Server Logs were the same for both.

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 16/06/10, Time 20:59:43.107: Client name is LAPTOP

234 Attempting to connect now

1232 Trying to locate server: Need details from Server Broadcast

1232 Failed to connect: waiting to try again

3245 Attempting to connect now

68110 Trying to locate server: Need details from Server Broadcast

442107 ****** End of session performance summary ******

442107 Total time connected = 0 seconds

442107 Reception maximum: 0 frames/sec, 0 bytes/sec

442107 Transmission maximum: 0 frames/sec, 0 bytes/sec

442107 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

442107 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Here is the

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 16/06/10, Time 21:13:51.414: Server name is UPSTAIRS

15069 Initialising TCP/IP server

15069 Initialising IPX/SPX server

15069 IPX/SPX socket() failed [Error=10044] Socket type not supported

15069 Failed to start IPX/SPX Server

15069 Initialising UDP/IP server

16099 Broadcasting service every 1000 mSecs

Thanks again

Angelo Cosma

[Pete Dowson]

That didn't change anything then or now I tried once with it in the .ini and once without it. Server Logs were the same for both.

The broadcasts are not working at all. This either means your network is not working or one of your systems is faulty (a corrupted operating system). Both Vista and Win7 support Broadcasting and that will work, even through firewalls, provided both PCs are in the same workgroup.

So, first off, does your Network actually work? Using Explorer can you share files or folders and see and access them from the other PC?

Have you by any chance configured the Win7 PC to only use the new (in Win7) "HomeGroup" network configuration? If so then I don't think you can link to it from any non-Windows 7 PCs -- they all then need to be Windows 7. If you have done such a thing I think you will have to delete or undo it and configure a non-"HomeGroup" type of network.

Assuming the Network is actually working but for some reason the Broadcasting doesn't (which would be the first time I ever heard of such an anomaly), then you could try again to get the connection working by getting the parameters correct. Add

ServerName=Upstairs

Protocol=TCP

to the [Config] section of the WideClient.INI.

Even if this doesn't work, it will at least try to connect (currently, because of the lack of broadcasts, it is not even able to try). The log files might then tell us more. If you know your IP address is fixed then you could also try:

ServerIPAddr=n.n.n.n (whatever it is)

Protocol=TCP

Regards

Pete

[CAT51]

Hello,

My config: Computeur Master's with XP, FSX, FSUIPC4 and WIDEFS7 registered

My config Computeur Slave: GA panel, Wide and SDK registered

I do not manage to connect on the network GA panel

Can you give yourself an instructions for use

Thank you

[Pete Dowson]

Hello,

My config: Computeur Master's with XP, FSX, FSUIPC4 and WIDEFS7 registered

My config Computeur Slave: GA panel, Wide and SDK registered

I do not manage to connect on the network GA panel

Can you give yourself an instructions for use

Thank you

Have you read the previous help in this thread? If you have a different problem please start a new thread. In either case please show the WideServer.Log, WideClient.LOG and FSUIPC4.Log files. Also, I don't know the program "GA Panel" so please explain what this is and confirm it uses FSUIPC.

Regards

Pete

[dfordis]

Dear Pete,

I am having a similar problem. I have bought FDC Live Cockpit from Flightsim.com and bought the downloadable version. The first time I ran it, it went awesome! Everything lined up perfectly with FSX. But when i started a new flight and tried to connect my aircraft to my FSX aircraft (same as, when everything went smooth (Boeing 737-800)) it told me "Incorrect FSUIPC, or not FSUIPC". I don't understand why everything worked great the first time and i changed nothing, nothing is working. I have downloaded you FSUIPC 4.6.00 from the internet and still isn't making a difference. I am not a computer savvy person, but i know enough t get around. Please help me. I am an aspiring pilot and i wish to have everything working smoothly every time. I have spent a lot of money on all of my add-ons (FDC included, NOT cheap). What do i need to do?

DJ Fordis

Lafayette, LA, USA

PS: if you wouldn't mind e-mailing me instead of this forum, i would much appreciate it. I understand e-mail and find it easier to navigate through e-mial a lot more

my email is djfordis@gmail.com

thank you soooooo much!

[Pete Dowson]

I am having a similar problem. I have bought FDC Live Cockpit from Flightsim.com and bought the downloadable version. The first time I ran it, it went awesome! Everything lined up perfectly with FSX. But when i started a new flight and tried to connect my aircraft to my FSX aircraft (same as, when everything went smooth (Boeing 737-800)) it told me "Incorrect FSUIPC, or not FSUIPC".

You've evidently not read the thread you are appending to nor even its title, as the problem here is a connection between PCs on a network. You mention no network nor WideFS, so how is it "similar"?

I don't understand why everything worked great the first time and i changed nothing, nothing is working.

It is simply not possible for software to work one time and with no change whatsoever, in software or hardware, not work again. Something has changed. But you provide no information so I cannot tell.

Are you running on a Network or not?

If you are, is WideFS connecting? What does the title bar in WideClient say? I need to see the WideClient and WideServer Log files -- the WideClient one is in the folder in which you placed WideClient. The WideServer one is in the FSX Modules folder.

Either way, WideFS use or not, I also need to see the FSUIPC4 log file -- you'll find this in the FSX Modules folder too. Close FSX first.

PS: if you wouldn't mind e-mailing me instead of this forum, i would much appreciate it. I understand e-mail and find it easier to navigate through e-mial a lot more

But it helps no one else to keep things private, and it makes much more work for me as a consequence. You only have to deal with me, I have to deal with thousands or users.

my email is djfordis@gmail.com

I'll send you a link to this reply. That's the most I am going to do via email unless things need to be confidential. I hope you understand.

Regards

Pete

[dfordis]

here is what I think you are looking for. And i apologize for not being similar with the topics. I saw not connecting with FSX and thought that was similar. Here is that file from my FSX-Modules folder.

Installer for FSUIPC4.DLL version 4.60a

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

AppPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.600 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\fordis\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\fordis\AppData\Roaming"

Found FSX.CFG in "C:\Users\fordis\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\fordis\Application Data\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Contacts\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Cookies\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Desktop\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Downloads\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Favorites\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Links\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Local Settings\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Music\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\My Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\NetHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Pictures\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\PrintHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Recent\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Saved Games\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Searches\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\SendTo\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Start Menu\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Templates\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Tracing\Roaming"

No FSX.CFG there

Looking in "C:\Users\fordis\Videos\Roaming"

No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix programno longer relevant

===========================================================

All installer tasks completed okay!

[Pete Dowson]

here is what I think you are looking for.

No, that's the FSUIPC4 installer log.

In the same folder there should be a file "FSUIPC4.LOG". That will show the run-time situation of FSUIPC.

One thing first though. Are you using a paid-for registered FSUIPC4? If so please check that your windows system date is correct.

Secondly, when in FSX flight mode is there a menu item, right-most, called "Add-Ons"? If so, see if FSUIPC is listed there.

Regards

Pete