Both FSUIPC and WideFs waiting

[veelo]

Hi Peter,

Have had heaps of problems with the new update of Windows 10 (version 109), even to the point I had to make a clean install of Windows and so all the rest.

Have all working again= P3Dv4.4 , ASP3D etc.

But cannot get FSUIPC and WideFs working.

Widefs Client log: 

********* WideClient Log [version 7.151] Class=FS98MAIN *********
Date (dmy): 07/12/18, Time 09:02:59.960: Client name is PIETER-2
      203 LUA: "D:\Widefs\Initial.LUA": not found
      250 Attempting to connect now
      250 Trying to locate server: Need details from Server Broadcast
      250 Failed to connect: waiting to try again
     1250 Attempting to connect now
    22250 Trying to locate server: Need details from Server Broadcast

  1365656 ****** End of session performance summary ******
  1365656 Total time connected = 0 seconds
  1365656 Reception maximum:  0 frames/sec, 0 bytes/sec
  1365656 Transmission maximum:  0 frames/sec, 0 bytes/sec
  1365656 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

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

FSUIPC log: Running inside Prepar3D v4
Module base=7FFC72770000
Windows 10 Pro 64 Bit reported as Build 17763, Release ID: 1809 (OS 10.0)
Prepar3D.exe version = 4.4.16.27077
Reading options from "E:\Prepar3D\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Pieter Veelo"
User Addr="p_veelo@yahoo.co.uk"
FSUIPC5 Key is provided
WideFS7 Key is provided
       16 System time = 07/12/2018 09:36:18
       32 FLT UNC path = "\\PIETERP3D\Users\p_vee\Documents\Prepar3D v4 Files\"
       32 Using DialogMode
       32 FS UNC path = "\\PIETERP3D\Prepar3D\"
       79 ---------------------- Joystick Device Scan -----------------------
      125 Product= G-Throttles
      125    Manufacturer= Leo Bodnar
      125    Serial Number= B38962
      125    Vendor=16C0, Product=27D3 (Version 1.36)
      375    GUIDs returned for product: VID_16C0&PID_27D3:
      375       GUID= {9BF98AE0-F7F9-11E8-8006-444553540000}
      375       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V4095,X4095,Y4095,Z4095
      375 Product= CH PRO PEDALS USB 
      375    Manufacturer= CH PRODUCTS
      375    Vendor=068E, Product=00F2 (Version 0.0)
      375    GUIDs returned for product: VID_068E&PID_00F2:
      375       GUID= {9C039D00-F7F9-11E8-800B-444553540000}
      375       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      375 Product= Saitek Pro Flight Yoke
      375    Manufacturer= Saitek
      375    Vendor=06A3, Product=0BAC (Version 3.3)
      375    GUIDs returned for product: VID_06A3&PID_0BAC:
      375       GUID= {9C12DF40-F7F9-11E8-8013-444553540000}
      375       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      375 -------------------------------------------------------------------
      391 Device acquired for use:
      391    Joystick ID = 0 (Registry okay)
      391    0=G-Throttles
      391    0.GUID={9BF98AE0-F7F9-11E8-8006-444553540000}
      391 Device acquired for use:
      391    Joystick ID = 1 (Registry okay)
      391    1=CH PRO PEDALS USB
      391    1.GUID={9C039D00-F7F9-11E8-800B-444553540000}
      391 Device acquired for use:
      391    Joystick ID = 2 (Registry okay)
      391    2=Saitek Pro Flight Yoke (USB)
      391    2.GUID={9C12DF40-F7F9-11E8-8013-444553540000}
      391 -------------------------------------------------------------------
      407 LogOptions=00000000 00000001
      407 -------------------------------------------------------------------
      407 SimConnect_Open succeeded: waiting to check version okay
      407 Opened separate AI Traffic client okay
      407 ### PDKmodeHelper callback registered!
    13891 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0)
    13891 Initialising SimConnect data requests now
    13891 FSUIPC Menu entry added
    13891 ... Using Prepar3D with Academic License
    13922 \\PIETERP3D\Users\p_vee\Documents\Prepar3D v4 Files\ProSim.fxml
    13922 \\PIETERP3D\Users\p_vee\Documents\Prepar3D v4 Add-ons\ProSim-AR\SimObjects\Airplanes\ProSim737-800-2018 Professional\Prosim738_Pro.air
    32875 ### The user object is 'Prosim_AR_737_800_PRO_2018_Transavia_NC'
    32875 ### Mode is NORMAL
    33016 ### Mode: PAUSE on
   103547 Loading Complete ...
   103579 ### Mode is NORMAL
   104422 Aircraft loaded: running normally now ...
   104469 User Aircraft ID 1 supplied, now being used
   104766 System time = 07/12/2018 09:38:03, Simulator time = 14:00:01 (12:00Z)
   104766 Aircraft="Prosim_AR_737_800_PRO_2018_Transavia_NC"
   110766 -------------------- Starting everything now ----------------------
   110766 Starting WideServer now ...
   110797 ASN active function link set
   110797 Ready for ActiveSky WX radar with additional data
   114000 Advanced Weather Interface Enabled
   180922 Sim stopped: average frame rate for last 76 secs = 45.3 fps
   180922    Max AI traffic was 0 aircraft
   205891 Starting WideServer now ...

