Jump to content
The simFlight Network Forums

WideFS - FSC - Plan-G


Recommended Posts

Hello Pete,

We really enjoy using your great products; FSUIPC and WideFS. Unfortunately we are having some issues with WideFS.

Our current setup is:

"Sentinel" and "Shadow" - Two powerful i7 rigs, running w7x64 and FSX Acceleration/SP2. Latest versions of FSUIPC and WideFS.

"Nimrod" - A P4-class XP machine with wideclient.

Our network is setup correctly as are all software packages. We are successfully able to connect WideClient to either Sentinel or Shadow and are able to manipulate the simulator sessions using our custom WideClient/FSUIPC touchscreen button map. GPSOut is configured to push data via WideServer/Client.

Unfortunately, when we try to use other software via WideFS, like FS Commander or Plan-G (tested multiple versions), we get errors from those software packages informing us that they cannot connect to the FS session. Use of flight planner software with direct interaction with the simulators is absolutely critical to our project.

[[sENTINEL AS WIDESERVER LOG]]

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 17/01/12, Time 19:54:17.323: Server name is SENTINEL

15834 Initialising TCP/IP server

15834 Initialising IPX/SPX server

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

15834 Failed to start IPX/SPX Server

15834 Initialising UDP/IP server

16115 Broadcasting service every 1000 mSecs

4133777 Connected to computer "SHADOW" running WideClient version 6.860 (IP=10.11.89.203) UDP

4444702 recvfrom failed: closing client! [Error=10054] Connection reset by peer (IP=10.11.89.203) UDP

4447994 Connected to computer "SHADOW" running WideClient version 6.860 (IP=10.11.89.203) UDP

4554652 Connected to computer "NIMROD" running WideClient version 6.860 (IP=10.11.89.103) UDP

5843641 recvfrom failed: closing client! [Error=10054] Connection reset by peer (IP=10.11.89.103) UDP

5991405 Close signalled to clients

5992497 Closing down now ...

Memory managed: Offset records: 4227 alloc, 4225 free

Read buffer usage: 1465 alloc, 1465 free, max in session: 1

Write buffer usage: 82550 alloc, 82550 free, max in session: 1

Throughput maximum achieved: 62 frames/sec, 1692 bytes/sec

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

Average receive rate from "NIMROD": 0 frames/sec, 18 bytes/sec

Average receive rate from "SHADOW": 0 frames/sec, 18 bytes/sec

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

[[sHADOW AS WIDECLIENT LOG]]

********* WideClient Log [version 6.86] Class=FS98MAIN01 *********

Date (dmy): 17/01/12, Time 21:08:23.289: Client name is SHADOW

2262 Attempting to connect now

2262 Trying UDP/IP addr 10.11.89.202, port 8001 ...

2262 UDP connectionless mode set up okay!

2262 LUA: "F:\WideFS\SENTINEL\Initial.LUA": not found

2356 Connection made: receiving okay!

1403604 ****** End of session performance summary ******

1403604 Total time connected = 1399 seconds

1403604 Reception maximum: 31 frames/sec, 897 bytes/sec

1403604 Reception average whilst connected: 27 frames/sec, 684 bytes/sec

1403604 Transmission maximum: 0 frames/sec, 20 bytes/sec

1403604 Transmission average whilst connected: 0 frames/sec, 20 bytes/sec

1403604 Max receive buffer = 572, Max send depth = 3, Send frames lost = 0

1403604 ********* Log file closed (Buffers: MaxUsed 4, Alloc 39645 Freed 39645 Refused 0) *********

I did get in touch with FS Commander about this, but since we spoke I have tested the lastes version and Plan-G with the same results, so I think we can discount this being an issue with that software. The thread of our discussion is here.

We really need to solve this problem as soon as possible and would appreciate any help you can give us in doing so.

All the best,

AoA.

Link to comment
Share on other sites

"Sentinel" and "Shadow" - Two powerful i7 rigs, running w7x64 and FSX Acceleration/SP2. Latest versions of FSUIPC and WideFS.

Actually you are running FSUIPC 4.703 which is about 10 m0nths old -- current is 4.758 or 4.761. But it wouldn't make any difference in this case.

Our network is setup correctly as are all software packages. We are successfully able to connect WideClient to either Sentinel or Shadow and are able to manipulate the simulator sessions using our custom WideClient/FSUIPC touchscreen button map. GPSOut is configured to push data via WideServer/Client.

Unfortunately, when we try to use other software via WideFS, like FS Commander or Plan-G (tested multiple versions), we get errors from those software packages informing us that they cannot connect to the FS session. Use of flight planner software with direct interaction with the simulators is absolutely critical to our project.

The fact that you are connecting successfully and using the connection certainly indicates that WideFS is working fine.The logs you supplied also confirm this. WideFS does not discriminate between its client applications.

I suspect that both FSC and PlanG not only need to talk to FS via WideFS and FSUIPC, but also need access to some of the FS folders in order to obtasin information about airports, scenery and so forth. You'll need to refer to their documentation to find out how to set file sharing up adequately for them to work. WideFs is merely a network extension of the FSUIPC interface, it is not a filesharing system. You have to rely on Windows' file sharing facilities and correct netowrk paths.

Please supply a complete FSUIPC4 log file too, with FSX closed beforehand, with any further queries.

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.