Watcher
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Watcher
-
-
I have solved the problem. After some investigation and some trail and error I was able to specify the TCP/IP protocol and address of the server in the client ini file, forcing the client to only connect through the local lan that was established through the crossover cable. Hope this helps others with the same problem.
-
I hace managed to get the crossover cable set up and providing a local connection. However, I am still having the client go away after various times. When I look at the client log it appears to be connecting to the local network based on the IP address. I have the WideServer and corresponding WideClient logs saved from my last terminated flight but have not been able to attach them. From the WideServer log it appears that the Client socket was unused for too long.
-
Yes, the cable that I am intending to buy is a crossover. I believe the cat numbers refer to speed.
-
I am connecting through a wireless network so it sounds like there is the most likely problem. Since I have the workgroups already set up and only two computers are involved would the connection work if a connected the two computers through a cat 6 crossover ethernet cable?
-
I recently added WIdeFS and moved Radar Contact and IYP to the client system. For the most part it works great but ocasionally my connection seems to drop. Once that happens I cannot restore the connection without ending my flight and sometimes I even have to close and restart the simulator. Is there any to restart the connection without haveing to do this? Also, the server sometimes continues to show waiting for clients when it is actually comunicating with a client. Other than this the problem it is working great.
-
As I pointed out earlier making the command line editable or providing a box to capture the startup directory would likely solve this problem. If I have to start SerialFP2 outside of your product there is no point to using it since I can do everything that it does (except for boost which seems to do more harm than good) by looking at the processes and making the core and affinity assignments there. The only advantage that Multicore Environment might provide for me is the ability to start a group and walk away until the last executable is running. Obviously I cannot do that in Multicore's current state.
-
Works fine outside of Multicore.
-
Reducing the priority does not help. What appears to be the problem is that SerialFP2 must start in a specific directory and there is no way in Multicore Environment to specify a start directory either by editing the execution string or through a specific box provided for that purpose.
-
I have just purchased and installed Multicore Environment Advanced and have encountered some problems. I tried your email support address but that fails so thought that I'd post here. I set up three programs: FSX, SerialFP2, and Radar Contact. Right now I am starting them each in turn rather than using groups. FSX is set for both of the two cores with boost on and high priority. FSX comes up ok. I then start SerialFP2, which is the software that drives a VRInsight M-Panel. I can see that SerialFP2 has started in Core 1 but it does not initialize the M-Panel. I then started Radar Contact in core 1. It seems to come up ok but when I press its start button the Menu shows at the top of the screen and is squeezed and it cannot be moved or resized because its top is overlaying the FSX menus. If I run these programs outside of Multicore Environment everything runs ok.
-
THank you for the reply. I will go ahead and download and install the 4.5 version.
-
I currently have FSUIPC version 4.3 installed. I am planning to purchase Air Hauler, which requires 4.5. When I look for an upgrade to FSUIPC the only thing that I can find is a download that inclides WIDEFS. If I download and install this version will my original key work? I purchased my 4.3 version in October 2008.
-
I have downloaded the the 4.30 version of FSUIPC4 for FSX ready to install. I have an older, unregistered, version installed. Should I just let the installer install over the old version? I intend to register the new version and would like to know the best way to do so. Any help with these two questions would be much appreciated.
Server shows waiting while client shows connected
in FSUIPC Support Pete Dowson Modules
Posted
I am not sure whether this is a problem or normal behaviour. I find that the WideFs Server at some random point in a flight changes from "1 Connected" to "Waiting fror Clients" while the Client still shows and is in fact connected and remains so for the rest of the flight. I am running Radar Contact and IYP on the client and they continue to work with FSX normally. As I am new to WideFs I am not sure whether this is what I am supposed to see other whether the Server should alwsys show the number of clients that are connected. My two systems are connected through an Ethernet Crossover cable so the connection should be stable.