Holy Cheese Posted December 9, 2011 Report Posted December 9, 2011 Hi Pete, since installing the FSUIPC 4.749f version yesterday, I can no longer connect with Wide Client from my laptop to my PC. I have tried re-installing, and also re-installing an older version, but to no avail. Everything has been working smoothly for years, and I have changed nothing else on either computer. I've attached the logs if these are of any help (well, printed them below as I can't seem to upload them). Would welcome any input you can offer on this. Thanks Jack Johnston Install Log Installer for FSUIPC4.DLL version 4.745 Looking in registry for FSX install path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"AppPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"AppPath" Not there, so looking in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... >>> OK! FOUND Prepar3D! <<< ... =========================================================== INSTALLATION FOR FSX: AppPath="F:\Microsoft Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: F:\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... No previous valid version found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "F:\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Jack\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Jack\AppData\Roaming" Found FSX.CFG in "C:\Users\Jack\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== INSTALLATION FOR Prepar3D: AppPath="F:\Prepar3D\" Checking version of Prepar3D.EXE: ... Version 1.2.3253.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: F:\Prepar3D\Modules\FSUIPC4.DLL ... Version 4.745 found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "F:\Prepar3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Jack\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Jack\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Jack\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed. Registration check for FSUIPC4 and WideFS was successful! (result code 00) *************** End of Install Log *************** FSUIPC 4 Log ********* FSUIPC4, Version 4.749f by Pete Dowson ********* User Name="John Johnston" User Addr="jj@atwsixpack.com" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 Module base=61000000 47 System time = 09/12/2011 17:52:28 63 FLT UNC path = "\\FLUSI-PC\Users\Jack\Documents\Flight Simulator X Files\" 94 Trying to connect to SimConnect Acc/SP2 Oct07 ... 94 FS UNC path = "\\FLUSI-PC\Microsoft Flight Simulator X\" 437 LogOptions=00000000 00000001 437 Wind smoothing fix is fully installed 437 G3D.DLL fix attempt installed ok 437 SimConnect_Open succeeded: waiting to check version okay 437 Trying to use SimConnect Acc/SP2 Oct07 4789 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 4789 Initialising SimConnect data requests now 4789 FSUIPC Menu entry added 4821 \\FLUSI-PC\Users\Jack\Documents\Flight Simulator X Files\C172 at Friday Harbour.FLT 4821 \\FLUSI-PC\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP_mod.AIR 193161 Aircraft="Cessna Skyhawk 172SP Paint1" 193176 System time = 09/12/2011 17:55:41, Simulator time = 10:52:33 (01:52Z) 196811 Starting everything now ... 200368 Advanced Weather Interface Enabled 213347 Weather Mode now = Custom 216732 Sim stopped: average frame rate for last 24 secs = 18.4 fps 1914055 Sim stopped: average frame rate for last 1669 secs = 20.0 fps 1932525 System time = 09/12/2011 18:24:41, Simulator time = 11:20:46 (02:20Z) 1932525 *** FSUIPC log file being closed Average frame rate for running time of 1694 secs = 20.0 fps G3D fix: Passes 59654, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 737 Allocs, 737 Freed ********* FSUIPC Log file closed *********** Wide Client ini ; ===================================================== [Config] Port=8002 ServerName=FLUSI-PC Protocol=TCP Window=175,409,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [sounds] Path=C:\Program Files\WideClient\Sound\ Device1=Primärer Soundtreiber Device2=Speakers (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) Wide Client Log ********* WideClient Log [version 6.86] Class=FS98MAIN ********* Date (dmy): 09/12/11, Time 17:59:25.185: Client name is JACK-ASUS 172 LUA: "C:\Program Files\WideClient\Initial.LUA": not found 187 Attempting to connect now 203 Trying TCP/IP host "FLUSI-PC" port 8002 ... 203 ... Okay, IP Address = 192.168.1.36 21201 Error on client pre-Connection Select() [Error=10060] Connection timed out 21201 Ready to try connection again 22215 Attempting to connect now 66269 Trying TCP/IP host "FLUSI-PC" port 8002 ... 66269 ... Okay, IP Address = 192.168.1.36 132382 Trying TCP/IP host "FLUSI-PC" port 8002 ... 132382 ... Okay, IP Address = 192.168.1.36 198449 Trying TCP/IP host "FLUSI-PC" port 8002 ... 198449 ... Okay, IP Address = 192.168.1.36 264469 Trying TCP/IP host "FLUSI-PC" port 8002 ... 264469 ... Okay, IP Address = 192.168.1.36 330535 Trying TCP/IP host "FLUSI-PC" port 8002 ... 330535 ... Okay, IP Address = 192.168.1.36 396601 Trying TCP/IP host "FLUSI-PC" port 8002 ... 396601 ... Okay, IP Address = 192.168.1.36 462652 Trying TCP/IP host "FLUSI-PC" port 8002 ... 462652 ... Okay, IP Address = 192.168.1.36 528719 Trying TCP/IP host "FLUSI-PC" port 8002 ... 528719 ... Okay, IP Address = 192.168.1.36 594785 Trying TCP/IP host "FLUSI-PC" port 8002 ... 594785 ... Okay, IP Address = 192.168.1.36 660898 Trying TCP/IP host "FLUSI-PC" port 8002 ... 660898 ... Okay, IP Address = 192.168.1.36 726996 Trying TCP/IP host "FLUSI-PC" port 8002 ... 726996 ... Okay, IP Address = 192.168.1.36 793062 Trying TCP/IP host "FLUSI-PC" port 8002 ... 793062 ... Okay, IP Address = 192.168.1.36 859176 Trying TCP/IP host "FLUSI-PC" port 8002 ... 859176 ... Okay, IP Address = 192.168.1.36 925242 Trying TCP/IP host "FLUSI-PC" port 8002 ... 925242 ... Okay, IP Address = 192.168.1.36 991308 Trying TCP/IP host "FLUSI-PC" port 8002 ... 991308 ... Okay, IP Address = 192.168.1.36 1057375 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1057375 ... Okay, IP Address = 192.168.1.36 1123426 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1123426 ... Okay, IP Address = 192.168.1.36 1189539 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1189539 ... Okay, IP Address = 192.168.1.36 1255605 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1255605 ... Okay, IP Address = 192.168.1.36 1321719 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1321719 ... Okay, IP Address = 192.168.1.36 1387785 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1387785 ... Okay, IP Address = 192.168.1.36 1453898 Trying TCP/IP host "FLUSI-PC" port 8002 ... 1453898 ... Okay, IP Address = 192.168.1.36 1486144 ****** End of session performance summary ****** 1486144 Total time connected = 0 seconds 1486144 Reception maximum: 0 frames/sec, 0 bytes/sec 1486144 Transmission maximum: 0 frames/sec, 0 bytes/sec 1486144 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 1486144 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* Wide Server Log ********* WideServer.DLL Log [version 7.749f] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 09/12/11, Time 17:55:45.520: Server name is FLUSI-PC 15803 Initialising TCP/IP server 15819 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 1732750 Closing down now ... Memory managed: Offset records: 737 alloc, 736 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed *********
Pete Dowson Posted December 9, 2011 Report Posted December 9, 2011 since installing the FSUIPC 4.749f version yesterday, I can no longer connect with Wide Client from my laptop to my PC. I have tried re-installing, and also re-installing an older version, but to no avail. Something else must have changed apart from the FSUIPC version if restoring your previous version didn't help. And there have been no changes in WideFS except for the new broadcast mode which is separate code and would need explicitly enabling. Everything has been working smoothly for years, and I have changed nothing else on either computer. So something must have changed by itself? Wide Client ini ServerName=FLUSI-PC Protocol=TCP Not that it should matter, but is there any reason you set these specifically instead of allowing it to connect automatically? ********* WideClient Log [version 6.86] Class=FS98MAIN ********* Could you try a more recent one, please, like the version 6.90 posted at the same time as the FSUIPC update? 203 Trying TCP/IP host "FLUSI-PC" port 8002 ... 203 ... Okay, IP Address = 192.168.1.36 21201 Error on client pre-Connection Select() [Error=10060] Connection timed out ... ]********* WideServer.DLL Log [version 7.749f] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 09/12/11, Time 17:55:45.520: Server name is FLUSI-PC 15803 Initialising TCP/IP server 15819 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 1732750 Closing down now ... These logs certainly indicate a block, probably at the Server end -- the client is sending messages but the Server never sees any at all. I think it must be your firewall. Have you disabled it both ends, or at least allowed WideClient through on the client and FSX through on the server? If you need the port number it is the one shown in your INI files -- 8002. If you didn't change the firewall settings yourself, maybe it happened through some automatic update? Regards Pete
Holy Cheese Posted December 11, 2011 Author Report Posted December 11, 2011 Yes, I also found it strange that reverting to an older version did not solve the problem - certainly looks to point to a problem with my network communication. If something has changed by itself, it can only be through a Microsoft Update. The only other thing I can think of is that I had to restart my router a couple of days back due to some difficulties with the WLAN - but my laptop and desktop are connected by cable and not by WLAN. Regarding the server name and protocol, I did allow it to connect automatically at first, but when it still didn't worked I added these lines in accordance with your user guide, which states that in case of problems one may have to add these lines manually. Also now tried with the 6.90 version of Wide Client, still not working. Firewalls are set to allow WideClient through on the laptop and also for FSX on the desktop. Have also tried switching off the firewalls, still no joy. Since I am not having any problems with the laptop communicating normally in the network (I can see and open 5 mapped drives no problem) I am beginning to suspect that the problem must lie in my router - will open its settings and see if I can see anything. Otherwise I'm completely stumped. Thanks Jack
Pete Dowson Posted December 11, 2011 Report Posted December 11, 2011 Yes, I also found it strange that reverting to an older version did not solve the problem - certainly looks to point to a problem with my network communication. If something has changed by itself, it can only be through a Microsoft Update. The only other thing I can think of is that I had to restart my router a couple of days back due to some difficulties with the WLAN - but my laptop and desktop are connected by cable and not by WLAN. But presumably by cables via the router? So another possibility is a block there? Regarding the server name and protocol, I did allow it to connect automatically at first, but when it still didn't worked I added these lines in accordance with your user guide, which states that in case of problems one may have to add these lines manually. Well, it's usually a way of connecting when the computers are in different workgroups, but it has also come in handy when the IP address supplied for one of the PCs is wrong -- see the FAQ about this. You could try setting the IP address in the INI instead of the ServerName. Also now tried with the 6.90 version of Wide Client, still not working. That's good, in a way, because it proves again that it isn't a change in FSUIPC's Server that's doing it. Firewalls are set to allow WideClient through on the laptop and also for FSX on the desktop. Have also tried switching off the firewalls, still no joy.Since I am not having any problems with the laptop communicating normally in the network (I can see and open 5 mapped drives no problem) I am beginning to suspect that the problem must lie in my router - will open its settings and see if I can see anything. Otherwise I'm completely stumped. Let me know, please. I assume you've checked the IP address that the Client is logging? (192.168.1.36). It looks like the right sort of IP address (unlike the ISP host addresses sometimes returned by routers in strange modes), but it bears checking. Regards Pete
Holy Cheese Posted December 12, 2011 Author Report Posted December 12, 2011 Hi Pete, problem solved, I'm happy to report. It was simple and stupid. When I had my WLAN problem the other night, I had disconnected the LAN cable from my flight sim pc in order to attach it to my girlfriend's laptop, as she could no longer get into the internet via WLAN (hers is normally not attached by cable as I normally have my desktop, my laptop and 2 tv wireless devices attached by cable and the router only has 4 ports). When I reconnected the cable to the desktop, I had inadvertently connected it to a second LAN port. When that came to mind this morning, I reconnected using the other LAN port and voilà - everything works again. Sorry to have wasted your time with this elementary error, and many many thanks for your work in finding a solution to the dreaded g3d.dll error - now I can fly in ORBX YBBN again :razz: . Wish you all the best for Xmas and the New Year! Cheers Jack
Pete Dowson Posted December 12, 2011 Report Posted December 12, 2011 Wish you all the best for Xmas and the New Year! You too, and I'm glad the problem was really so simple! ;-) Pete
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now