Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Good morning,

I'm a 777 pitbuilder. Willing to use project magenta I installed FSUIPC and Wideserver.dll in the module folder of the main computer (along with the various .ini files). On the second computer Project magenta is installed with wideclient.exe and wideclient.ini (Run1="PMadress").When i open Wideclient, FS2004 detects 1 client and the status bar shows "connected". However PM does not connect and shows "Avionics off". It is the same problem with open source gauges like freeFD for example. I'm pretty sure I made no mistake in versions between Wideclient and wideserver and that the installation is clean

Thanks fo your time

squick

PS: both softs are registered

Posted
When i open Wideclient, FS2004 detects 1 client and the status bar shows "connected". However PM does not connect and shows "Avionics off". It is the same problem with open source gauges like freeFD for example. I'm pretty sure I made no mistake in versions between Wideclient and wideserver and that the installation is clean

What does the Wideclient Log say? When the programs "don't connect" what do they say? Maybe the WideServer Log would show something of interest too? What versions of wideServer, WideClient, FSUIPC?

Pete

Posted

I'm sorry for my late reply.

Here are the logs frome wideserver and wideclient. I just realised they're not from the same session and that the wideserver.log is quiet strange looking.

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

Date (dmy): 27/09/06, Time 18:09:53.734: Client name is ORDI2

94 Attempting to connect now

469 Server = ORDI1

485 Trying TCP/IP host "ORDI1" port 8002 ...

485Okay, IP Address = 192.168.1.7

485 Connection made okay!

4766 New Client Application: "pfd" (Id=352)

17297 ****** End of session performance summary ******

17297 Total time connected = 15 seconds

17297 Reception maximum: 24 frames/sec, 5275 bytes/sec

17297 Reception average whilst connected: 25 frames/sec, 4829 bytes/sec

17297 Transmission maximum: 4 frames/sec, 796 bytes/sec

17297 Transmission average whilst connected: 1 frames/sec, 134 bytes/sec

17297 Max receive buffer = 952, Max send depth = 4, Send frames lost = 0

17297 **************** Individual client application activity ****************

17297 Client 352 requests: 975 (Ave 65/sec), Data: 1065355 bytes (71023/sec), Average 1092 bytes/Process

17297 ********* Log file closed (Buffers: MaxUsed 5, Alloc 1380 Freed 1380 Refused 0) *********

and the server :

********* WideServer.DLL Log [version 6.51] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 27/09/06, Time 16:51:26.031: Server name is ORDI1

57907 Initialising TCP/IP server

58094 Initialising IPX/SPX server

58094 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

58094 Failed to start IPX/SPX Server

58344 Broadcasting service every 1 mSecs

59282 Incoming connection Accepted ok (skt=316)

59391 Connected to computer "ORDI2" running WideClient version 6.510 (skt=316)

349235 Error 10053: client socket disconnected at Client: removing (skt=316)

357328 Incoming connection Accepted ok (skt=464)

357375 Connected to computer "ORDI2" running WideClient version 6.510 (skt=464)

588157 Error 10053: client socket disconnected at Client: removing (skt=464)

679860 Incoming connection Accepted ok (skt=372)

679938 Connected to computer "ORDI2" running WideClient version 6.510 (skt=372)

716516 Error 10053: client socket disconnected at Client: removing (skt=372)

726578 Incoming connection Accepted ok (skt=464)

726703 Connected to computer "ORDI2" running WideClient version 6.510 (skt=464)

801516 Error 10053: client socket disconnected at Client: removing (skt=464)

865844 Incoming connection Accepted ok (skt=460)

865891 Connected to computer "ORDI2" running WideClient version 6.510 (skt=460)

882766 Error 10054: client socket disconnected at Client: removing (skt=460)

1101391 Closing down now ...

Memory managed: Offset records: 836 alloc, 836 free

Throughput maximum achieved: 24 frames/sec, 13575 bytes/sec

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

Average receive rate from "ORDI2": 0 frames/sec, 7 bytes/sec

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

I know this isn't much but we are really stuck on that. On the network everything seems ok. Both computers are in the same workgroup.

Thanks a lot

Posted

Here are the logs frome wideserver and wideclient. I just realised they're not from the same session and that the wideserver.log is quiet strange looking.

Unfortunately neither log is of any use because of this.

The client log shows PFD loading and everything running perfectly well -- for just 15 secoonds before you close it down. I hardly think 15 seconds is enough for PFD to get going properly. Even so an average frame rate of 25 is good, very good, and the PFD program made an average of 65 requests per second.

The Server log is totally irrelevant to the above, of course. It simply shows an FS session runninmg for 18 minutes, with the Client (ORD12) apparently restarting at irregular intervals. Since there's no matching client log there's no way of knowing why. It looks like you did it manually in some cases.

The first connection lasts for about 1 minute into the session for about 5 minutes with no problems, reconnecting only 8 seconds later. It lasted another 4 minutes then disconnected and reconnected a good 1.5 minutes later, this time for only 40 seconds.

And so on.

Whilst connected the performance was good, 24 frames per second, but of course it wasn't connected much.

There's no other information I can extract. The client log would show more.

Pete

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
×
×
  • 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.