Tried everything I could think of, like

Turning of all Firewalls and AV's

Redownloading FSUIPC5 and WideFS6

I can see that LUA: "D:\Widefs\Initial.LUA": not found

But do not know what to do to fix it.

Maybe again WINDOWS 10 v 109. I surely hope not as it took 2 days with the help of Prosim and OC helpdesks to get things going again.

Please advise,

[Pete Dowson]

24 minutes ago, veelo said:

Tried everything I could think of, like

First of all, the FSUIPC log isn't the correct one for WdeFS. I need the WideServer log (in the same folder).

Second, you say you tried everything, but did you read a little of the WideFS user guide. You don't need to read all of it, just the bit on Page 4 headed

Configure your Network
IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS!

You either need either to have all PCs in the same workgroup so that the clients cannot receive broadcasts from the server, OR you have to add ther ServerName (or ServerIPaddr) details, plus your Protocol selection (TCP ot UDP0 to the WideClient.INI file to tell it where to connect.

Changing operating systems on either PC will change the workgroup name.

Pete

 

[veelo]

Hi Peter,

Maybe I forgot to tell you but all 3 comp. are open to each other (ProSim) (see att)Network

Sorry I took the wrong log.

As far as the Servername see att.

WideClient.log

WideClient.log

WideClient0.log

WideServer.log

WideServer.log

[Pete Dowson]

1 hour ago, veelo said:

Maybe I forgot to tell you but all 3 comp. are open to each other (ProSim) (see att)Network

Sorry, what do you mean "open to each other"? What has this to do with wideFS? And what am I supposed to learn from your screen grab? I don't need to know your computer names!!

The client logs say:

      250 Attempting to connect now
      250 Trying to locate server: Need details from Server Broadcast
      250 Failed to connect: waiting to try again
     1250 Attempting to connect now
    22250 Trying to locate server: Need details from Server Broadcast

and the Server log says

    15219 Initialising TCP/IP server
    15219 Initialising UDP/IP server
    16000 Broadcasting service every 1000 mSecs
  1373828 Closing down now ...

So, the Server is broadcasting its details, but they are not being received by the Clients, so the latter does not knw how to connect to the Server.

This happens when the WorkGroup name is different on the server compared with the clients. Windows does not send broadcasts outside of its workgroup.

So, as I already said, you either need to change the workgroup name in the Server to match the Clients, OR enter the server details into the Client INI files. Then it doesn't need to see the broadcasts.

I don't think you really read my previous reply, or read that section in the documentation. Please do. The documentation is supplied for a purpose.

Pete