Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Pete,

First I want to say thanks for your program.  I have been using it for about 5 years with my sim starting with FSX and now P3D - it has been a great help with all my a/c addon control settings.  This week I got a new laptop but it is Win10 where before my client was on Win7 and so is my Sim computer.  FSUIPC and WideClient had both been working all that time with Win7.  Now that the client is on Win10 I have not been able to get them to connect.   I had a network tech set up my network to share files from my Win7 Sim with my Win10 client.  I can open and write to folders on my Sim machine from the laptop client.   But right now it is on network connections not the home group setup. 

My questions are about the impact of Win10 and connection of FSUIPC and WideClient.  Does Win10 require any special settings or sharing?   Does it specifically require the Homegroup to be set up and working?  I have searched this forum for info and didn't find anything specific to this issue as far as I could tell.  I referred back to the install manual and it talks about the homegroup so hence my question about specifically needing it or just network sharing.  To confirm my sharing I was just able to open the P3D Modules folder and copy the FSUIPC4.ini file from my laptop client over the network.

Anything you can point me to would be greatly appreciated so I can get my setup connecting again.  I can send you any files that would help with this but I did look at the Wideclient log and the last line is - 22515 Trying to locate server: Need details from Server Broadcast.   The last line of the Wideserver.dll log is - Broadcasting service every 1000 mSecs.

Thanks,
Jerry

Posted

Hi,

I found best to connect with Win8.x and Win10 is to use in [Config] section of WideClient.ini the ServerName= option
For example my Server Name of the FS-PC is TSR-DEV, so it looks like
[Config]
ServerName=TSR-DEV

...
Thomas
Posted

I tried that but it still did not connect. I got the waiting for connection message on both side but no connection.  I can send the text of the wideclient log or any other log if that would help.

Posted

Thomas,

I went back to the manual again and found I was missing a line per Pete's instructions.  Here is what I used and it is working now.  :)

ServerName=NameOfServer
Protocol=TCP    -(Missing line)

Thanks for getting me going in the right direction.

Jerry

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.