Jump to content
The simFlight Network Forums

HELP !!! : FSUIPC / WideFS and FS2004


Recommended Posts

Hello Everybody... :)

I am probably overlooking something obvious, but since I am more or less new to using WideFS and FSUIPC (and paying for them...) I would really like some help trying to get them working together with FS2004.

I installed all files concerned into the folders specified in their manuals :

FSUIPC.dll (v3.1.0) , WideServer.dll and WideServer.ini (v6.1.0) into FS2004/modules ;

WideClient.exe and WideClient.ini into Project Magenta folders on several networked pc's.

All Pc's used have fixed IP adresses (FS2004 PC : 192.168.123.25) and are connected via a Broadband/LAN Router. (network workes fine)

All harddrives used are fully shared.

The registration codes for FSUIPC and WideFS were succesfully entered in FS2004.

The WideServer.ini and WideClient.ini file were then modified as follows:

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

[Config]

Port=8002

UseTCPIP=Yes

Window=189,195,886,589 (only wideclient)

Visible=Yes (only wideclient)

ServerName=SIMULATOR-A

ServerIPAddr=192.168.123.25

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

After starting FS2004 (sim mode, not setup screen) and running WideClient on the network pc's, the status of WideClient remains "waiting for connection" for reasons unknown to me...

Running the very helpfull PMFileCheck tool on the network pc's(comes with Project Magenta) results in the following report:

(example: PC with Project Magenta PFD/ND "Simulator-B")

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

Standing by (Press button on the right)

Opening Connections

Local Path: E:\Program Files\PFD ND

Checking Computer and User Name

Local Computer Name: SIMULATOR-B

Local User Name: Jordan C. Tuinman

FSUIPC/WideFS found!

FSUIPC Version 0

FAIL - FMC Not Detected (CDU or MCDU)

FAIL - A/P NOT Detected (MCP or FCU)

Checking FS Path

FAIL - No FS Path reported

Checking PMNETDIR Path (FMC Generated Path)

Looking for INI files

Closing Everything

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

Since both FSUIPC and WideFS are found by PMFileCheck I think the network settings are OK up to the misterious "FS Path" wich is missing.

Non of the manuals I have read refers to a "FS Path" setting in the .ini files or anywere else. Please help me out !!??

Regards in advance,

Jordan Tuinman

The Netherlands

Link to comment
Share on other sites

After starting FS2004 (sim mode, not setup screen) and running WideClient on the network pc's, the status of WideClient remains "waiting for connection" for reasons unknown to me...

The reasons will be best found by checking the WideServer and WideClient.Log files. These will be found in the same folder as WideServer and WideClient, respectively.

Running the very helpfull PMFileCheck tool on the network pc's(comes with Project Magenta) results in the following report:

This tells me nothing useful, I'm afraid. It is best to ask PM questions at the PM support place. But show me the Log files which I can understand and we'll take it from there.

By the way, please always use the latest versions -- FSUIPC is 3.11 and WideFS is 6.101.

Regards,

Pete

Link to comment
Share on other sites

Dear Pete,

Thanks for the quick reply...

I included the log and .ini files of both WideServer and Wideclient, I hope you will find something in here.

Thanks for helping me out,

Jordan

The Hague, The Netherlands

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

********* WideClient.DLL Log [version 6.101] Class=FS98MAIN *********

Date (dmy): 27/10/03, Time 23:18:48.187: Client name is SIMULATOR-B

62 Attempting to connect now

2640 Reception maximum achieved: 0 frames/sec, 0 bytes/sec

2640 Max receive buffer = 0, Max send depth = 0

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

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

WideClient.ini

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

[Config]

Port=8002

UseTCPIP=Yes

Window=63,389,886,589

Visible=Yes

ServerName=SIMULATOR-A

ServerIPAddr=192.168.123.25

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

[user]

Log=Errors+

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

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

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

Using blocksize guide of 4096 bytes

Date (dmy): 27/10/03, Time 23:06:55.875: Server name is SIMULATOR-A

52438 Initialising server socket now

82516 Restarting service due to total lack of use

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

WideServer.ini

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

[Config]

Port=8002

UseTCPIP=Yes

ServerName=SIMULATOR-A

ServerIPAddr=192.168.123.25

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

[user]

Log=Errors+

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

Link to comment
Share on other sites

I included the log and .ini files of both WideServer and Wideclient

Date (dmy): 27/10/03, Time 23:18:48.187: Client name is SIMULATOR-B

62 Attempting to connect now

2640 Reception maximum achieved: 0 frames/sec, 0 bytes/sec

2640 Max receive buffer = 0, Max send depth = 0

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

You closed down the client after only 2.6 seconds? It can take longer than that before they connection is confirmed!

Here's a typical start of a WideClient Log, using TCP/IP:

********* WideClient.DLL Log [version 6.101] Class=FS98MAIN *********

Date (dmy): 28/10/03, Time 00:17:59.171: Client name is NEWLEFT

2484 Attempting to connect now

2578 Trying TCP/IP host "OFFCENTRE" ...

2578Okay, IP Address = 192.168.0.170

9750 Connection made okay!

Try deleting the IPAddress parameter from your WideClient.ini file. See if it can find your Server by name rather than address. You only need to give one in any case, and the name is less error-prone.

And you don't need to tell the server its own name and address. those parameters don't belong in there at all, though they won't do any harm.

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

Using blocksize guide of 4096 bytes

Date (dmy): 27/10/03, Time 23:06:55.875: Server name is SIMULATOR-A

52438 Initialising server socket now

82516 Restarting service due to total lack of use

And where's the rest of the Server's Log? There will be much more than this! If FS is closed down there will be a summary of WideServer's performance, just like when you closed down WideClient.

Are the times correct on both PCs? Was the Client actually started 12 minutes after the Server?

Please delete the IP address parameters, and also let it run for a few minutes, then tell me what is wrong!

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