Jump to content

CAN'T CONNECT WIDE FS WITH FSX


Recommended Posts

I correctly installed the FSUIPC 4.12 on FSX and register. I configure the wideclient.ini correctly and when y try to connect, they seems to connect Ok buy a few seconds later they disconnect and reconect again. On the FSX bar, each time the wideclient reconects, they show a new conection, as if another PC conects FSX, and they show me 3, 4 ,5 connections.

Any ide why?

here are my files:

WIDECLIENT.INI

; PLEASE SEE WideFS documentation for parameter details

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

[Config]

Port=8002

Port2=9002

Window=164,223,886,589

Visible=Yes

ServerName=santiagofs

Protocol=TCP

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

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

[user]

Log=Errors+

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

WIDECLIENT.LOG

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

Date (dmy): 19/06/07, Time 12:02:17.140: Client name is SEMPRON3

203 Attempting to connect now

219 Trying TCP/IP host "santiagofs" port 8002 ...

219Okay, IP Address = 192.168.1.107

219 Connection made okay!

36562 Timed out response: connection assumed lost!

36562 Ready to try connection again

36625 Timed out response: connection assumed lost!

37562 Attempting to connect now

37562 Connection made okay!

55750 Timed out response: connection assumed lost!

55750 Ready to try connection again

55812 Timed out response: connection assumed lost!

56750 Attempting to connect now

56750 Connection made okay!

63765 ****** End of session performance summary ******

63765 Total time connected = 63 seconds

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

63765 Reception average whilst connected: 0 frames/sec, 0 bytes/sec

63765 Transmission maximum: 0 frames/sec, 108 bytes/sec

63765 Transmission average whilst connected: 0 frames/sec, 21 bytes/sec

63765 Max receive buffer = 0, Max send depth = 1, Send frames lost = 0

63765 ********* Log file closed (Buffers: MaxUsed 1, Alloc 30 Freed 30 Refused 0) *********

I ATTACHED A PHOTO OF THE FSX BAR WITH A CONECTION OF ONE PC. as yoy can see its like if there are 3 PC conected.

PLEASE ANY HELP

post-20758-128689532192_thumb.jpg

Link to comment
Share on other sites

I correctly installed the FSUIPC 4.12 on FSX and register. I configure the wideclient.ini correctly

If you are using Windows XP all round you should have no need to touch that INI file. What did you change?

they seems to connect Ok buy a few seconds later they disconnect and reconect again. On the FSX bar, each time the wideclient reconects, they show a new conection, as if another PC conects FSX, and they show me 3, 4 ,5 connections.

Any ide why?

Well, the reason for the apparent increase in the number of connections is actually explained fairly clearly in the documentation. As to what it is trying to reconnect, let's see:

36562 Timed out response: connection assumed lost!

36562 Ready to try connection again

36625 Timed out response: connection assumed lost!

37562 Attempting to connect now

37562 Connection made okay!

55750 Timed out response: connection assumed lost!

55750 Ready to try connection again

55812 Timed out response: connection assumed lost!

56750 Attempting to connect now

56750 Connection made okay!

OkayWideClient says it is timing out waiting for data from the Server. That is why it is trying to reconnect.

What did the WideServer Log show? This is only half the story!

I ATTACHED A PHOTO OF THE FSX BAR WITH A CONECTION OF ONE PC. as yoy can see its like if there are 3 PC conected.

There's no need for a photo. Why not just read the explanation in the documentation? Here, I'll reproduce it for you to save you all the bother:

Note that the number of current connections is shown in the title bar of Flight Simulator. This may fluctuate if responses to clients aren't currently being sent. This is because the client assumes that a lack of response for many tries means a disconnected link, so opens a new one. The server detects disused links after a while, and closes them, but there's an overlapping period whilst more connections may actually be open than there are clients.

There. That was in the early section in the WideFS User Guide called "Running WideFS".

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.